Channel
@web3secnews
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,370subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002006893879 |
|---|---|
| Type | Channel |
| Username | @web3secnews |
| Created | Between 1 November 2023 and 30 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/web3secnews |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 07:14 | 2,370 | +1 |
| 8 Aug 2026, 11:15 | 2,369 | -1 |
| 7 Aug 2026, 15:47 | 2,370 | first reading |
20 posts held, back to 25 March 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 1 pageof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.
62 reactions across 19 posts, in 17 distinct kinds. The most used accounts for 21.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👏 | 13 | 21.0% | |
| ❤ | 12 | 19.4% | |
| 🔥 | 8 | 12.9% | |
| 👍 | 6 | 9.68% | |
| 👀 | 5 | 8.06% | |
| 🙏 | 2 | 3.23% | |
| 🤔 | 2 | 3.23% | |
| 🤝 | 2 | 3.23% | |
| 🤡 | 2 | 3.23% | |
| 🤯 | 2 | 3.23% | |
| 🫡 | 2 | 3.23% | |
| ⚡ | 1 | 1.61% | |
| 👌 | 1 | 1.61% | |
| 👎 | 1 | 1.61% | |
| 💩 | 1 | 1.61% | |
| 🗿 | 1 | 1.61% | |
| 😁 | 1 | 1.61% |
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 19 of the 20 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 62reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 25 March 2026 to 29 June 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.
Quick one for the builders here. Polymarket lost ~$3M last week and it wasn't their contracts or servers.. a third-party script on their frontend got compromised and changed what users were signing. Same story as Badger, Ledger Connect Kit, Balancer, the npm drainers. You can't fully control everything on your own domain, so it has to be monitored. That's what we've been building VANTAGE for, now in alpha with beta …
👌1👏1🤡1😁1
hey folks, been getting quite a few messages around this so put it all together --> web3sec roadmap + AI-era path for anyone getting into this. drop improvements via PR if any, tried to make it short, clear and actionable. https://x.com/__Raiders/status/2059294222600294845
❤2👏2👎1🔥1
Hey everyone! Just a quick reminder that today is the last day to support our Ethereum security quadratic funding on Giveth. If you can spare a $ in donation, it will be matched, which means we'll be able to continue doing awesome research and developing tools for the crypto community. Web3sec news: https://qf.giveth.io/project/web3secnews:-security-intelligence-newsletter Digibastion: https://qf.giveth.io/project…
👍1👏1🔥1
hey fam, Web3Sec.News and DigiBastion.com both projects made it into the thedaofund Ethereum Security QF Round on Giveth 🎉 500 ETH matching pool, voting open until May 14. Even $1 from a unique donor makes a real difference. 🔗 web3sec_news: https://qf.giveth.io/project/web3secnews:-security-intelligence-newsletter 🔗 DigiBastion: https://qf.giveth.io/project/digibastion:-dns-opsec-supply-chain-security Full detai…
👏2⚡1❤1
cow.fi got hijacked recently, so did hypurr.fi, and neutrl.fi - all in the same few weeks, all through DNS, none through code. we saw someone also survive an attempted attack on our own domain. caught it in 30 seconds. here's the full breakdown: ✦ how the attack chain works (registrar → ns swap → valid cert → live phishing) ✦ our field report — what we did in the first 10 mins ✦ 4 attacker TTPs extracted from confi…
❤1
Protecting Crypto Domains and Infra: A Guide to Defending Against DNS Hijacking and BGP Attacks A detailed guide by vladimir https://x.com/i/status/2044147555618173261
❤2👍2👏2
For affected users: Revoke everything at revoke.cash, focus on CoW Protocol router contracts. Move funds out of any wallet connected to cow.fi today. Stay safe. https://x.com/__Raiders/status/2044106026321096751
👀1
🚨 CONFIRMED: cow[.]fi (CoW Swap) is under an ACTIVE supply chain attack. If you connected your wallet to cow.fi today — REVOKE ALL APPROVALS NOW. → revoke.cash → etherscan.io/tokenapprovalchecker …
🤔1
honoured to be selected for the ETHSecurity Badge holder already heads down building at digibastion, dns security, live threat intel, supply chain and phishing tooling, opsec guides... a lot coming together a lot of work ahead but excited to contribute to the DAO https://x.com/i/status/2043883600152801651
you're NOT even aware of the types of hacks & exploits POSSIBLE through third-party packages, existing code, binaries, SDKs, and projects whose code is NEVER visible - yet broadly TRUSTED and used. and with vibe coding across AI tools and different LLMs, new attack surfaces are opening up that can lead to FULL infra compromise & data exfiltration. give it 1-2 years & it'll click for most people. everything is a ma…
👀1🤔1🤯1🫡1
Been working on something quietly over the past few months. I built an internal Domain and DNS security intelligence scanner to help teams stay protected from domain hijacking, DNS misconfigurations, registrar issues, and other overlooked risks. This came from seeing the same thing again and again. Critical domains getting compromised not because of complex exploits, but because of simple gaps in DNS or registrar s…
🔥2❤1👏1🙏1
Most audit tools pattern match. guardix maps your architecture first. invariants, assumptions, design decisions. then hunts for violations. Every finding is backed by a verified exploit. audit runs are versioned. fix, re-audit, see exactly what changed. 1 free solidity audit after signup. If you've been vibe coding contracts, now's a good time to check what you're about to ship. → https://guardix.io
❤2👏1💩1🔥1
Showing the 12 most recent of 20 posts we hold for @web3secnews. 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 — 1,087,562 of 1,183,361entries 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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“Web3 Security News” (@web3secnews), 2,370 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/web3secnews.
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.