Telegram RegisterThe public register of Telegram
Telegram profile photo for ZeroDay | Кибербезопасность

Channel

ZeroDay | Кибербезопасность

@cybersec_academy

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Polls · Citations · Telegram's recommendations · Cite this entry

42,833subscribers

-207 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001563260161
TypeChannel
Username@cybersec_academy
DescriptionВаш учебник по кибербезопасности Реклама - @bashmak_media https://telega.in/c/cybersec_academy РКН: https://vk.cc/cHYqeq
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live1 October 2026
Measurements held34
Confirmed unchanged1 time, most recently 1 October 2026
On Telegramt.me/cybersec_academy

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 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 why it has no browse page of its own yet.

Growth

42,81743,04042,928.56 August 2026 — 43,040 subscribers7 August 2026 — 43,031 subscribers8 August 2026 — 43,029 subscribers9 August 2026 — 43,014 subscribers10 August 2026 — 42,997 subscribers11 August 2026 — 42,990 subscribers12 August 2026 — 42,983 subscribers14 August 2026 — 42,975 subscribers15 August 2026 — 42,969 subscribers16 August 2026 — 42,963 subscribers17 August 2026 — 42,964 subscribers18 August 2026 — 42,957 subscribers20 August 2026 — 42,945 subscribers20 August 2026 — 42,916 subscribers22 August 2026 — 42,901 subscribers24 August 2026 — 42,907 subscribers25 August 2026 — 42,903 subscribers26 August 2026 — 42,891 subscribers27 August 2026 — 42,876 subscribers28 August 2026 — 42,868 subscribers29 August 2026 — 42,855 subscribers30 August 2026 — 42,860 subscribers31 August 2026 — 42,861 subscribers1 September 2026 — 42,844 subscribers2 September 2026 — 42,818 subscribers3 September 2026 — 42,817 subscribers5 September 2026 — 42,823 subscribers8 September 2026 — 42,850 subscribers11 September 2026 — 42,848 subscribers13 September 2026 — 42,862 subscribers14 September 2026 — 42,856 subscribers16 September 2026 — 42,839 subscribers18 September 2026 — 42,838 subscribers1 October 2026 — 42,833 subscribers42,8336 August 20261 October 2026
34 measurements spanning 56 days, net -207. 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,784–43,073 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
1 Oct 2026, 11:1542,833-5
18 Sept 2026, 11:2042,838-1
16 Sept 2026, 07:2042,839-17
14 Sept 2026, 13:4042,856-6
13 Sept 2026, 01:0142,862+14
11 Sept 2026, 02:1742,848-2
8 Sept 2026, 05:5742,850+27
5 Sept 2026, 02:3742,823+6
3 Sept 2026, 10:2242,817-1
2 Sept 2026, 07:2942,818-26
1 Sept 2026, 05:1342,844-17
31 Aug 2026, 04:2742,861+1
30 Aug 2026, 06:0542,860+5
29 Aug 2026, 04:3342,855-13
28 Aug 2026, 05:2842,868-8
27 Aug 2026, 03:4742,876-15
26 Aug 2026, 00:4542,891-12
25 Aug 2026, 03:5642,903-4
24 Aug 2026, 00:5742,907+6
22 Aug 2026, 08:1842,901first reading

Engagement

73 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 117 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.05%
avg views ÷ 42,833 subscribers
Avg views / post
3,450
30 posts measured
Reaction rate
0.309%
reactions ÷ views · ER floor
Posts in window
30
of 73 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
WindowRolling 30 days · latest post in window 1 October 2026
Posts held73 (21 July 2026 – 1 October 2026)
Views total103,486
Reactions total320
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Oct 2026, 03:12 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
≈810
Videos
≈8
Links
≈1,070

Lifetime counters from Telegram’s own channel header, read 2 October 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.

Reaction mix

