Telegram RegisterThe public register of Telegram
Telegram profile photo for T00ls公开频道 | T00ls.com | 低调求发展,潜心习安全!

Channel

T00ls公开频道 | T00ls.com | 低调求发展,潜心习安全!

@T00lsCom

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

4,624subscribers

+251 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001793798727
TypeChannel
Username@T00lsCom
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live25 September 2026
Measurements held15
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/T00lsCom

Topic

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 13 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.

Growth

4,3734,6244,498.56 August 2026 — 4,373 subscribers6 August 2026 — 4,373 subscribers7 August 2026 — 4,377 subscribers10 August 2026 — 4,395 subscribers13 August 2026 — 4,509 subscribers17 August 2026 — 4,508 subscribers20 August 2026 — 4,525 subscribers24 August 2026 — 4,547 subscribers27 August 2026 — 4,561 subscribers30 August 2026 — 4,568 subscribers3 September 2026 — 4,576 subscribers9 September 2026 — 4,582 subscribers13 September 2026 — 4,589 subscribers17 September 2026 — 4,603 subscribers25 September 2026 — 4,624 subscribers6 August 202625 September 2026
15 measurements spanning 50 days, net +251. 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 4,335–4,662 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Sept 2026, 12:194,624+21
17 Sept 2026, 07:194,603+14
13 Sept 2026, 07:584,589+7
9 Sept 2026, 03:364,582+6
3 Sept 2026, 09:394,576+8
30 Aug 2026, 17:134,568+7
27 Aug 2026, 06:354,561+14
24 Aug 2026, 02:284,547+22
20 Aug 2026, 04:334,525+17
17 Aug 2026, 12:564,508-1
13 Aug 2026, 23:454,509+114
10 Aug 2026, 13:434,395+18
7 Aug 2026, 11:564,377+4
6 Aug 2026, 14:464,373no change
6 Aug 2026, 14:374,373first reading

Engagement

22 posts held, back to 22 July 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 6 pages 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 22 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

3 reactions across 2 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤3100.0%

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 3 of the 22 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 22 most recent posts we hold, published 22 July 2026 to 7 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.

Recent posts

7 Aug 2026, 16:30 UTC337 viewsread 8 August 2026
Photo

安装广告拦截插件的重要性:广告公司Adform遭攻击 黑客在植入恶意代码劫持加密钱包(作者:weak_hong) 安装广告拦截插件的重要性:广告技术平台 Adform 在 7 月 27 日被攻击,黑客在广告代码里添加恶意代码劫持加密货币钱包。根据调查,用户只需要访问加载 Adform 广告代码的网站,恶意代码就会劫持剪贴板和输入框等,然后替换用户复制的钱包地址。如果用户安装广告拦截插件,那完全没影响,因为恶意代码也会被拦截。

Signed T00lsBot

7 Aug 2026, 14:30 UTC324 viewsread 8 August 2026

T00ls.com | 低调求发展,潜心习安全! 攻防博弈思路(作者:Mr靳传良)

Signed T00lsBot

6 Aug 2026, 08:30 UTC574 viewsread 8 August 2026
Photo

举报用户存在黑灰产问题(作者:赵振天)

Signed T00lsBot

5 Aug 2026, 21:30 UTC609 viewsread 8 August 2026
Photo

TA488 利用 Outlook 漏洞 CVE-2026-42897 部署 OWAReaper 后门程序(作者:jxmriri) 威胁组织 TA488 正利用 Microsoft Outlook Web Access(OWA)中的跨站脚本(XSS)零日漏洞 CVE-2026-42897 发起新一轮攻击,通过精心伪装的电子邮件部署名为 OWAReaper 的 JavaScript 后门。该恶意程序可在 OWA 运行,并具备持久化、窃取凭证及滥用邮箱权限等功能,攻击完成后还会自动清除痕迹,以降低被发现的风险。

Signed T00lsBot

5 Aug 2026, 04:30 UTC661 viewsread 8 August 2026
Photo

