Telegram RegisterThe public register of Telegram
Telegram profile photo for Malware Hunters

Channel

Malware Hunters

@malwarehunters

Has discussion group

On this record: Topic · Growth · Engagement · Cite this entry

1,197subscribers

-22 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-1001649087886
TypeChannel
Username@malwarehunters
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded4 October 2026
Last confirmed live1 November 2026
Measurements held22
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/malwarehunters

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 4 October 2026 and assigned it the closest of 31 fixed categories, at 97% 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

1,1961,2201,2087 August 2026 — 1,219 subscribers8 August 2026 — 1,220 subscribers11 August 2026 — 1,218 subscribers14 August 2026 — 1,216 subscribers20 August 2026 — 1,215 subscribers24 August 2026 — 1,214 subscribers27 August 2026 — 1,213 subscribers30 August 2026 — 1,212 subscribers2 September 2026 — 1,208 subscribers10 September 2026 — 1,207 subscribers14 September 2026 — 1,205 subscribers18 September 2026 — 1,206 subscribers27 September 2026 — 1,200 subscribers4 October 2026 — 1,200 subscribers5 October 2026 — 1,199 subscribers12 October 2026 — 1,198 subscribers15 October 2026 — 1,197 subscribers18 October 2026 — 1,196 subscribers21 October 2026 — 1,198 subscribers27 October 2026 — 1,197 subscribers29 October 2026 — 1,198 subscribers1 November 2026 — 1,197 subscribers1,1977 August 20261 November 2026
22 measurements spanning 86 days, net -22. 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 1,192–1,224 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
1 Nov 2026, 12:171,197-1
29 Oct 2026, 20:361,198+1
27 Oct 2026, 01:571,197-1
21 Oct 2026, 05:501,198+2
18 Oct 2026, 12:041,196-1
15 Oct 2026, 12:451,197-1
12 Oct 2026, 11:081,198-1
5 Oct 2026, 14:221,199-1
4 Oct 2026, 04:261,200no change
27 Sept 2026, 19:151,200-6
18 Sept 2026, 11:161,206+1
14 Sept 2026, 07:221,205-2
10 Sept 2026, 17:551,207-1
2 Sept 2026, 02:221,208-4
30 Aug 2026, 07:491,212-1
27 Aug 2026, 09:291,213-1
24 Aug 2026, 14:541,214-1
20 Aug 2026, 16:221,215-1
14 Aug 2026, 17:091,216-2
11 Aug 2026, 05:341,218first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 1 November 2026 — this entry's latest reading, not the date you are reading this.

“Malware Hunters” (@malwarehunters), 1,197 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/malwarehunters.

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.