876 reactions across 71 posts, in 31 distinct kinds. The most used accounts for 32.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤28832.9%
😁18621.2%
🔥9410.7%
🤣879.93%
👍748.45%
💯323.65%
🆒293.31%
🤨171.94%
👎91.03%
🤔91.03%
❤‍🔥80.913%
👏70.799%
✍60.685%
🎉40.457%
💋30.342%
🖕30.342%
🤝30.342%
⚡20.228%
🏆20.228%
💊20.228%
11 further kinds111.26%

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 72 of the 73 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 876 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 73 most recent posts we hold, published 21 July 2026 to 1 October 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
6
across the posts below
Posts paid on
4
of 73 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 73 most recent posts we hold for this entry, published 21 July 2026 to 1 October 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
4.11%
3 of 73 posts carry an ad marker
Regulatory tokens
3
posts carrying an erid · 3 distinct tokens
Median views · ads
1,350
over 3 measured posts
Median views · rest
3,880
over 70 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. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2W5zFGUhTzZ11 October 20261 October 2026
2W5zFGwVHf711 October 20261 October 2026
2W5zFKAFm9319 September 20269 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 73 most recent posts we hold, published 21 July 2026 to 1 October 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

1 Oct 2026, 11:00 UTC≈1,210 views6 reactionsread 2 October 2026
Advertisementerid 2W5zFGwVHf7Photo

Ну что, поехали! Пятый сезон CyberCamp стартовал! И у нас сразу три новости: 📣 Открыта регистрация на CampGO — командные киберучения пройдут с 24 октября по 6 ноября в три тура на выбывание. Собирай команду из 3–6 человек и готовься к 10+ заданиям по разным направлениям кибербеза. Заявки принимаем до 15 октября. 📣 Запустили новую платформу CyberCamp. Теперь здесь будут жить мероприятия сезона, доклады, практика и …

🏆2🔥2✍1👍1

1 Oct 2026, 10:00 UTC926 views1 reactionsread 2 October 2026
Video

