Channel
@sitreports
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
23,088subscribers
-102 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001426514777 |
|---|---|
| Type | Channel |
| Username | @sitreports |
| Description | AI, technology, mass surveillance, and intelligence — everything you need to know about tomorrow. |
| Created | 11 October 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/sitreports |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 01:52 | 23,088 | -8 |
| 29 Aug 2026, 05:04 | 23,096 | -4 |
| 28 Aug 2026, 02:25 | 23,100 | +1 |
| 26 Aug 2026, 23:43 | 23,099 | -1 |
| 26 Aug 2026, 02:43 | 23,100 | -11 |
| 25 Aug 2026, 05:35 | 23,111 | -10 |
| 24 Aug 2026, 07:04 | 23,121 | -9 |
| 22 Aug 2026, 18:04 | 23,130 | -2 |
| 21 Aug 2026, 10:35 | 23,132 | -2 |
| 20 Aug 2026, 09:22 | 23,134 | -1 |
| 19 Aug 2026, 09:18 | 23,135 | +19 |
| 18 Aug 2026, 11:36 | 23,116 | -9 |
| 17 Aug 2026, 11:34 | 23,125 | -10 |
| 16 Aug 2026, 02:27 | 23,135 | -7 |
| 14 Aug 2026, 12:55 | 23,142 | -6 |
| 13 Aug 2026, 05:56 | 23,148 | -5 |
| 12 Aug 2026, 08:33 | 23,153 | -10 |
| 11 Aug 2026, 08:23 | 23,163 | -4 |
| 9 Aug 2026, 12:32 | 23,167 | -7 |
| 8 Aug 2026, 10:52 | 23,174 | first reading |
237 posts held, back to 4 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 50 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 30 August 2026 |
|---|---|
| Posts held | 237 (4 August 2026 – 30 August 2026) |
| Views total | 93,497 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 30 Aug 2026, 09:40 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 30 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
🤖 Unitree G1 flaws enable remote root access and robot-to-robot spread A security researcher chained two Unitree G1 vulnerabilities, CVE-2026-76639 and CVE-2026-76640, to gain unauthenticated root access within Bluetooth range. The chain abused an unpaired BLE path, a cloud decryption workflow lacking ownership checks, and a firmware-level buffer overflow. Unitree patched the cloud-side ownership check and paid a $5…
🔍 Five critical WordPress flaws expose sites to takeover and RCE Researchers detailed five critical vulnerabilities affecting WordPress plugins and themes, with impact ranging from full site takeover to remote code execution. The issue set spans widely deployed third-party components in the WordPress ecosystem, extending risk beyond core platform security. The WordPress ecosystem remains exposed where vulnerable plu…
🔍 Critical Gogs Path Traversal Flaw Enables Remote Code Execution via Git Hooks A critical flaw in Gogs is reported to allow authenticated attackers to use path traversal and place malicious Git hooks outside the intended repository storage path, resulting in remote code execution. Operationally, this turns a code hosting platform into an execution point. Any environment exposing Gogs to multiple users should treat…
🔍 TA4922 Hackers Use Tax Phishing to Deploy PackClient RAT Across Asia TA4922 is identified as using tax-themed phishing to deliver the PackClient RAT across Asia. The activity links a Chinese-speaking threat actor to credential-style lures built around tax matters, with malware deployment centered on a modular remote access framework. Operationally, tax-themed phishing indicates targeting through high-trust admini…
🔍 Supply-Chain Worm Hits TanStack Query Code Generator Multiple releases of the npm package @7nohe/openapi-react-query-codegen, used to generate type-safe TanStack Query hooks, were reportedly compromised to steal developer credentials. The reported impact includes developer workstations and CI environments, with risks of repository backdoors and poisoned downstream packages. This is a high-leverage software supply…
⚡ US border task force uses laser to down 3 cartel-linked drones Joint Task Force-Southern Border said it used the Army’s AMP-HEL high-energy laser to defeat three hostile drones over two days this week while supporting CBP under USNORTHCOM. The unit said the UAVs were tied to cartel activity and posed a physical threat to troops and border agents. The system was identified as an AeroVironment platform in a release.…
🔍 Cosmos EVM flaw exploited after broad exposure window A security flaw in Cosmos EVM was reportedly exploited after Cosmos Labs had identified that every blockchain running the component was vulnerable. The issue affected chains using the EVM integration layer across the Cosmos ecosystem, creating a shared exposure set rather than an isolated single-chain bug. The key takeaway is concentration risk: one vulnerable…
🔍 Over 8,300 internet-exposed Gitea servers remain vulnerable to active code injection attacks Shadowserver counted 8,393 exposed instances still unpatched against CVE-2026-60004. The flaw lets an authenticated attacker execute shell commands via Gitea’s diffpatch API, and default self-registration can provide the required repository write access. Gitea fixed the issue in 1.27.1 in Gitea’s advisory. The exposure is…
🔍 AI agent instruction files open a new supply-chain path Research into public llms.txt and llms-full.txt files found 8,565 files across 6,214 live domains, with 237+ cases where official agent guidance pointed to unclaimed package names or expired domains. In a controlled test, Alon Hertz registered referenced names and achieved code execution inside a Fortune 500 environment within four minutes via llms.txt-driven…
🔍 CISA expands KEV with ownCloud, Linux kernel, Artifactory flaws CISA has added CVE-2023-49105 in ownCloud, CVE-2026-53362 in the Linux kernel, and CVE-2026-66384 in JFrog Artifactory to its Known Exploited Vulnerabilities catalog. The ownCloud issue is an improper-authentication flaw in WebDAV, the kernel issue is an out-of-bounds write in IPv6 packet handling, and the Artifactory issue is a path-traversal bug in …
🔍 PaperCut flaws chained for unauthenticated RCE Attackers are exploiting two PaperCut vulnerabilities in tandem to achieve remote code execution without authentication. The reported chain removes the need for valid credentials and turns exposed PaperCut instances into directly reachable initial access targets via the PaperCut vulnerabilities. The operational significance is straightforward: internet-facing print m…
📡 DISA expands industry outreach for combatant command migration to DoDNet DISA issued an additional sources-sought notice as it prepares to move all 11 U.S. combatant commands from legacy common-use NIPRNet and SIPRNet services into DoDNet by the end of FY2028. The effort covers roughly 231,000 users across about 200 sites and seeks one contract spanning discovery, network and endpoint migration, and transition to …
Showing the 12 most recent of 237 posts we hold for @sitreports. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank — 865,189 of 1,626,935entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 35 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 30 August 2026 — this entry's latest reading, not the date you are reading this.
“SITREP - Independent OSINT Channel” (@sitreports), 23,088 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/sitreports.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.