Google 删除了 3 个 ADK AI 工作流;此前恶意 GitHub Issue 可触发高权限 AI 代理(作者:ranran) Google 已删除 ADK Python 代码库中的三个 AI 代理工作流。此前 Pillar Security 发现,攻击者可通过提示词注入绕过权限检查来利用公开的 GitHub Issue,触发高权限自动修复流程,并在概念验证中实现 CI 环境代码执行及获取敏感凭证。Google 已修复该问题,目前没有证据显示漏洞遭实际利用或会影响 ADK 正式发布的版本。

Signed T00lsBot

5 Aug 2026, 02:30 UTC616 viewsread 8 August 2026
Photo

研究人员披露新劫持方法:本地恶意软件可以劫持Chrome同步的通行密钥(作者:sasser) 研究人员发布报告披露谷歌浏览器内置密码管理器同步 Passkey 存在的安全缺陷,在本地植入恶意软件的情况下,可以劫持用户登录。这种攻击方式并非破解通行密钥,而是滥用设备信任机制绕过原本应该由用户进行的 PIN、指纹或面容识别认证,攻击过程也不需要管理员权限。

Signed T00lsBot

4 Aug 2026, 05:30 UTC710 viewsread 8 August 2026
Photo

研究人员发布 GitLab 的远程代码执行 PoC,使已认证用户能够以 Git 身份执行命令(作者:ranran) 研究人员公开了 GitLab RCE PoC,在未升级的自托管 GitLab(18.11.3 等受影响版本)中,任何已认证的用户并具有项目 Push 权限的都可利用 Notebook Diff 漏洞链,以 git 用户身份执行任意命令。官方建议尽快升级至 18.10.8、18.11.5 或 19.0.2,目前暂无有效缓解措施。

Signed T00lsBot

2 Aug 2026, 08:30 UTC≈1,300 viewsread 8 August 2026
Photo

Chrome近期3个版本修复1,442个漏洞 比之前23个版本修复的漏洞总和还多😬😬(作者:sasser) 谷歌透露 Chrome 近期 3 个版本合计修复 1,442 个漏洞,比之前 23 个版本修复的漏洞总和还多。具体来说在 6 月发布的 149/150 版中谷歌修复 1,072 个漏洞,而 126~148 合计修复的漏洞都没超过 1,000 个。如此快的漏洞发掘速度自然是靠 AI 实现的,无论是谷歌还是安全公司现在都在积极使用 AI 发掘漏洞。

Signed T00lsBot

31 Jul 2026, 04:30 UTC≈1,050 viewsread 8 August 2026
Photo

零日漏洞遭攻击者利用,静态凭据可能导致敏感数据泄露(作者:ranran) 美国 CISA 已将 Cisco Secure FMC 软件漏洞 CVE-2026-20316 列入已知遭利用漏洞(KEV)目录。该漏洞允许攻击者利用内置低权限账户远程登录受影响设备,并可与其他漏洞串联实现权限提升甚至代码执行。Cisco 已发布热修复程序,并建议用户尽快升级,同时检查设备是否存在遭利用迹象。

Signed T00lsBot

31 Jul 2026, 02:30 UTC948 viewsread 8 August 2026
Photo

苹果称已经修复iCloud+隐藏邮箱地址功能会泄露用户真实邮箱地址的漏洞(作者:sasser) 苹果称已经彻底修复 iCloud+ 隐藏邮箱地址会泄露用户真实邮箱地址的漏洞,这回是真修复了!该漏洞最初是安全研究员泰勒墨菲在 2025 年 6 月发现的,通报给苹果后,苹果确实修复了漏洞但并不彻底,以至于仍然会泄露用户邮箱。日前苹果发布回应称已经在 7 月 3 日部署补丁,该问题已经完全解决。

Signed T00lsBot

30 Jul 2026, 14:30 UTC886 viewsread 8 August 2026
Photo

护网是来干活挣钱的,住宿只是睡觉的地方,不值得为这种玩意儿消耗情绪(作者:EnHkekit-Search)

Signed T00lsBot

30 Jul 2026, 03:30 UTC859 views0 reactionsread 8 August 2026

T00ls.com | 低调求发展,潜心习安全! 现在挖洞真难啊,(作者:wuyanzu)

Signed T00lsBot

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

Forward network

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.

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

“T00ls公开频道 | T00ls.com | 低调求发展,潜心习安全!” (@T00lsCom), 4,624 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/T00lsCom.

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.