Channel
@sitreports
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
22,944subscribers
-246 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 |
| Created | 11 October 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 19 October 2026 |
| Measurements held | 42 |
| Confirmed unchanged | 1 time, most recently 19 October 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 |
|---|---|---|
| 19 Oct 2026, 05:56 | 22,944 | -2 |
| 18 Oct 2026, 04:26 | 22,946 | -11 |
| 16 Oct 2026, 05:01 | 22,957 | -6 |
| 15 Oct 2026, 03:59 | 22,963 | -1 |
| 13 Oct 2026, 21:58 | 22,964 | -17 |
| 10 Oct 2026, 16:17 | 22,981 | -6 |
| 6 Oct 2026, 10:58 | 22,987 | -2 |
| 1 Oct 2026, 11:15 | 22,989 | -37 |
| 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 | first reading |
424 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 88 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 14 October 2026 |
|---|---|
| Posts held | 424 (4 August 2026 – 14 October 2026) |
| Views total | 59,326 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Oct 2026, 11:20 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.
Measured directly from 2 videos 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.
🔍 253 verified security bugs found across AI agent tools in MCP servers Researchers testing 118 open-source MCP servers identified 253 verified bugs affecting 343 tools after reviewing 508 candidates. The dataset covered 273 reachable servers and 3,405 extracted tools, with findings including 115 reflected-output flaws, 64 path-traversal issues, 58 log-injection bugs, 7 SSRF cases, 5 data-exfiltration bugs, 3 comman…
🤖 Anthropic flags low-cost AI as a potential IoT botnet enabler Anthropic warns that small AI models may soon be capable of building self-propagating botnets across insecure IoT devices, lowering the skill barrier for large-scale compromise. The Anthropic warning centers on how compact models could automate discovery, exploitation, and propagation against weakly secured connected hardware. The operational significa…
🔍 Ghostscript PDF flaw opens RCE path on upload-processing servers A critical heap overflow in Ghostscript tracked as CVE-2026-39919 allows remote code execution via crafted PDFs. Affected versions span 9.21 through 10.07.1. Researchers showed the bug can be reached when systems render attacker-supplied PDFs, including WordPress deployments that generate previews through ImageMagick/Imagick. Artifex fixed the issue …
🔍 Microsoft ships record Patch Tuesday with 1,413 fixes Microsoft has released patches for 1,413 vulnerabilities across its product stack, a record monthly total. The batch includes an actively exploited Windows Shell flaw and spans core Windows components, enterprise software, and developer platforms detailed in Microsoft’s October security update. The scale alone raises triage pressure for defenders: broad remedi…
🔍 French supermarket refrigeration attacks disrupted food storage at scale Cyberattacks hit refrigeration systems at French retailers including Carrefour, Intermarché, Monoprix, and Coopérative U, with temperatures reportedly driven up to 50°C. Hundreds of stores were affected, forcing disposal of perishable stock; some incidents reportedly triggered fires. Danfoss said impacted customers were running outdated firmw…
🔍 CISA adds Ivanti Connect Secure flaw to KEV CISA has added CVE-2026-104935 to its Known Exploited Vulnerabilities catalog. The flaw is an authentication bypass by spoofing in Ivanti Connect Secure before 25.1.3.0, with potential for remote unauthenticated command execution. Ivanti said the issue has been exploited in the wild and noted that version 22.7R2.14 and earlier are not affected. KEV inclusion shifts this…
🔍 Ivanti Connect Secure hit by chained zero-days Attackers are exploiting three zero-day vulnerabilities in Ivanti Connect Secure to obtain root access. Two of the flaws have patches available, while the third remains unpatched. The chain affects a remote access platform widely deployed at the network edge, making exposure immediate for organizations that rely on ICS gateways. The operational takeaway is simple: pa…
📡 Yandex cloud outage follows strikes on three data centers Yandex says drone attacks damaged facilities in Sasovo on 8 October, Kaluga on 9 October, and Vladimir on 11 October, forcing two sites offline and degrading a third. The company’s status page shows ongoing issues across cloud services, while customers report missing file thumbnails, failed downloads, and HTTP 302, 500, and 504 errors. The incident affects…
📡 US 8th Army adapts for drone-heavy warfare in Korea The US 8th Army says it is folding lessons from Ukraine, the Middle East, and recent US operations into training, modernization, and experimentation on the Korean Peninsula. At AUSA, commanders said forces are preparing for one-way attack drones, survivability jumps, deception measures, and integration of IBCS-enabled Patriot and IFPC systems. The shift indicate…
🔍 Nippon Columbia incident exposes 8.7 million karaoke-linked records Daiichi Kosho says malware on a Nippon Columbia Group employee device exposed data tied to 8,631,000 customers and 93,000 employees. Affected records include names, gender, dates of birth, email addresses, and phone numbers linked to brands including BIG ECHO and Karaoke CLUB DAM. The company’s customer notice says no passwords were included and n…
🔍 Bitdefender tracks firmware-level Android malware on low-cost phones Bitdefender says the Midnight Mimosa cluster was found preinstalled in firmware on budget Android phones using MediaTek platforms, affecting thousands of devices across 150+ countries. Hidden in system packages, it cannot be removed by users, silently installs apps, commits ad fraud, and can turn phones into proxy relay nodes. Bitdefender’s Midni…
🔍 CISA expands KEV with five actively exploited flaws CISA added ProFTPD, ONLYOFFICE Docs, Strapi, Apache Struts, and ISC BIND vulnerabilities to its Known Exploited Vulnerabilities catalog. The listed CVEs span file access abuse, path traversal with possible RCE, sensitive data exposure, command injection, and denial-of-service. Federal agencies were ordered to remediate by 11 October 2026. The update places these…
Showing the 12 most recent of 424 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 55 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 19 October 2026 — this entry's latest reading, not the date you are reading this.
“SITREP - Independent OSINT Channel” (@sitreports), 22,944 subscribers as measured 19 October 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.