Channel
@information_security_channel
On this record: Growth · Engagement · What this channel posts · Posts · Telegram's recommendations · Cite this entry
11,366subscribers
+80 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 | 26 August 2026 |
| Measurements held | 19 |
| Confirmed unchanged | 1 time, most recently 26 August 2026 |
| On Telegram | t.me/information_security_channel |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 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 | +3 |
| 18 Aug 2026, 14:38 | 11,347 | +12 |
| 17 Aug 2026, 12:44 | 11,335 | +7 |
| 16 Aug 2026, 04:36 | 11,328 | +8 |
| 14 Aug 2026, 16:05 | 11,320 | +7 |
| 13 Aug 2026, 07:38 | 11,313 | +6 |
| 12 Aug 2026, 07:54 | 11,307 | +3 |
| 11 Aug 2026, 07:02 | 11,304 | +1 |
| 10 Aug 2026, 10:37 | 11,303 | +1 |
| 9 Aug 2026, 09:53 | 11,302 | +5 |
| 8 Aug 2026, 07:21 | 11,297 | +10 |
| 7 Aug 2026, 05:28 | 11,287 | +1 |
| 6 Aug 2026, 11:02 | 11,286 | first reading |
133 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 36 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 26 August 2026 |
|---|---|
| Posts held | 133 (4 August 2026 – 26 August 2026) |
| Views total | 29,310 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Aug 2026, 06:24 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 27 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.
AI Speeds Up Malware Development, Not Its Success Rate: Analysis https://www.securityweek.com/ai-speeds-up-malware-development-not-its-success-rate-analysis/ Palo Alto Networks Unit 42 analyzed 405 AI-linked malware samples and found only 12 reached production endpoints. The post AI Speeds Up Malware Development, Not Its Success Rate: Analysis (https://www.securityweek.com/ai-speeds-up-malware-development-not-its-su…
Adobe and Nvidia Patch Dozens of Vulnerabilities https://www.securityweek.com/adobe-and-nvidia-patch-dozens-of-vulnerabilities/ Adobe and Nvidia each published several advisories, including ones that address critical vulnerabilities in their products. The post Adobe and Nvidia Patch Dozens of Vulnerabilities (https://www.securityweek.com/adobe-and-nvidia-patch-dozens-of-vulnerabilities/) appeared first on SecurityWe…
CISA: Over 100 Internet-Exposed Water Systems Targeted in July Cyberattacks https://www.securityweek.com/cisa-over-100-internet-exposed-water-systems-targeted-in-july-cyberattacks/ The agency has released guidance on reducing internet exposure in the wake of the recent Iran-linked hacker attacks. The post CISA: Over 100 Internet-Exposed Water Systems Targeted in July Cyberattacks (https://www.securityweek.com/cisa-o…
The MFA Identity Trap: When Authentication Creates a False Sense of Security https://www.securityweek.com/the-mfa-identity-trap-when-authentication-creates-a-false-sense-of-security/ Organizations must distinguish identity verification, authentication and threat detection, or risk successfully authenticating the attackers they are trying to stop. The post The MFA Identity Trap: When Authentication Creates a False Se…
Chrome 152 Patches Over 300 Vulnerabilities https://www.securityweek.com/chrome-152-patches-over-300-vulnerabilities/ Most of the flaws were discovered by Google using AI, but researchers are still discovering high-value Chrome vulnerabilities. The post Chrome 152 Patches Over 300 Vulnerabilities (https://www.securityweek.com/chrome-152-patches-over-300-vulnerabilities/) appeared first on SecurityWeek (https://www.s…
Sensitive Information Exposed in Nutex Health Data Breach https://www.securityweek.com/sensitive-information-exposed-in-nutex-health-data-breach/ Nutex Health has informed the SEC that it recently detected unauthorized access and data exfiltration. The post Sensitive Information Exposed in Nutex Health Data Breach (https://www.securityweek.com/sensitive-information-exposed-in-nutex-health-data-breach/) appeared firs…
CISA Warns of Exploited Gitea Vulnerability https://www.securityweek.com/cisa-warns-of-exploited-gitea-vulnerability/ CVE-2026-60004 is a remote code execution vulnerability patched by Gitea developers in late July with the release of version 1.27.1. The post CISA Warns of Exploited Gitea Vulnerability (https://www.securityweek.com/cisa-warns-of-exploited-gitea-vulnerability/) appeared first on SecurityWeek (https:/…
Linux Foundation to Govern TRACE, an Open Standard for AI Runtime Attestation https://www.securityweek.com/linux-foundation-to-govern-trace-an-open-standard-for-ai-runtime-attestation/ TRACE was developed by AMD, Intel, Microsoft, OPAQUE, and TII and contributed to the Linux Foundation. The post Linux Foundation to Govern TRACE, an Open Standard for AI Runtime Attestation (https://www.securityweek.com/linux-foundati…
Road to OSCE3: Episodio 1 – OSEP https://www.offsec.com/blog/road-to-osce3-episodio-1/ ¡Hola a todos! Con este post da comienzo una serie de 3 posts donde hablaré de las certificaciones que forman OSCE3 y de cómo yo me las he preparado. ¿Qué es OSCE3? Si llevas algún tiempo en el mundo de la ciberseguridad ofensiva, seguro que has oído hablar del OSCP (Offensive Security Certified Professional). Es The post Road …
Knowing what not to attack https://www.offsec.com/blog/knowing-what-not-to-attack/ Most talk about offensive security agents is about power. Can it find the bug? Can it chain the exploit? Can it own the box? That’s the easy part. Wiring a model up to tools is normal engineering now, and raw capability improves on its own every time a new model ships. The parts that don’t The post Knowing what not to attack (https://…
Silent Patches Don’t Stop Attackers – They Blind Defenders https://www.securityweek.com/silent-patches-dont-stop-attackers-they-blind-defenders/ Silent patches can become exploit intelligence for attackers while leaving defenders without the context needed to prioritize risk. The post Silent Patches Don’t Stop Attackers – They Blind Defenders (https://www.securityweek.com/silent-patches-dont-stop-attackers-they-blin…
Taiwan Charges 9 Over Illegal AI Server Exports to China, Including Nvidia and Super Micro Staff https://www.securityweek.com/taiwan-charges-9-over-illegal-ai-server-exports-to-china-including-nvidia-and-super-micro-staff/ AI infrastructure, including advanced semiconductors mostly made in Taiwan, has become a key point of competition between the U.S. and China. The post Taiwan Charges 9 Over Illegal AI Server Expor…
Showing the 12 most recent of 133 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 2 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 26 August 2026 — this entry's latest reading, not the date you are reading this.
“Information Security” (@information_security_channel), 11,366 subscribers as measured 26 August 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.