Telegram RegisterThe public register of Telegram
Telegram profile photo for Web3 反诈联盟

Channel

Web3 反诈联盟

@tgScamExposure

On this record: Topic · Growth · Engagement · Reactions · Posts · Handles named that no longer answer · Cite this entry

28subscribers

-2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002415092074
TypeChannel
Username@tgScamExposure
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live13 November 2026
Measurements held4
Confirmed unchanged3 times, most recently 13 November 2026
On Telegramt.me/tgScamExposure

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 20 October 2026 and assigned it the closest of 31 fixed categories, at 56% 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 the other topics.

Growth

2830297 August 2026 — 30 subscribers11 August 2026 — 30 subscribers20 October 2026 — 29 subscribers28 October 2026 — 28 subscribers7 August 202628 October 2026
4 measurements spanning 82 days, net -2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 28–30 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Oct 2026, 07:3928-1
20 Oct 2026, 15:4029-1
11 Aug 2026, 04:1630no change
7 Aug 2026, 17:5330first reading

Engagement

20 posts held, back to 11 May 2025 — 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 page of 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 24 April 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

6 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 83.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤583.3%
👍116.7%

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 6 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 6 reactions 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 11 May 2025 to 24 April 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.

Recent posts

24 Apr 2026, 08:46 UTC399 viewsread 11 August 2026

🚨 警告:假U / 黑U / 冻U = 一不小心直接归零 现在骗子已经进化到“几乎无法分辨”: 在 TokenPocket、imToken 等钱包里: 能转账 ✅ 有余额 ✅ 链上可查 ✅ 界面完全一致 ✅ 👉 看起来100%是真的 但结局只有一个: ❌ 提不了现 ❌ 交易所不认 💸 手续费却是真的(全被骗子拿走) 🧠 三种坑一眼看懂 冻U:官方冻结,永远转不走 黑U:能转,但一进交易所就封号 假U:完全假币,只能“自嗨转账” 🛡 保命三条 🚫 来源不明的U一律别碰 🔍 必须上交易所验证 💻 大额别用插件钱包(尤其Windows) ⚠️ 一句话 链上能查 ≠ 钱是真的 越逼真,越可能是骗局 来源:https://x.com/33357xyz/status/2044627383752552882

6 Mar 2026, 04:08 UTC352 viewsread 11 August 2026

🚨警惕虚假 imToken Chrome 扩展程序 Chrome 应用商店一个虚假 imToken Chrome 扩展程序,会钓鱼获取种子短语和私钥。

26 Dec 2025, 09:08 UTC368 viewsread 11 August 2026

