Channel
@thehackernews
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
162,047subscribers
-109 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001009650918 |
|---|---|
| Type | Channel |
| Username | @thehackernews |
| Created | 17 October 2015 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/thehackernews |
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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 |
|---|---|---|
| 12 Aug 2026, 18:53 | 162,047 | +8 |
| 11 Aug 2026, 21:02 | 162,039 | -74 |
| 10 Aug 2026, 20:22 | 162,113 | -6 |
| 9 Aug 2026, 23:43 | 162,119 | -14 |
| 9 Aug 2026, 01:50 | 162,133 | +1 |
| 8 Aug 2026, 04:13 | 162,132 | -43 |
| 7 Aug 2026, 00:58 | 162,175 | +5 |
| 6 Aug 2026, 04:31 | 162,170 | +14 |
| 6 Aug 2026, 01:31 | 162,156 | no change |
| 5 Aug 2026, 20:40 | 162,156 | first reading |
88 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 17 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 12 August 2026 |
|---|---|
| Posts held | 88 (4 August 2026 – 12 August 2026) |
| Views total | 407,056 |
| Reactions total | 990 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 18: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.
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.
752 reactions across 68 posts, in 8 distinct kinds. The most used accounts for 41.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 315 | 41.9% | |
| 😁 | 106 | 14.1% | |
| 👍 | 87 | 11.6% | |
| 👏 | 81 | 10.8% | |
| 🤔 | 59 | 7.85% | |
| 🤯 | 50 | 6.65% | |
| 😱 | 29 | 3.86% | |
| ⚡ | 25 | 3.32% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 88 of the 88 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 990reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 88 most recent posts we hold, published 4 August 2026 to 12 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🚨 Lazarus-linked attacks exploit a Windows zero-day for SYSTEM access. Dream Job lures defense and aerospace targets with fake recruiter messages. One chain exploits CVE-2026-68820 for privilege escalation; another uses a trojanized PDF viewer to load the new Troy backdoor. See how the attacks work: https://thehackernews.com/2026/08/lazarus-exploits-windows-zero-day-to.html
👏5🤯2
How much malware is hiding beyond what's reported? Stairwell analyzed 1,085 public threat reports and found that every published malware hash corresponded to an average of 2.4 additional malicious variants, uncovering more than 54,000 related malicious files that weren't included in the original research. Organizations may be investigating only part of an attack while related malware remains active inside their env…
👍3🔥2
🚨 737 Chrome VPN extensions routed browser traffic through threat actor-controlled servers. They drew 75,486 installs, with 274 impersonating 66 VPN and privacy brands. Most sent entire browser sessions through SOCKS5 proxies. Read: https://thehackernews.com/2026/08/737-chrome-vpn-extensions-caught.html Check if you installed one.
🔥7👍1👏1😁1
Once attackers get inside, defenses stop just 37%. Across 338M+ attack simulations, reconnaissance was stopped only 10% of the time, while just 14% of simulated attacks triggered an alert. The quiet moves are getting through. Read more: https://thehackernews.com/2026/08/enterprise-defenses-recovered-at-edge.html
🔥3👍2
‼️ Researchers found a way to make a weaker AI decode a stronger model's hidden reasoning. They extracted hidden traces from OpenAI, Anthropic, and Google APIs, recovering secret API keys and passwords, along with other credentials, in publicly shared agent logs. Read more: https://thehackernews.com/2026/08/openai-anthropic-google-api-flaw-let.html
👏8👍3🤯1
🚨 Three Adobe flaws hit CVSS 10.0 and could enable code execution. Adobe patched the maximum-severity bugs in ColdFusion and Campaign Classic, plus a CVSS 9.1 Commerce flaw that could allow privilege escalation. No exploitation has been seen in the wild. Read: https://thehackernews.com/2026/08/adobe-patches-three-cvss-100-coldfusion.html
🔥6😁4👏2
🚨 Watch out: Attackers are exploiting VMware vCenter for persistence. After exploiting CVE-2026-59310, they planted a malicious cron job running reverse_ssh to maintain access. Researchers identified up to 361 victim IPs across 47 countries. Read more: https://thehackernews.com/2026/08/attackers-exploit-vmware-vcenter.html
🔥5
‼️ BREAKING: A 40-minute LiteLLM PyPI compromise potentially exposed 2,100+ organizations. Tied to Trivy's supply-chain attack, the malicious releases stole cloud, SSH, Kubernetes, and database credentials. Researchers later obtained roughly 434,000 captured files mapping potential exposure across thousands of organizations. See what the stolen data reveals: https://thehackernews.com/2026/08/malicious-litellm-relea…
🔥5😁1😱1
⚠️ Warning: SAP Commerce Cloud flaw could enable arbitrary code execution. CVE-2026-58231 carries a CVSS 10.0 score and can be triggered by an unauthenticated attacker abusing a default authentication client with crafted input. SAP has released a fix. Patch and redeploy. Read: https://thehackernews.com/2026/08/sap-commerce-cloud-flaw-could-let.html
😁5🔥2🤯2
‼️ Microsoft patched RoguePlanet. Now the researcher has dropped another zero-day that claims to bypass the fix. ShieldBreak is said to fully bypass Defender’s CVE-2026-50656 patch. The underlying flaw can lead to SYSTEM-level privileges. Read more: https://thehackernews.com/2026/08/shieldbreak-zero-day-poc-claims.html
🔥17😁5
🛑 Exploited Cisco firewall flaw can remotely crash affected devices. CVE-2026-20349 affects certain ASA and FTD configurations. A crafted HTTP request can force a device reload and cause a denial-of-service condition. Cisco says exploitation is already underway and no workaround exists. Patch now: https://thehackernews.com/2026/08/cisco-asa-and-ftd-flaw-exploited-in.html
🔥8👍1
🛑 398 fixes. One exploited Windows zero-day. Four unauthenticated 9.8 RCEs. Microsoft’s August Patch Tuesday fixes CVE-2026-68820, which can elevate an attacker with existing code execution to SYSTEM. It also closes the RCE half of a SharePoint exploit chain. Here’s what to patch first ➝ https://thehackernews.com/2026/08/microsoft-patches-398-flaws-including.html
👍8🔥8
Showing the 12 most recent of 88 posts we hold for @thehackernews. 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 — 63,113 of 1,151,006entries 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.
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 1 registered channel — 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“The Hacker News” (@thehackernews), 162,047 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/thehackernews.
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.