Telegram RegisterThe public register of Telegram
Telegram profile photo for Zero Trust Hackers . Cyber Security . Hacking Resources . Bug Bounty . Hacks

Channel

Zero Trust Hackers . Cyber Security . Hacking Resources . Bug Bounty . Hacks

@zerotrusthackers

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

2,411subscribers

+14 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002438372390
TypeChannel
Username@zerotrusthackers
CreatedBetween 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live21 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 21 August 2026
On Telegramt.me/zerotrusthackers

Growth

2,3972,4112,4047 August 2026 — 2,397 subscribers7 August 2026 — 2,397 subscribers8 August 2026 — 2,398 subscribers11 August 2026 — 2,403 subscribers14 August 2026 — 2,406 subscribers17 August 2026 — 2,409 subscribers21 August 2026 — 2,411 subscribers7 August 202621 August 2026
7 measurements spanning 13 days, net +14. 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 2,395–2,413 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
21 Aug 2026, 04:562,411+2
17 Aug 2026, 19:392,409+3
14 Aug 2026, 07:132,406+3
11 Aug 2026, 07:382,403+5
8 Aug 2026, 01:462,398+1
7 Aug 2026, 20:172,397no change
7 Aug 2026, 19:022,397first reading

Engagement

20 posts held, back to 14 January 2026the 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.

ERR · 30 days
17.4%
avg views ÷ 2,411 subscribers
Avg views / post
420
3 posts measured
Reaction rate
0.238%
reactions ÷ views · ER floor
Posts in window
3
of 20 held

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. It is computed over the 1 of 3 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 28 July 2026
Posts held20 (14 January 202628 July 2026)
Views total1,260
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 20:17 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.

Reaction mix

14 reactions across 7 posts, in 3 distinct kinds. The most used accounts for 78.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1178.6%
😁214.3%
🥰17.14%

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 9 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 14reactions 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 14 January 2026 to 28 July 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

28 Jul 2026, 16:20 UTC420 viewsread 7 August 2026
Photo

📚BOOK ChatGPT for CyberSecurity #2 by Joas Antonio dos Santos

28 Jul 2026, 16:19 UTC421 views1 reactionsread 7 August 2026
Photo

📚BOOK 2026 TD State of Malware by ThreatDown

1

28 Jul 2026, 16:18 UTC419 viewsread 7 August 2026
Photo

📚BOOK Pentesting Lab Active Directory by Felix, Possegger, Pongratz, Prodinger, Schauklies, Schwarzl

24 Jun 2026, 19:28 UTC559 views1 reactionsread 7 August 2026
Forwarded from @intercomuniversity

Microsoft's Secret Stash of 100+ Free Courses You Need to Know About * Microsoft Azure * Artificial Intelligence * Cybersecurity * Data Analytics * Software Development * Cloud Computing * Power Platform * Database Technologies Link 👉 :- https://intercomuniversity.com/free-courses/development/microsofts-secret-stash-of-100-free-courses-you-need-to-know-about/ Enroll for FREE

1

23 Apr 2026, 15:08 UTC979 views5 reactionsread 7 August 2026

Anthropic’s cybersecurity AI was reportedly breached on launch day. Claude Mythos — built for enterprise security — was accessed by a Discord group that reverse-engineered its system and got in through a third-party contractor. Anthropic had restricted it to vetted partners under Project Glasswing, including Apple. The incident has triggered global attention, with financial regulators and security agencies now mon

2😁2🥰1

2 Apr 2026, 15:57 UTC≈1,060 views3 reactionsread 7 August 2026
Forwarded from @techpsyche

Here's a List Of 50 Different Cybersecurity Careers 1. Security Analyst 2. Penetration Tester 3. Security Consultant 4. Incident Responder 5. Security Engineer 6. Ethical Hacker 7. Security Architect 8. Malware Analyst 9. Cryptographer 10. Security Administrator 11. Network Security Engineer 12. Security Auditor 13. Security Operations Center (SOC) Analyst 14. Threat Intelligence Analyst 15. Security Compliance Anal

3

1 Apr 2026, 09:53 UTC778 viewsread 7 August 2026
Forwarded from @techpsychePhoto

npm leakage mercor leak liteLLM compromised Claude code source code leak railway CDN problem axios package compromised delve leaked customer data All over the past 7 days

1 Apr 2026, 09:51 UTC737 viewsread 7 August 2026
Forwarded from @techpsyche

Claude code fork repositories have been taken down https://github.com/nirholas/claude-code

31 Mar 2026, 18:30 UTC552 views1 reactionsread 7 August 2026
Forwarded from @techpsychePhoto

⚠️One of npm's most depended-on packages has been attacked!!

1

31 Mar 2026, 14:55 UTC560 viewsread 7 August 2026
Forwarded from @freecoursescentre

4 Microsoft Free Courses: AI, Data Science, IoT and Machine Learning 🚀 Gain/Upskill your tech skills with these free micsoroft courses✨ * Artificial Intelligence (AI) * Internet of Things (IoT) * Machine Learning (ML) * Data Science Link👇:- https://cutt.ly/XtAvtTCA 🔗 Start Learning Today!

30 Mar 2026, 19:17 UTC839 viewsread 7 August 2026
Photo

🛑 Two OpenAI flaws showed how AI systems can expose sensitive data. 🔸 One allowed silent leaks via a DNS side channel in ChatGPT 🔸 Another enabled GitHub token theft via Codex injection 🛡 t.me/zerotrusthackers

30 Mar 2026, 13:07 UTC530 views0 reactionsread 7 August 2026
Forwarded from @techpsyche

Books and tutorials are great, but nothing teaches you faster than getting your hands dirty. Even the tiniest project, a to-do app, a note saver or a random quote generator, forces you to: Think through problems step by step Debug real issues (not textbook ones) See how code fits together in the real world Small projects = fast feedback = massive growth. 🔆 t.me/techpsyche

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

Citation-graph rank — 1,100,334 of 1,584,733entries 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.

Forward network

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.

Mentions

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.

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

“Zero Trust Hackers . Cyber Security . Hacking Resources . Bug Bounty . Hacks” (@zerotrusthackers), 2,411 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/zerotrusthackers.

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.