Telegram RegisterThe public register of Telegram
Telegram profile photo for ALTALSEC

Channel

ALTALSEC

@altalsec

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

475subscribers

-17 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-1001425905281
TypeChannel
Username@altalsec
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live3 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 3 November 2026
On Telegramt.me/altalsec

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 21 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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

4754934847 August 2026 — 492 subscribers8 August 2026 — 492 subscribers25 August 2026 — 493 subscribers1 September 2026 — 491 subscribers10 September 2026 — 487 subscribers26 September 2026 — 484 subscribers7 October 2026 — 481 subscribers14 October 2026 — 480 subscribers21 October 2026 — 478 subscribers27 October 2026 — 477 subscribers3 November 2026 — 475 subscribers7 August 20263 November 2026
11 measurements spanning 88 days, net -17. 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 472–496 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
3 Nov 2026, 20:31475-2
27 Oct 2026, 14:06477-1
21 Oct 2026, 11:36478-2
14 Oct 2026, 14:38480-1
7 Oct 2026, 20:20481-3
26 Sept 2026, 13:01484-3
10 Sept 2026, 19:00487-4
1 Sept 2026, 19:04491-2
25 Aug 2026, 00:48493+1
8 Aug 2026, 04:20492no change
7 Aug 2026, 20:10492first reading

Engagement

20 posts held, back to 30 December 2024 — 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 30 April 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

23 Apr 2025, 05:25 UTC455 viewsread 8 August 2026

https://www.aikido.dev/blog/xrp-supplychain-attack-official-npm-package-infected-with-crypto-stealing-backdoor

1 Apr 2025, 18:53 UTC364 viewsread 8 August 2026

https://github.com/prodaft/malware-ioc/blob/master/Lucid/README.md

29 Mar 2025, 08:36 UTC337 viewsread 8 August 2026

https://www.silentpush.com/blog/russian-intelligence-phishing/

24 Mar 2025, 18:04 UTC328 viewsread 8 August 2026

https://www.wietzebeukema.nl/blog/bypassing-detections-with-command-line-obfuscation

12 Mar 2025, 08:04 UTC327 viewsread 8 August 2026

https://research.checkpoint.com/2025/blind-eagle-and-justice-for-all/

Showing the 12 most recent of 20 posts we hold for @altalsec. 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 3 November 2026 — this entry's latest reading, not the date you are reading this.

“ALTALSEC” (@altalsec), 475 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/altalsec.

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.