🚨 严重安全警报|Trust Wallet 浏览器扩展 2.68 疑遭供应链攻击,恶意代码窃取助记词,损失已超 600 万美元 📍 事件概况 据 Trust Wallet 官方、链上侦探 ZachXBT,以及安全研究者 @im23pds / @0xakinator / 余弦 综合分析,Trust Wallet 浏览器扩展 v2.68 疑似遭遇供应链攻击,被植入恶意代码,导致大量用户资产被盗,初步统计损失已超 600 万美元。 📍 核心技术细节(已确认) 恶意代码位于扩展文件 4482.js 该代码伪装成分析 / 统计工具 当用户在扩展中 导入钱包(输入助记词) 时: 助记词会被 直接发送到钓鱼域名: metrics-trustwallet[.]com 该域名为新注册钓鱼域名,目前已无法访问 ➡️ 结论: 这是一次明确的助记词级别泄露,攻击者可完全控制钱包资产。 📍 攻击时间线(余弦预估) 12.8:攻击者开始准备(基…

21 Dec 2025, 04:40 UTC229 viewsread 11 August 2026

🚨 安全警报|GitHub 开源项目藏恶意依赖,Polymarket 跟单机器人窃取私钥 某 Polymarket 跟单交易机器人 开发者在 GitHub 发布恶意开源项目,并非在主代码中直接植入后门,而是刻意引入其自行编写的恶意依赖包,具有极强隐蔽性。 该恶意依赖会在程序运行时自动读取用户 .env 文件中的 钱包私钥、CEX / DEX API Key,并将敏感信息上传至黑客服务器,导致资产被直接盗取。 值得注意的是,单独审查主仓库源码或使用 AI 扫描极难发现异常,因恶意逻辑完全隐藏在依赖包中。该项目作者还多次修改提交记录,刻意掩盖作恶行为。 慢雾科技首席信息安全官 23pds 警示称:此类“依赖投毒式”攻击 并非首次出现,也绝不会是最后一次。 🛡 安全建议 • 谨慎使用涉及资金的 GitHub 开源项目 • 不明来源项目不要直接运行 • 核查所有依赖包来源与代码 • 涉及私钥 / API Key 项目优先自行实…

17 Dec 2025, 06:51 UTC204 viewsread 11 August 2026

🚨警告:Windows 电脑 + 插件钱包 = 高风险组合 BitsLab 最近发现 十多个主流 Chrome 插件钱包 中都存在同一个严重漏洞,可能被用于 直接窃取私钥。 ⚠️受影响的钱包包括: Coinbase Wallet 插件版 Binance Wallet 插件版 以及多款头部插件钱包 虽然该漏洞的利用需要特定条件,但 一旦触发就是全额资产被盗 的级别。 🛡安全建议: Windows 电脑上 勿在插件钱包中操作大资金 兑换、划转、创建账户等敏感操作尽量用 硬件钱包 / 手机冷环境 插件钱包仅用于小额、日常操作 等修复发布后 BitsLab 会第一时间披露细节 原文链接:https://x.com/0xyilu/status/2000947033386225811

16 Dec 2025, 07:36 UTC178 views1 reactionsread 11 August 2026

🚨警报:用户因签署恶意 “permit” 签名,被盗走价值 $563,590 的 aEthUSDT! 一名用户在误签恶意 permit 授权 后,资产被攻击者瞬间转走。 这种攻击无需用户发起转账,只要签一次“授权”,攻击者即可调用代币并清空余额。 📌受害者地址 0xC782Fde5962d5627e0366520f768e6143Dc646d0 🦹攻击者地址 0xbb4223Ef4cCe93fB40beb62178aBE9A666f682aF 0xCa056cc070CdEEBfa7212BD099344A3E9c82F3d7 🧨攻击手法简述 通过伪装的 DApp 或钓鱼链接诱导用户签署 permit 或 increaseApproval 用户看到的只是“看似正常的授权” 实际攻击者获得代币无限额度授权,立即转走全部资产 ➡️ 一次签名 = 整个钱包余额的授权 🛡如何保护自己 仔细核对每一次签名请求内容 …

❤1

16 Dec 2025, 03:48 UTC155 views0 reactionsread 11 August 2026

🚨警报:黑客利用 React 漏洞向加密网站注入恶意脚本,诱导用户签名盗币! 网络安全组织 SEAL 披露,攻击者正大规模利用 React CVE-2025-55182 漏洞,在合法加密网站的前端植入恶意 JavaScript,用来伪装弹窗、奖励提示或钱包授权界面,诱骗用户签署恶意交易。 📌攻击关键点 受影响模块包含:react-server-dom-webpack、react-server-dom-parcel、react-server-dom-turbopack 漏洞允许远程代码执行,攻击者可直接在网站前端注入代码 黑客模仿真实 UI,引导用户批准“签名”,实则发起盗币操作 最近几天,被上传到合法网站的窃取程序数量 显著增加 🧨谁处于风险? 使用 React Server Components 的加密网站 / Web3 项目 访问这些网站并看到突然出现的签名请求的用户 任何允许钱包连接、交易签名的前端界面…

28 Nov 2025, 01:56 UTC249 views1 reactionsread 11 August 2026

🚨警报:恶意 Chrome 插件“Crypto Copilot”偷偷从 Solana 交易中抽佣! 网络安全公司 Socket 披露,一个名为 Crypto Copilot 的 Chrome 插件允许用户在 X(推特)上直接交易 Solana,但会在每次 swap 中悄悄添加一笔隐藏转账,把资金划给攻击者。 📌攻击特点 插件伪装为便捷工具,让用户无需离开 X 就能交易 Solana 实际每次 swap 都会: ✔️ 使用 Raydium 完成正常交易 ✔️ 偷偷追加一条转账指令 → 抽走 0.0013 SOL 或 0.05% 交易额 钱包签名界面只显示“单笔交易摘要”,不展示隐藏指令 ➡️ 用户以为只是普通 swap,实际上签了两条链上指令 📍扩散情况 上架于 2024年6月18日 表面仅 15 名用户,但可能实际存在更广泛影响 Socket 已向 Chrome Web Store 提交下架请求 ⚠️Chro…

❤1

20 Nov 2025, 06:26 UTC201 viewsread 11 August 2026

🚨警报:WhatsApp 正爆发“蠕虫 + 银行木马”双重攻击,专偷加密钱包与银行账户! 恶意软件 Eternidade Stealer 通过 WhatsApp 链接传播 伪装成政府补贴、快递通知、朋友消息、投资群等常见内容 点击后会安装: ✔️ 蠕虫:劫持 WhatsApp、自动向联系人传播 ✔️ 银行木马:窃取巴西银行、交易所、加密钱包凭证 木马使用 Gmail 作 C2,指令可随邮件更新,极难封杀 目标主要是加密用户与巴西银行体系 🛡如何防护 不要随便打开 WhatsApp 链接,即使来自朋友 用其它 App 再确认对方是否真的发送 保持系统与 App 更新 若疑似中招:立即冻结银行/交易所访问,转移钱包资金

17 Nov 2025, 08:15 UTC185 viewsread 11 August 2026

🚨警报:部分使用 @nofx_ai 自动交易系统的用户出现私钥与 API Key 泄露事件!🚨 📍 说明 必须先强调:NOFX AI 本身作为开源项目整体较为良心,代码公开透明。 但我们此前披露的潜在风险,如今已经出现真实的盗币事件。 📌事件概况 已有部分使用者遭遇 钱包私钥泄露 部分用户的 CEX / DEX API Key 也疑似被窃取 风险来源与使用者本地环境、部署方式、第三方依赖等因素相关 🛡风险提示 若使用 @nofx_ai,请立即排查: 📌 是否曾在服务器明文保存私钥 📌 是否暴露 API Key 至日志、环境变量、前端 📌 是否使用来源不明的 fork 或脚本 📌 部署环境是否存在木马 / 恶意包 建议立即: 🚫 重置所有 API Key 🚫 迁移钱包资产至新地址 🚫 审计本地与服务器依赖环境

16 Oct 2025, 01:30 UTC326 views1 reactionsread 11 August 2026

🚨 警报:朝鲜黑客向 npm 上传超 300 个恶意包,窃取密码与加密钱包密钥🚨 据 Decrypt 报道,美国网络安全公司 Socket 披露,朝鲜黑客组织近期向主流软件库 npm 上传了 300+ 个恶意代码包,通过伪装成热门库(如 express、hardhat)的拼写错误版本,诱导开发者误装,进而窃取密码与加密钱包私钥。 🧠 攻击行动名称 “传染性面试”(Contagious Interview) —— 黑客冒充 Web3 / 区块链公司招聘人员,诱骗开发者下载被感染的依赖包。 🔍 攻击特征 恶意包 伪装成常见依赖库的拼写错误版本(如 expreess、hardhat-kit)。 已被下载约 5 万次,部分包仍在线。 加载器脚本采用 内存解密技术(memory decryption),规避静态检测与取证。 溯源分析确认其代码模式与 朝鲜黑客组织 活动一致。 🧩 当前应对 GitHub 与 npm 官方…

❤1

Showing the 12 most recent of 20 posts we hold for @tgScamExposure. 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.

Cite this entry

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 28 October 2026 — this entry's latest reading, not the date you are reading this.

“Web3 反诈联盟” (@tgScamExposure), 28 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/tgScamExposure.

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.