BOTNET - AESBOT pinned «Weekly card 1000 USDT/100 times a day, 60 seconds attack»

Channel
BOTNET - AESBOT
@botnet1t
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
99subscribers
-6 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 | -1001723232298 |
|---|---|
| Type | Channel |
| Username | @botnet1t |
| Created | Between 1 October 2021 and 11 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 2 times, most recently 9 November 2026 |
| On Telegram | t.me/botnet1t |
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 26 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 01:16 | 99 | -2 |
| 27 Oct 2026, 08:06 | 101 | -1 |
| 20 Oct 2026, 12:59 | 102 | -1 |
| 7 Oct 2026, 15:14 | 103 | -1 |
| 27 Sept 2026, 12:41 | 104 | -4 |
| 29 Aug 2026, 09:56 | 108 | +3 |
| 9 Aug 2026, 09:02 | 105 | no change |
| 7 Aug 2026, 01:46 | 105 | first reading |
Engagement
20 posts held, back to 11 October 2021 — 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 7 March 2023. An engagement rate over an empty window would be a number about nothing.
Recent posts
Weekly card 1000 USDT/100 times a day, 60 seconds attack
BOTNET - AESBOT pinned «If you are interested in BOTNET do not hesitate to contact me(@rpp33), Actually the power is around 1Tbps +- only serious people.»
如果您对 BOTNET 感兴趣,请不要犹豫与我联系(@rpp33),实际上功率大约为 1Tbps + - 只有认真的人。
If you are interested in BOTNET do not hesitate to contact me(@rpp33), Actually the power is around 1Tbps +- only serious people.
大家好! 自11月以来,我们一直很忙,没有在旧的僵尸网络上工作,因为它被废弃了,我一直在为linux从头开始工作,新的功能将被添加,新的攻击类型,我会让你们知道,当僵尸在线开放销售,显然,我们将回来与市场上最好的力量,一如既往地。 新年快乐! 现在我们的恶意软件/机器人被称为。AES,因为我们使用AES来加密字符串、流量和其他
Hello everybody! Since November we have been busy and have not been working on the old botnet as it is deprecated and I have been working on a new bot for linux from scratch, new features will be added, new types of attacks I will let you guys know when the bot is online to open sales, obviously we will be back with the best power on the market, as always. happy new year! Now our malware/bot is called: AES, becau…
Photo, posted without a caption
CLOUDFLARE 2Tbps 🥶
path network
今天我们进行了更新并修复了CNC和代理机器人之间的连接错误,电源稳定+ 1Tbps UDP,300Gbps SYN & ACK
我们正在更新僵尸网络以增加力量
Showing the 12 most recent of 20 posts we hold for @botnet1t. 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.
Mentions
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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“BOTNET - AESBOT” (@botnet1t), 99 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/botnet1t.
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.