https://github.com/quarkslab/proxyblob

Channel
ALTALSEC
@altalsec
On this record: Topic · Growth · Engagement · Posts · Cite this entry
481subscribers
-11 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 |
|---|---|
| Type | Channel |
| Username | @altalsec |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Oct 2026, 20:20 | 481 | -3 |
| 26 Sept 2026, 13:01 | 484 | -3 |
| 10 Sept 2026, 19:00 | 487 | -4 |
| 1 Sept 2026, 19:04 | 491 | -2 |
| 25 Aug 2026, 00:48 | 493 | +1 |
| 8 Aug 2026, 04:20 | 492 | no change |
| 7 Aug 2026, 20:10 | 492 | first 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
https://www.aikido.dev/blog/xrp-supplychain-attack-official-npm-package-infected-with-crypto-stealing-backdoor
https://github.com/slainwalker/defend-and-detect/tree/main
https://eshard.com/posts/emulating-ios-14-with-qemu
https://cyberalerts.io/vulnerabilities
https://github.com/prodaft/malware-ioc/blob/master/Lucid/README.md
https://www.silentpush.com/blog/russian-intelligence-phishing/
https://www.wietzebeukema.nl/blog/bypassing-detections-with-command-line-obfuscation
https://think-awesome.com/download_unitree_report
https://github.com/DarkSpaceSecurity/SSH-Stealer
https://www.cert.ssi.gouv.fr/cti/CERTFR-2025-CTI-004/
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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“ALTALSEC” (@altalsec), 481 subscribers as measured 7 October 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.