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 9 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
65 measurements spanning 101 days, net -481. 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 42,487–43,112 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)
Subscribers
Change
15 Nov 2026, 21:45
42,559
-20
12 Nov 2026, 12:10
42,579
-9
10 Nov 2026, 11:54
42,588
-26
8 Nov 2026, 22:54
42,614
-18
7 Nov 2026, 12:24
42,632
-13
6 Nov 2026, 12:17
42,645
-7
5 Nov 2026, 11:16
42,652
-12
4 Nov 2026, 09:11
42,664
+3
3 Nov 2026, 05:49
42,661
-12
2 Nov 2026, 02:20
42,673
-18
1 Nov 2026, 05:21
42,691
-2
31 Oct 2026, 05:28
42,693
-13
30 Oct 2026, 08:29
42,706
-8
29 Oct 2026, 05:19
42,714
-12
28 Oct 2026, 03:57
42,726
-11
27 Oct 2026, 06:58
42,737
-16
26 Oct 2026, 03:51
42,753
-17
25 Oct 2026, 06:17
42,770
-4
24 Oct 2026, 04:01
42,774
+10
23 Oct 2026, 04:19
42,764
first reading
Engagement
125 posts held, back to 21 July 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 219 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
6.87%
avg views ÷ 42,559 subscribers
Avg views / post
2,920
35 posts measured
Reaction rate
0.376%
reactions ÷ views · ER floor
Posts in window
35
of 125 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 17 November 2026
Posts held
125 (21 July 2026 – 17 November 2026)
Views total
102,260
Reactions total
384
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 Nov 2026, 12:13 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
≈850
Videos
≈8
Links
≈1,100
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
4s
Average length
4s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
1,440 reactions across 122 posts, in 37 distinct kinds. The most used accounts for 35.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
513
35.6%
😁
292
20.3%
🔥
156
10.8%
👍
154
10.7%
🤣
142
9.86%
💯
32
2.22%
🆒
29
2.01%
❤🔥
21
1.46%
🤨
17
1.18%
👎
12
0.833%
✍
11
0.764%
🤔
9
0.625%
👀
7
0.486%
👏
7
0.486%
🎉
4
0.278%
⚡
3
0.208%
💋
3
0.208%
🖕
3
0.208%
🤝
3
0.208%
🎃
2
0.139%
17 further kinds
20
1.39%
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 124 of the 125 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 1,440 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 125 most recent posts we hold, published 21 July 2026 to 17 November 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.
Telegram Stars
Stars received
9
across the posts below
Posts paid on
6
of 125 we hold a reading for · 5%
Most on one post
3
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @cybersec_academy. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 125 most recent posts we hold for this entry, published 21 July 2026 to 17 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Advertising
Ad load
6.40%
8 of 125 posts carry an ad marker
Regulatory tokens
8
posts carrying an erid · 8 distinct tokens
Median views · ads
2,310
over 8 measured posts
Median views · rest
3,690
over 117 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2SDnjeS2rL4
1
20 October 2026
20 October 2026
2Vtzqw84EVK
1
22 October 2026
22 October 2026
2VtzqwQZ9CR
1
15 October 2026
15 October 2026
2VtzqxJBEEa
1
10 November 2026
10 November 2026
2W5zFG7WfZc
1
12 November 2026
12 November 2026
2W5zFGUJq7p
1
31 October 2026
31 October 2026
2W5zFHVjryX
1
6 October 2026
6 October 2026
2W5zFKAFm93
1
9 September 2026
9 September 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 125 most recent posts we hold, published 21 July 2026 to 17 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 35 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Взломали подрядчика - добрались до его клиентов: что показали исследования PT Vector
👋 Приветствую в мире цифровой безопасности!
Взлом одной компании может обернуться проблемами для десятков других. Достаточно получить доступ к почте подрядчика, его программному обеспечению или системе управления инфраструктурой. По данным исследования Positive Technologies PT Vector, за год число атак на организации через клиентов…
Скрепка против Nintendo: как взламывали консоли до появления нейросетей
Пока сегодня нейросети пишут эксплойты, раньше хакерам приходилось обходиться тем, что лежало в ящике с инструментами. Для Nintendo Switch годилась скрепка, для 3DS - магнит, а для Wii - пинцет. И нет, это не инструкция по ремонту приставок 😅
⏺Автор собрал истории взлома Nintendo и Sony, где вместо сложных инструментов в ход шли контакты Joy-Co…
5 неочевидных фишек Bash
👋 Приветствую в мире цифровой безопасности!
Bash умеет не только запускать команды. Некоторые его особенности помогают находить подозрительный код, скрытые обработчики и ошибки безопасности в скриптах.
⏺Проверяем подмену команд. В Bash функция может называться так же, как системная утилита:
type -a ssh
declare -f ssh
Если вместо /usr/bin/ssh вызывается функция, стоит проверить её содержи…
Человек, который придумал взламывать пароли с помощью словаря
👋 Приветствую в мире цифровой безопасности!
Сегодня расскажу о Роберте Моррисе-старшем, одном из первых исследователей компьютерной безопасности. Ещё в 1970-х он показал, почему даже зашифрованные пароли могут оказаться бесполезными, если люди выбирают слишком предсказуемые комбинации.
⏺В то время Моррис работал в Bell Labs над Unix. Система уже использ…
Маршрут построен: выбираем свой путь в ИБ
Защита или пентест, вендор или интегратор, собственная практика или большая компания — у карьеры в кибербезопасности много сценариев.
На public talk от K2 Кибербезопасность:
✅ разберем плюсы и минусы разных карьерных треков
✅ сравним работу в Blue и Red командах
✅ обсудим, как не потеряться среди множества ролей
После — попрактикуемся проходить собесы, поедим пиццу и разы…
SSH без authorized_keys: где может прятаться чужой доступ
👋 Приветствую в мире цифровой безопасности!
Отключили вход по паролю, запретили root-login, проверили authorized_keys. Посторонних ключей нет, но это ещё не значит, что доступ к серверу полностью под контролем. У OpenSSH есть несколько менее очевидных способов авторизации, которыми могут воспользоваться и атакующие.
⏺Начнём с реальных настроек SSH. Конфигур…
CloudFox: ищем опасные разрешения и забытые ресурсы в AWS
👋 Приветствую в мире цифровой безопасности!
В облаке легко упустить лишние права доступа, старые IAM-роли или случайно открытые сервисы. Особенно когда инфраструктура разрослась на десятки ресурсов. Для такой ревизии пригодится CloudFox.
⏺CloudFox - open-source инструмент для разведки и аудита облачной инфраструктуры. Собирает сведения о правах, ресурсах и …
Как остановить хакера, который уже проник в корпоративную сеть?
Представьте, что ИТ-инфраструктура — это многоэтажный дом, где виртуальные машины — отдельные помещения, а сетевые сегменты — этажи. Если злоумышленник проник в одну комнату, как не дать ему попасть в остальные?
Один из способов — микросмегментация средствами программно-определяемых сетей, или SDN (Software Defined Networks). Эта технология помогает ко…
Ваш Mac уже знает, кто ваша семья. Даже если вы ему не рассказывали… 😐
Оказывается, macOS умеет сама вычислять, кто вам родственник, партнёр или близкий друг. Для этого система смотрит, кому вы пишете, с кем чаще фотографируетесь, где бываете и даже в какое время общаетесь. А самое интересное, что все эти догадки Mac складывает в отдельную базу, о существовании которой большинство пользователей даже не подозревает.
…
Sudo Audit Linux. Как обнаружить обход sudo через подмену редактора
👋 Приветствую в мире цифровой безопасности!
В прошлой части разбирали корреляцию sudo и auditd.
⏺Теперь рассмотрим менее очевидную историю: пользователь не имеет права запускать shell от root, зато ему разрешено редактировать системные файлы через sudoedit. Казалось бы, безопаснее обычного sudo. Но есть нюансы.
⏺Где возникает риск? sudoedit запус…
❤6👍4
Showing the 12 most recent of 125 posts we hold for @cybersec_academy. 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.
Posts edited after publishing
@cybersec_academy edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
16 October 2026
Most recent edit
16 October 2026
Posts recorded as deleted after publishing
We recorded 34 posts on @cybersec_academy as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
First seen missing
10 August 2026
Most recent seen missing
12 November 2026
Median time before seen missing
5 days
Seen missing in the last 30 days
12
Polls
The 6 most recent of 7 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 125 most recent posts we hold, published 21 July 2026 to 17 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Mentions
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 29 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Бункер Хакера @book_academ · 21,292 Telegram ranks this channel #1 of 72 here — alongside 71 others — read 23 September 2026
Белый хакер @bezopasno_soft · 29,580 Telegram ranks this channel #1 of 78 here — alongside 77 others — read 8 September 2026
CYBER HUNTER - Кибербезопасность @cyberbezopasno · 58,542 Telegram ranks this channel #4 of 50 here — alongside 49 others — read 26 August 2026
Серверная Админа | Компьютерные сети @school_network · 26,381 Telegram ranks this channel #5 of 85 here — alongside 84 others — read 12 September 2026
PulSe @Pulsechanel · 20,012 Telegram ranks this channel #7 of 69 here — alongside 68 others — read 29 September 2026
Лаборатория хакера @lab_hack · 25,374 Telegram ranks this channel #9 of 71 here — alongside 70 others — read 14 September 2026
InfoSec Portal @cybersecinform · 20,065 Telegram ranks this channel #10 of 75 here — alongside 74 others — read 2 October 2026
infosecurity @tg_infosec · 26,820 Telegram ranks this channel #11 of 74 here — alongside 73 others — read 11 September 2026
CyberYozh @cyberyozh_official · 62,660 Telegram ranks this channel #11 of 81 here — alongside 80 others — read 21 August 2026
Kali Linux @linuxkalii · 55,893 Telegram ranks this channel #15 of 89 here — alongside 88 others — read 23 August 2026
infosec @it_secur · 63,564 Telegram ranks this channel #16 of 81 here — alongside 80 others — read 22 August 2026
no system is safe // cybersec @nsis_cybersec · 21,091 Telegram ranks this channel #17 of 71 here — alongside 70 others — read 23 September 2026
Этичный Хакер @hack_less · 242,543 Telegram ranks this channel #20 of 81 here — alongside 80 others — read 12 August 2026
Social Engineering @Social_engineering · 124,636 Telegram ranks this channel #23 of 82 here — alongside 81 others — read 13 August 2026
S.E.Book @S_E_Book · 23,075 Telegram ranks this channel #24 of 64 here — alongside 63 others — read 19 September 2026
Termux, please @termuxplz0x41 · 32,423 Telegram ranks this channel #24 of 54 here — alongside 53 others — read 4 September 2026
Linux Academy @linuxacademiya · 28,694 Telegram ranks this channel #25 of 84 here — alongside 83 others — read 9 September 2026
S.E.Reborn @S_E_Reborn · 22,441 Telegram ranks this channel #31 of 66 here — alongside 65 others — read 20 September 2026
Mr. Robot @elliot_cybersec · 38,872 Telegram ranks this channel #31 of 70 here — alongside 69 others — read 31 August 2026
Пакет Безопасности @package_security · 34,225 Telegram ranks this channel #32 of 82 here — alongside 81 others — read 4 September 2026
КиберДед official @deedcoin_club · 23,016 Telegram ranks this channel #34 of 84 here — alongside 83 others — read 25 September 2026
Bash Days | Linux | DevOps @bashdays · 23,608 Telegram ranks this channel #34 of 94 here — alongside 93 others — read 18 September 2026
Life-Hack - Хакер @haccking · 62,998 Telegram ranks this channel #35 of 85 here — alongside 84 others — read 21 August 2026
IT Portal @IT_Portal · 118,936 Telegram ranks this channel #43 of 78 here — alongside 77 others — read 15 August 2026
This channel appears in 32 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 November 2026 — this
entry's latest reading, not the date you are reading this.
“ZeroDay | Кибербезопасность” (@cybersec_academy), 42,559 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/cybersec_academy.
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.