Zeroization: как правильно уничтожать секреты в памяти 👋 Приветствую в мире цифровой безопасности! ⏺Zeroization - это практика безопасного удаления чувствительных данных из памяти после использования. Ключи, пароли, токены и другие секреты не должны оставаться в RAM дольше необходимого. ⏺Проблема в том, что обычного освобождения памяти недостаточно. Например: char secret[32] = "super-secret-key"; use_secret(sec…

🔥1

1 Oct 2026, 07:00 UTC≈1,350 views1 reactionsread 2 October 2026
Advertisementerid 2W5zFGUhTzZPhoto

Один вход на все сетевые устройства: практикум по AAA и RADIUS По данным исследования ГК «Солар», более чем в 40% компаний учётные записи сотрудников продолжают работать после увольнения. С сетевым оборудованием ещё сложнее: у каждого админа свой локальный пароль к маршрутизатору, а кто менял конфигурацию, не выяснить. Уже завтра, в 19:00 мск, пройдёт открытый практикум по защите административного доступа к сетевым…

❤1

30 Sept 2026, 12:25 UTC≈1,590 views7 reactionsread 2 October 2026
Video

Анализ скрытых MITM в Wireshark: часть 2 👋 Приветствую в мире цифровой безопасности! В прошлой части смотрели на сертификаты и сетевые параметры. Теперь копнём глубже: разберём признаки, которые по отдельности ещё ничего не доказывают, но вместе могут вывести на след прокси или перехватывающего узла. ⏺Начнём с TLS Alert. Если посредник не может нормально обработать соединение, он может оборвать сессию прямо во вре…

❤6🔥1

28 Sept 2026, 14:06 UTC≈2,540 views3 reactionsread 2 October 2026
Photo

Как дать контейнеру SSH и при этом не дать ему украсть ключ? Контейнеру нужно забрать код из приватного Git или сходить на сервер. Самый очевидный путь - сунуть внутрь ~/.ssh. Только вместе с SSH-доступом приложение получает и приватный ключ: если процесс взломают, ключ можно прочитать и унести. ⏺Автор статьи решил сделать наоборот - оставить контейнеру полноценный SSH, но сам секрет от него спрятать. Вместо ключа …

❤3

25 Sept 2026, 09:46 UTC≈3,580 views12 reactionsread 2 October 2026
Photo

Человек, который научил Интернет не бояться чужих глаз 👋 Приветствую в мире цифровой безопасности! Сегодня расскажу о Мартине Хеллмане, одном из людей, благодаря которым защищённое соединение в интернете вообще стало возможным. ⏺В 1970-х Хеллман работал профессором в Стэнфорде и занимался криптографией. Тогда она в основном ассоциировалась с военными и закрытыми государственными разработками. Даже коллеги советова…

🔥9❤2🥰1

24 Sept 2026, 12:05 UTC≈3,000 views6 reactionsread 2 October 2026
Photo

Cross-Site Leaks: полная защита 👋 Приветствую в мире цифровой безопасности! В прошлый раз разобрали как атакующий вытаскивает данные через побочные эффекты браузера. Сегодня будем защищаться. ⏺Fetch Metadata на сервере: браузер сам добавляет к каждому запросу контекст откуда он пришёл. Проверяем его до выполнения любой логики: def fetch_metadata_check(request): site = request.headers.get('Sec-Fetch-Site', '')…

❤5👌1

23 Sept 2026, 11:25 UTC≈2,650 views10 reactionsread 2 October 2026
Photo

Cross-Site Leaks: как атакующий читает чужие данные через браузер 👋 Приветствую в мире цифровой безопасности! XS-Leaks - класс атак, где один сайт узнаёт информацию о юзере на другом сайте, не нарушая Same-Origin Policy напрямую. Разбираем как это работает 👇 ⏺Браузер изолирует сайты: один не может прочитать ответ запроса к другому. Но атакующий может наблюдать за побочными эффектами: сколько времени занял запрос, …

✍4❤2👏2💊1🔥1

22 Sept 2026, 11:16 UTC≈2,780 views11 reactionsread 2 October 2026
Photo

Velociraptor: как искать следы атаки на хосте 👋 Приветствую в мире цифровой безопасности! После алерта хочется быстро понять, что вообще происходило на машине. Какие процессы запускались, что менялось в системе, какие артефакты остались. Для этого есть Velociraptor. ⏺Velociraptor собирает данные с Windows, Linux и macOS через VQL. Запросы можно запускать прямо на endpoint и получать состояние системы без ручного о…

❤10✍1

21 Sept 2026, 13:55 UTC≈3,370 views5 reactionsread 2 October 2026
Photo

Сервер, который не отвечает без сертификата: как mTLS отсекает атаки ещё до HTTP Автор поднял homelab на одном сервере с Traefik и Dokploy и решил проверить mTLS не на схеме, а на реальных атаках. Сначала определил, что именно нужно защищать и от кого, а потом начал ломать собственный сервер без клиентского сертификата. ⏺В статье показывают, как mTLS отсекает brute force, credential stuffing и попытки добраться до …

❤3🔥2

19 Sept 2026, 09:08 UTC≈3,880 views30 reactionsread 2 October 2026
Photo

DLL Hijacking: когда Windows загружает не ту библиотеку 👋 Приветствую в мире цифровой безопасности! Расскажу, как работает атака DLL Hijacking. ⏺Допустим, программа запускает helper.dll, не указывая полный путь. Если рядом с приложением лежит DLL с таким именем, Windows может загрузить её вместо той, которую разработчик рассчитывал найти в системном каталоге. ⏺На этом и строится DLL Hijacking. Атакующему не обяза…

🔥28❤2

Showing the 12 most recent of 73 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.

Polls

The 5 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.

16 Sept 2026, 10:00 UTCAnonymous Quiz656 voters

На сервере обнаружили PowerShell-процесс с -EncodedCommand. Что это само по себе означает?

  1. Команда точно вредоносная5%
  2. Команда зашифрована AES29%
  3. Команда представлена в Base6444%
  4. PowerShell запущен из памяти22%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

12 Sept 2026, 10:47 UTCAnonymous Quiz764 voters

EDR фиксирует процесс, который обращается к памяти lsass.exe. Что из этого наиболее важно проверить?

  1. Имя пользователя процесса25%
  2. Права доступа к процессу60%
  3. Размер файла процесса8%
  4. Время создания каталога7%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

23 Aug 2026, 11:50 UTCAnonymous Quiz600 voters

Какой механизм защиты от атак типа buffer overflow использует случайную расстановку адресов в памяти?

  1. Stack Canaries24%
  2. DEP19%
  3. ASLR43%
  4. ROP14%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

22 Aug 2026, 17:56 UTCAnonymous Quiz557 voters

Что нужно для создания Silver Ticket?

  1. Хэш krbtgt24%
  2. Пароль Domain Admin14%
  3. Секрет сервисного аккаунта27%
  4. TGT текущего пользователя35%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

25 Jul 2026, 09:00 UTCAnonymous Quiz1,050 voters approx.

Какой тип атаки позволяет украсть NTLM-хэш без взлома пароля?

  1. SQL Injection18%
  2. DNS Spoofing12%
  3. Pass-the-Hash61%
  4. Clickjacking9%

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 73 most recent posts we hold, published 21 July 2026 to 1 October 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.

Names

Channels on the register whose handles appear in this channel's posts.

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.

Белый хакер
@bezopasno_soft · 29,652
#1
infosec
@it_secur · 62,112
#2
Social Engineering
@Social_engineering · 125,007
#3
Бункер Хакера
@book_academ · 21,429
#4
Архив Безопасника
@secure_archive · 10,833
#5
infosecurity
@tg_infosec · 26,779
#6
Admin Guides | Сисадмин
@admguides · 11,942
#7
Серверная Админа | Компьютерные сети
@school_network · 26,588
#8
Записки Безопасника
@infosec_globe · 18,074
#9
Не хакинг, а ИБ
@searchack · 18,194
#10
no system is safe // cybersec
@nsis_cybersec · 21,518
#11
Похек
@poxek · 16,849
#12
SecurityLab.ru
@SecLabNews · 84,654
#13
CyberINS // Лаборатория ИБешника
@cyberins · 11,425
#14
Kali Linux
@linuxkalii · 55,412
#15
S.E.Reborn
@S_E_Reborn · 22,405
#16
Inf0 | ИБ, OSINT
@info_cybersecurity · 10,381
#17
Life-Hack - Хакер
@haccking · 63,183
#18
Codeby
@codeby_sec · 37,041
#19
Арсенал Безопасника
@arsenal_security · 15,191
#20
InfoSec Portal
@cybersecinform · 19,315
#21
Сетевик Джонни // Network Admin
@iscode · 5,799
#22
Пакет Безопасности
@package_security · 33,011
#23
White Hat
@kind_hack · 11,934
#24
PyLinux - Всё о Linux, Python и IT
@pylinux0 · 11,047
#25
S.E.Book
@S_E_Book · 23,146
#26
IT Portal
@IT_Portal · 99,978
#27
Чёрный Треугольник
@black_triangle_tg · 63,850
#28
Network Admin
@networkadm · 12,380
#29
Bash Days | Linux | DevOps
@bashdays · 23,634
#30
Хакер — Xakep.RU
@xakep_ru · 39,610
#31
Project Omega | ИБ
@omega_cybersec · 8,788
#32
Cybred
@cybred · 11,118
#33
Архив Программиста
@storage_it · 8,749
#34
NetworkAdmin.ru
@networkadminru · 4,703
#35
Linux Academy
@linuxacademiya · 28,434
#36
GitHub Разработчика
@git_developer · 17,018
#37
IT-KB 🤖
@ITKB_channel · 8,000
#38
Investigation & Forensic TOOLS
@forensictools · 22,417
#39
Пост Лукацкого
@alukatsky · 37,915
#40
ServerAdmin.ru
@srv_admin · 32,572
#41
[PYTHON:TODAY]
@python2day · 63,764
#42
INSPECTOR | OSINT
@it_fullstak · 10,829
#43
Security Vision
@svplatform · 5,398
#44
AP Security
@ap_security · 3,981
#45
PulSe
@Pulsechanel · 19,875
#46
Positive Technologies
@Positive_Technologies · 29,062
#47
RED Security
@redsecurity_co · 5,194
#48
InfoSec Community
@infosec_tg · 10,338
#49
NetStalkers
@netstalkerscom · 7,844
#50
APT
@APT_Notes · 16,685
#51
IT Syndicate
@ITSyndicate_23 · 8,560
#52
Linux / Линукс
@linux_gram · 13,665
#53
Мыслить как безопасник
@artemov_security · 9,063
#54
Библиотека Кодера
@library_dev · 5,281
#55
Библиотека хакера | Hacking, Infosec, ИБ, информационная безопасность
@hackproglib · 12,691
#56
Mr. Robot
@elliot_cybersec · 38,917
#57
Вакансии в ИБ | infosec
@infosec_work · 15,755
#58
Open Source
@open_source_friend · 52,304
#59
Russian OSINT
@Russian_OSINT · 47,943
#60
SecAtor
@true_secator · 41,748
#61
Эксплойт
@exploitex · 2,048,279
#62
Управление Уязвимостями и прочее
@avleonovrus · 12,122
#63
PRO:PENTEST
@pro_pentest · 10,108
#64
RECURA | Программирование & IT
@recura_tech · 14,576 (as read 29 August 2026)
#65
LinuxCamp | DevOps
@linuxcamp_tg · 13,600
#66
Бэкдор
@whackdoor · 1,590,187
#67
Утечки информации
@dataleak · 119,057
#68
Python Developer
@python_tg · 20,942
#69
GitHub Community
@github · 155,991
#70

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,429
Telegram ranks this channel #1 of 72 here — alongside 71 others — read 23 September 2026
Белый хакер
@bezopasno_soft · 29,652
Telegram ranks this channel #1 of 78 here — alongside 77 others — read 8 September 2026
CYBER HUNTER - Кибербезопасность
@cyberbezopasno · 56,399
Telegram ranks this channel #4 of 50 here — alongside 49 others — read 26 August 2026
Серверная Админа | Компьютерные сети
@school_network · 26,588
Telegram ranks this channel #5 of 85 here — alongside 84 others — read 12 September 2026
PulSe
@Pulsechanel · 19,875
Telegram ranks this channel #7 of 69 here — alongside 68 others — read 29 September 2026
Лаборатория хакера
@lab_hack · 25,556
Telegram ranks this channel #9 of 71 here — alongside 70 others — read 14 September 2026
infosecurity
@tg_infosec · 26,779
Telegram ranks this channel #11 of 74 here — alongside 73 others — read 11 September 2026
CyberYozh
@cyberyozh_official · 62,597
Telegram ranks this channel #11 of 81 here — alongside 80 others — read 21 August 2026
Kali Linux
@linuxkalii · 55,412
Telegram ranks this channel #15 of 89 here — alongside 88 others — read 23 August 2026
infosec
@it_secur · 62,112
Telegram ranks this channel #16 of 81 here — alongside 80 others — read 22 August 2026
no system is safe // cybersec
@nsis_cybersec · 21,518
Telegram ranks this channel #17 of 71 here — alongside 70 others — read 23 September 2026
Этичный Хакер
@hack_less · 233,911
Telegram ranks this channel #20 of 81 here — alongside 80 others — read 12 August 2026
Social Engineering
@Social_engineering · 125,007
Telegram ranks this channel #23 of 82 here — alongside 81 others — read 13 August 2026
S.E.Book
@S_E_Book · 23,146
Telegram ranks this channel #24 of 64 here — alongside 63 others — read 19 September 2026
Termux, please
@termuxplz0x41 · 32,722
Telegram ranks this channel #24 of 54 here — alongside 53 others — read 4 September 2026
Linux Academy
@linuxacademiya · 28,434
Telegram ranks this channel #25 of 84 here — alongside 83 others — read 9 September 2026
S.E.Reborn
@S_E_Reborn · 22,405
Telegram ranks this channel #31 of 66 here — alongside 65 others — read 20 September 2026
Mr. Robot
@elliot_cybersec · 38,917
Telegram ranks this channel #31 of 70 here — alongside 69 others — read 31 August 2026
Пакет Безопасности
@package_security · 33,011
Telegram ranks this channel #32 of 82 here — alongside 81 others — read 4 September 2026
КиберДед official
@deedcoin_club · 24,189
Telegram ranks this channel #34 of 84 here — alongside 83 others — read 25 September 2026
Bash Days | Linux | DevOps
@bashdays · 23,634
Telegram ranks this channel #34 of 94 here — alongside 93 others — read 18 September 2026
Life-Hack - Хакер
@haccking · 63,183
Telegram ranks this channel #35 of 85 here — alongside 84 others — read 21 August 2026
IT Portal
@IT_Portal · 99,978
Telegram ranks this channel #43 of 78 here — alongside 77 others — read 15 August 2026
Task No Face
@TaskNoFace · 29,506
Telegram ranks this channel #45 of 78 here — alongside 77 others — read 8 September 2026

This channel appears in 30 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 1 October 2026 — this entry's latest reading, not the date you are reading this.

“ZeroDay | Кибербезопасность” (@cybersec_academy), 42,833 subscribers as measured 1 October 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.