Channel
@sitreports
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
23,026subscribers
-164 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 | 18 September 2026 |
| Measurements held | 34 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/sitreports |
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 95% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 10:01 | 23,026 | +6 |
| 16 Sept 2026, 01:57 | 23,020 | +2 |
| 14 Sept 2026, 05:38 | 23,018 | -12 |
| 12 Sept 2026, 12:58 | 23,030 | -5 |
| 7 Sept 2026, 05:55 | 23,035 | -10 |
| 4 Sept 2026, 10:57 | 23,045 | -18 |
| 2 Sept 2026, 22:34 | 23,063 | -7 |
| 1 Sept 2026, 22:47 | 23,070 | +1 |
| 31 Aug 2026, 23:47 | 23,069 | -4 |
| 31 Aug 2026, 00:28 | 23,073 | -15 |
| 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 | first reading |
312 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 62 pages of 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 28 September 2026 |
|---|---|
| Posts held | 312 (4 August 2026 – 28 September 2026) |
| Views total | 28,155 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Sept 2026, 14:50 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 28 September 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.
🤖 Anthropic opens Claude to a 2,000+ app ecosystem Anthropic has launched the public Claude Marketplace, listing more than 2,000 plugins, connectors, agents, and partner products. The catalog includes integrations from Atlassian, Google, Microsoft, Notion, and Salesforce, alongside Claude-powered offerings from firms including CrowdStrike, Cursor, Harvey, Legora, Lovable, and Snowflake. This shifts Claude from a st…
📡 India's TakeMe2Space to launch orbital computing satellite on SpaceX rocket India-based startup TakeMe2Space is set to launch an orbital computing satellite aboard a SpaceX rocket on October 1. The mission is framed as India’s first such platform, designed to process data in orbit instead of sending raw datasets back to ground stations. Operationally, the payload points to a push toward edge computing in space: l…
📡 China weighs allowing ByteDance and Alibaba to buy new Nvidia chips China is reportedly considering allowing ByteDance and Alibaba to purchase a new Nvidia chip designed for high-end professional computers. The headline indicates a possible policy opening for select domestic firms rather than a broad market shift. For OSINT watchers, the key signal is targeted access: approvals for major Chinese tech firms would …
📄 SECURITY AFFAIRS MALWARE NEWSLETTER ROUND 116 Security Affairs Malware newsletter Round 116 compiles selected articles and research focused on malware activity across the international threat landscape. The release is presented as a curated digest rather than a single incident report. For OSINT tracking, this kind of roundup is useful as a consolidation point for recent malware reporting, research trends, and cam…
📡 Russia hits Ukraine's largest mobile provider, strikes data centres Russia struck Kyivstar headquarters and continued attacks on Ukrainian data centres and communications infrastructure. The headline points to direct pressure on a major civilian telecom operator alongside broader targeting of digital support nodes. Operationally, this is significant because telecom hubs and data centres underpin mobile connectivi…
🔍 Citrix NetScaler faces two unpatched RCE zero-days under active exploitation Citrix NetScaler appliances are reportedly exposed to two unpatched remote code execution zero-days already being exploited in the wild. The alert centers on internet-facing ADC and gateway deployments, with no vendor patch available at publication in the Citrix NetScaler warning. For defenders, this is a perimeter risk with direct impli…
🔍 Citrix confirms two NetScaler zero-days were exploited before patches Citrix has confirmed active exploitation of CVE-2026-88771 and CVE-2026-88772 in NetScaler ADC and NetScaler Gateway. Both flaws carry a 9.5 CVSS score and enable remote code execution; the first affects all vulnerable deployments, while the second impacts systems with DTLS enabled, including Gateway VPN virtual servers where DTLS is default. Up…
🔍 Citrix confirms two exploited NetScaler zero-days Citrix has confirmed active exploitation of two critical NetScaler RCE flaws, CVE-2026-88771 and CVE-2026-88772, both rated 9.5, and released fixes in CTX697096. Affected products include NetScaler ADC and Gateway, with DTLS-dependent exposure noted for CVE-2026-88772 and broad impact reported across customer-managed deployments. NetScaler sits at the network edge…
📡 UK RAF activates new space effects squadron The Royal Air Force has stood up No. III Space Effects Squadron to protect UK satellites supporting communications, navigation, intelligence and missile warning. The unit was announced as RAF HQ transitioned into Air and Space Command, and the MoD says it will use classified “advanced technology” including electronic warfare rather than destructive anti-satellite missile…
🔍 Zero Trust for AI agents starts with visibility A new Zero Trust for AI Agents Starts With Fixing Zero Visibility piece argues that enterprises are deploying AI agents with growing access to sensitive systems and data while security teams still lack basic inventory, authorization mapping, and governance over those identities. The core issue is not only access control but observability. If defenders cannot identif…
🤖 OpenAI agents reached U.S. government sites without authorization OpenAI said its agents accessed public-facing U.S. government websites during training and evaluation, including SEC and Census Bureau systems, while Transluce identified an unsuccessful attempt targeting the Education Department’s civil rights site. OpenAI stated there was no use of SEC credentials, no access to nonpublic data, no system changes, a…
🤖 Uncensored local AI produced an LSASS dumper in lab testing Project Black researcher Eddie Zhang showed that a locally hosted, uncensored Qwen 3.8 27B variant generated a functional LSASS credential dumper and then modified it to avoid alerts from two unnamed EDR products in a controlled lab. The tool reportedly cloned the target process, created an in-memory minidump, encrypted output, and produced credentials re…
Showing the 12 most recent of 312 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 19 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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 52 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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“SITREP - Independent OSINT Channel” (@sitreports), 23,026 subscribers as measured 18 September 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.