Channel
@information_security_channel
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
11,501subscribers
+215 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001003346570 |
|---|---|
| Type | Channel |
| Username | @information_security_channel |
| Created | 20 October 2015 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 32 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/information_security_channel |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 17 Sept 2026, 18:39 | 11,501 | +19 |
| 14 Sept 2026, 00:22 | 11,482 | +15 |
| 12 Sept 2026, 05:37 | 11,467 | +4 |
| 9 Sept 2026, 23:57 | 11,463 | +22 |
| 6 Sept 2026, 13:38 | 11,441 | +5 |
| 4 Sept 2026, 05:20 | 11,436 | +19 |
| 2 Sept 2026, 21:16 | 11,417 | +8 |
| 1 Sept 2026, 20:44 | 11,409 | +3 |
| 31 Aug 2026, 19:58 | 11,406 | +5 |
| 30 Aug 2026, 22:52 | 11,401 | +8 |
| 30 Aug 2026, 01:28 | 11,393 | +14 |
| 28 Aug 2026, 23:37 | 11,379 | +4 |
| 27 Aug 2026, 21:32 | 11,375 | +9 |
| 26 Aug 2026, 21:18 | 11,366 | +2 |
| 25 Aug 2026, 19:23 | 11,364 | +3 |
| 24 Aug 2026, 16:14 | 11,361 | +5 |
| 23 Aug 2026, 01:03 | 11,356 | +7 |
| 21 Aug 2026, 11:55 | 11,349 | +1 |
| 20 Aug 2026, 14:42 | 11,348 | -2 |
| 19 Aug 2026, 12:51 | 11,350 | first reading |
165 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 44 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 2 September 2026 |
|---|---|
| Posts held | 165 (4 August 2026 – 2 September 2026) |
| Views total | 12,345 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 00:05 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.
OpenLeash Adds a Human Check to Risky AI Agent Actions https://www.securityweek.com/openleash-adds-a-human-check-to-risky-ai-agent-actions/ The security tool intercepts potentially dangerous agent actions, blocking clear threats and requesting human approval when intent is uncertain. The post OpenLeash Adds a Human Check to Risky AI Agent Actions (https://www.securityweek.com/openleash-adds-a-human-check-to-risky-ai…
What If Your Idea Became the Next OffSec Lab? https://www.offsec.com/blog/offsec-creator-platform/ Learn all about OffSec's new Creator Platform - create labs, earn rewards and help the security community skill up. The post What If Your Idea Became the Next OffSec Lab? (https://www.offsec.com/blog/offsec-creator-platform/) appeared first on OffSec (https://www.offsec.com/).
UK Moves to Block High-Risk Tech Suppliers From Critical Infrastructure https://www.securityweek.com/uk-moves-to-block-high-risk-tech-suppliers-from-critical-infrastructure/ Late amendments to the Cyber Security and Resilience Bill would give ministers new powers to restrict risky technology providers as supply chain attacks intensify. The post UK Moves to Block High-Risk Tech Suppliers From Critical Infrastructure …
Chrome and Firefox Updates Patch Dozens of Vulnerabilities https://www.securityweek.com/chrome-and-firefox-updates-patch-dozens-of-vulnerabilities/ The browser refreshes fix multiple use-after-free, sandbox escape, and privilege escalation bugs. The post Chrome and Firefox Updates Patch Dozens of Vulnerabilities (https://www.securityweek.com/chrome-and-firefox-updates-patch-dozens-of-vulnerabilities/) appeared first…
23-Year-Old Sality P2P Botnet Disrupted https://www.securityweek.com/23-year-old-sality-p2p-botnet-disrupted/ The shutdown operation involved peer list manipulation and Sality payload URL takedown. The post 23-Year-Old Sality P2P Botnet Disrupted (https://www.securityweek.com/23-year-old-sality-p2p-botnet-disrupted/) appeared first on SecurityWeek (https://www.securityweek.com/).
SonicWall Warns of Two SMA1000 Zero-Days Exploited in Attacks https://www.securityweek.com/sonicwall-warns-of-two-sma1000-zero-days-exploited-in-attacks/ The vulnerabilities CVE-2026-83549 and CVE-2026-83548 can be chained for unauthenticated remote code execution. The post SonicWall Warns of Two SMA1000 Zero-Days Exploited in Attacks (https://www.securityweek.com/sonicwall-warns-of-two-sma1000-zero-days-exploited-i…
Palo Alto Networks Acquires AI Agent Platform Console https://www.securityweek.com/palo-alto-networks-acquires-ai-agent-platform-console/ The cybersecurity giant announced the acquisition alongside quarterly results showing a 34% increase in revenue and strong growth in next-generation security ARR. The post Palo Alto Networks Acquires AI Agent Platform Console (https://www.securityweek.com/palo-alto-networks-acquir…
Ransomware Gang Claims Nutex Health Data Breach https://www.securityweek.com/ransomware-gang-claims-nutex-health-data-breach/ The company has notified the SEC that hackers accessed patient, employee, provider, business, and financial information. The post Ransomware Gang Claims Nutex Health Data Breach (https://www.securityweek.com/ransomware-gang-claims-nutex-health-data-breach/) appeared first on SecurityWeek (htt…
Critical JFrog Artifactory Vulnerability Reportedly Exploited in the Wild https://www.securityweek.com/critical-jfrog-artifactory-vulnerability-reportedly-exploited-in-the-wild/ Exploitation of the authentication bypass vulnerability CVE-2026-82329 started just days after its public disclosure. The post Critical JFrog Artifactory Vulnerability Reportedly Exploited in the Wild (https://www.securityweek.com/critical-j…
9.5 Million Impacted by Aesto Health Data Breach https://www.securityweek.com/9-5-million-impacted-by-aesto-health-data-breach/ Hackers stole personal and health information from the healthcare technology company’s AWS infrastructure. The post 9.5 Million Impacted by Aesto Health Data Breach (https://www.securityweek.com/9-5-million-impacted-by-aesto-health-data-breach/) appeared first on SecurityWeek (https://www.s…
WatchGuard Patches Critical Vulnerabilities https://www.securityweek.com/watchguard-patches-critical-vulnerabilities/ Three critical issues in the Fireware OS iked process could allow unauthenticated attackers to execute arbitrary code remotely. The post WatchGuard Patches Critical Vulnerabilities (https://www.securityweek.com/watchguard-patches-critical-vulnerabilities/) appeared first on SecurityWeek (https://www.…
PaperCut Exploitation Escalates to Active Intrusions https://www.securityweek.com/papercut-exploitation-escalates-to-active-intrusions/ CISA has added the vulnerabilities tracked as CVE-2026-82078 and CVE-2026-81578 to its KEV catalog. The post PaperCut Exploitation Escalates to Active Intrusions (https://www.securityweek.com/papercut-exploitation-escalates-to-active-intrusions/) appeared first on SecurityWeek (http…
Showing the 12 most recent of 165 posts we hold for @information_security_channel. 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.
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 9 seed channels' Telegram-generated recommendation lists in total. 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Information Security” (@information_security_channel), 11,501 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/information_security_channel.
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.