Photo, posted without a caption

Channel
Hunters
@hunters_sec
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,231subscribers
-4 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 | -1002524092060 |
|---|---|
| Type | Channel |
| Username | @hunters_sec |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/hunters_sec |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 15:38 | 1,231 | -3 |
| 5 Oct 2026, 14:15 | 1,234 | -6 |
| 27 Sept 2026, 21:59 | 1,240 | -3 |
| 15 Sept 2026, 10:17 | 1,243 | -2 |
| 11 Sept 2026, 23:55 | 1,245 | -1 |
| 2 Sept 2026, 04:15 | 1,246 | +3 |
| 30 Aug 2026, 13:38 | 1,243 | +5 |
| 24 Aug 2026, 08:59 | 1,238 | +2 |
| 17 Aug 2026, 09:36 | 1,236 | -1 |
| 14 Aug 2026, 00:15 | 1,237 | +3 |
| 10 Aug 2026, 22:04 | 1,234 | -1 |
| 7 Aug 2026, 12:26 | 1,235 | no change |
| 7 Aug 2026, 12:02 | 1,235 | first reading |
Engagement
15 posts held, back to 8 June 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 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 15 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
28 reactions across 9 posts, in 4 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 16 | 57.1% | |
| 🔥 | 6 | 21.4% | |
| 🍓 | 4 | 14.3% | |
| ⚡ | 2 | 7.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 10 of the 15 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 28 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 8 June 2026 to 3 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
Yet again another Samsung 0-day iced
This bug would allow a remote attacker to send specially crafted SMS messages and corrupt memory on a target device. We have reported over 4 similar memory bugs that, when used together in a chain, could lead to full remote access on Samsung devices.
🔥1
Yet again another 0 day has been approved by Samsung try the GLM 5.2 uncensored model by cyberneurova https://cyberneurova.ai
🔥2
Get the latest Cyberneurova Desktop application with alot of the major updates including proper support for agentic work using cyberneurova-GLM5.2 model get the latest app on V0.1.12 https://cyberneurova.ai/downloads
Samsung just confirmed another reward for a bug we found 26 days ago.
❤5🍓4
Try out the DeepSeek model, a more efficient and top stable model we have added. https://cyberneurova.ai/
Hunters supports normal pentests on networks, web, and applications, reverse engineering on APKs, binaries, and code analysis. Hunters also uses CyberNeurova models which are uncensored and will come in handy during your research, currently supporting DeepSeek models.
❤2🔥1
Hunters has capabilities of helping researchers write working exploits for any CVE ever reported. This makes work for security researchers super simple and fun. We have also integrated functions where, by giving Hunters a dataset, it checks the technologies the platform was built on and will give you detailed info if there are any potential vulnerable code in them.
❤1
Hunters is now open — and getting in is simple We’ve made it easy for anyone to get access to Hunters, the autonomous AI pentester for offensive security. Two ways to register: 🌐 Individual or company with a domain Add your domain and verify you own it (DNS record, file upload, or meta tag). Once verified, you get direct access — no waiting — to pentest your own assets. 🏴☠️ Bug bounty hunter Submit a request with th…
⚡2❤2
GLM 5.2 cyberBench results on security research
Hunters through CyberNeurova have submitted over 32 zero-day vulnerabilities to Samsung. Out of these, Samsung has verified most of them, while the rest are still under review. This process has been ongoing for more than five months. We began reporting vulnerabilities in February, when we submitted our first batch of 7 vulnerabilities, all of which Samsung validated. Later, at the beginning of June, we submitted a …
❤4
Showing the 12 most recent of 15 posts we hold for @hunters_sec. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Hunters” (@hunters_sec), 1,231 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/hunters_sec.
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.