Telegram RegisterThe public register of Telegram
Telegram profile photo for Белый хакер

Channel

Белый хакер

@bezopasno_soft

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

29,631subscribers

-68 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001614759234
TypeChannel
Username@bezopasno_soft
DescriptionОдин из ведущих каналов по информационной безопасности. Реклама - @bashmak_media Мы на бирже: https://telega.in/c/bezopasno_soft РКН: https://vk.cc/cHYq3i
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 November 2026
Measurements held58
Confirmed unchanged2 times, most recently 6 November 2026
On Telegramt.me/bezopasno_soft

Topic

Software piracy — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 52% 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

29,59329,72729,6607 August 2026 — 29,699 subscribers8 August 2026 — 29,703 subscribers9 August 2026 — 29,701 subscribers10 August 2026 — 29,694 subscribers11 August 2026 — 29,691 subscribers12 August 2026 — 29,694 subscribers13 August 2026 — 29,698 subscribers14 August 2026 — 29,697 subscribers15 August 2026 — 29,696 subscribers16 August 2026 — 29,691 subscribers17 August 2026 — 29,695 subscribers18 August 2026 — 29,687 subscribers19 August 2026 — 29,678 subscribers20 August 2026 — 29,669 subscribers22 August 2026 — 29,666 subscribers24 August 2026 — 29,651 subscribers25 August 2026 — 29,652 subscribers26 August 2026 — 29,643 subscribers27 August 2026 — 29,646 subscribers27 August 2026 — 29,641 subscribers28 August 2026 — 29,638 subscribers29 August 2026 — 29,633 subscribers30 August 2026 — 29,625 subscribers1 September 2026 — 29,619 subscribers1 September 2026 — 29,612 subscribers4 September 2026 — 29,619 subscribers7 September 2026 — 29,691 subscribers10 September 2026 — 29,714 subscribers12 September 2026 — 29,721 subscribers14 September 2026 — 29,727 subscribers15 September 2026 — 29,704 subscribers17 September 2026 — 29,706 subscribers28 September 2026 — 29,652 subscribers5 October 2026 — 29,634 subscribers9 October 2026 — 29,607 subscribers13 October 2026 — 29,595 subscribers15 October 2026 — 29,599 subscribers16 October 2026 — 29,593 subscribers17 October 2026 — 29,630 subscribers18 October 2026 — 29,639 subscribers19 October 2026 — 29,643 subscribers20 October 2026 — 29,653 subscribers21 October 2026 — 29,646 subscribers23 October 2026 — 29,698 subscribers24 October 2026 — 29,699 subscribers25 October 2026 — 29,702 subscribers26 October 2026 — 29,698 subscribers27 October 2026 — 29,694 subscribers28 October 2026 — 29,688 subscribers29 October 2026 — 29,679 subscribers30 October 2026 — 29,667 subscribers31 October 2026 — 29,665 subscribers1 November 2026 — 29,662 subscribers2 November 2026 — 29,652 subscribers3 November 2026 — 29,649 subscribers4 November 2026 — 29,642 subscribers5 November 2026 — 29,633 subscribers6 November 2026 — 29,631 subscribers29,6317 August 20266 November 2026
58 measurements spanning 91 days, net -68. 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 29,573–29,747 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 58
Measured (UTC)SubscribersChange
6 Nov 2026, 00:3729,631-2
5 Nov 2026, 02:4029,633-9
4 Nov 2026, 02:1529,642-7
3 Nov 2026, 01:3029,649-3
2 Nov 2026, 04:4929,652-10
1 Nov 2026, 07:0529,662-3
31 Oct 2026, 08:3629,665-2
30 Oct 2026, 11:5529,667-12
29 Oct 2026, 08:4929,679-9
28 Oct 2026, 05:5829,688-6
27 Oct 2026, 06:1729,694-4
26 Oct 2026, 05:3929,698-4
25 Oct 2026, 03:5829,702+3
24 Oct 2026, 00:3829,699+1
23 Oct 2026, 00:2629,698+52
21 Oct 2026, 22:1629,646-7
20 Oct 2026, 14:4029,653+10
19 Oct 2026, 13:0429,643+4
18 Oct 2026, 14:2829,639+9
17 Oct 2026, 14:3029,630first reading

Engagement

111 posts held, back to 16 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 165 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
9.40%
avg views ÷ 29,631 subscribers
Avg views / post
2,780
35 posts measured
Reaction rate
0.354%
reactions ÷ views · ER floor
Posts in window
35
of 111 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. It is computed over the 32 of 35 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 November 2026
Posts held111 (16 July 2026 – 7 November 2026)
Views total97,459
Reactions total316
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Nov 2026, 12:02 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
≈1,770
Videos
≈198
Links
≈1,910

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

919 reactions across 105 posts, in 28 distinct kinds. The most used accounts for 33.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤30433.1%
👍16217.6%
😁13514.7%
🔥10211.1%
🤣444.79%
🤯444.79%
🤔252.72%
🥰192.07%
👏131.41%
🤷‍♂121.31%
🐳111.20%
👎111.20%
🙈90.979%
🫡40.435%
⚡30.326%
🏆30.326%
💯30.326%
✍20.218%
🆒20.218%
🎉20.218%
8 further kinds90.979%

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

Measured over the 111 most recent posts we hold, published 16 July 2026 to 7 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.

Advertising

Ad load
6.31%
7 of 111 posts carry an ad marker
Regulatory tokens
7
posts carrying an erid · 7 distinct tokens
Median views · ads
2,190
over 7 measured posts
Median views · rest
3,140
over 104 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
eridPostsFirst seenLast seen
2Vtzqua9Wuy121 August 202621 August 2026
2VtzqviTXJK14 September 20264 September 2026
2VtzqvznHuf112 October 202612 October 2026
2Vtzqx4v9TB127 October 202627 October 2026
2W5zFHLz153126 October 202626 October 2026
2W5zFJ6HeZY15 November 20265 November 2026
2W5zFJNayqj128 October 202628 October 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 111 most recent posts we hold, published 16 July 2026 to 7 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).

7 Nov 2026, 10:50 UTC469 views9 reactionsread 7 November 2026
Photo

👍 Белый хакер #мем

😁9

6 Nov 2026, 11:07 UTC≈1,710 views5 reactionsread 7 November 2026
Video

🚨 В ChatGPT нашли уязвимость, позволявшую незаметно красть переписки даже в защищённом режиме Привет! Исследователи Check Point обнаружили способ обойти Lockdown Mode - специальный режим ChatGPT, который должен ограничивать передачу данных на внешние серверы. В определённых условиях атакующий мог похитить содержимое чатов без дополнительных действий пользователя. 👨‍💻 Проблема скрывалась в предпросмотре HTML-кода. C…

❤4🤔1

5 Nov 2026, 10:01 UTC≈2,300 views17 reactionsread 7 November 2026
Photo

🇷🇺 Российские хакеры заражали iPhone и Android через обычные сайты. Иногда хватало просто открыть страницу Привет! Исследователи Sekoia раскрыли кампанию Poisoned Source, которую связывают с APT29. Хакеры внедряли вредоносный JavaScript на настоящие сайты, в том числе связанные с военной сферой, а затем использовали уязвимости браузеров для кражи данных со смартфонов посетителей. 👨‍💻 Один из самых интересных эпизод…

🤯10🤣3🤔2🔥1😁1

5 Nov 2026, 07:00 UTC≈1,560 views3 reactionsread 5 November 2026
Advertisementerid 2W5zFJ6HeZYPhoto

В отрасли тектонический сдвиг. Одни на нём вырастут, другие проиграют. Где будешь ты? 👉 Узнать что происходит ны рынке ⚡️ Софт скоро будет у всех за копейки. За что тогда компании будут платить безопасникам? ⚡️ У атакующих появился AI-усилитель. Угроза профессии или рост цены? ⚡️ Коммуникатор или «инженер в подвале»: кто через 3 года заработает больше? ⚡️ Взломать сейчас легко. Кто сделает так, чтобы банк устоял? …

❤1🤣1😁1

4 Nov 2026, 07:28 UTC≈2,190 views2 reactionsread 7 November 2026
Photo

❌ Миф: если процесс запущен с seccomp, опасные системные вызовы заблокированы Привет! В Linux seccomp часто используют для ограничения системных вызовов. Настроили фильтр, запретили опасные операции и решили, что процесс теперь не сможет обойти ограничения. Но многое зависит от того, какие именно аргументы проверяет фильтр. 👨‍💻 Возьмём openat(). Через него процесс может открывать файлы, а seccomp позволяет проверят…

👍2

3 Nov 2026, 11:23 UTC≈2,480 views12 reactionsread 7 November 2026
Photo

🇮🇷 Иранские хакеры добрались до правительственного облака Ирака через фальшивые приложения и вакансии Привет! Группировка DarkBlinders провела серию атак на Ближнем Востоке. Среди целей оказались высокопоставленный человек в Израиле и правительственная облачная инфраструктура Иракского Курдистана. Исследователи Dream Research Labs рассказали, как хакерам удалось туда проникнуть. 👨‍💻 Один из способов - поддельный се…

❤8👍3🤔1

2 Nov 2026, 08:11 UTC≈2,780 views12 reactionsread 7 November 2026
Photo

🇰🇵 Северокорейские хакеры украли у Binance $6,43 млрд. Это крупнейшая криптокража в истории Привет! ФБР связало рекордный взлом Binance с северокорейской группировкой TraderTraitor, известной также как Jade Sleet. Хакерам удалось похитить криптовалюту на $6,43 млрд - больше чем в четыре раза превышает сумму знаменитого взлома Bybit в 2025 году. 👨‍💻 Средства вывели сразу из 11 блокчейнов, причём 82% украденного прих…

🔥6❤3🤔2👨‍💻1

31 Oct 2026, 07:00 UTC≈3,110 views45 reactionsread 7 November 2026
Photo

👍 Белый хакер #мем

❤22😁20👍3

30 Oct 2026, 12:04 UTC≈3,100 views12 reactionsread 7 November 2026
Photo

⌨️ Команда недели: setpriv Привет! Иногда нужно запустить программу с ограниченными привилегиями и проверить, что она действительно не сможет сделать лишнего. Менять пользователя через sudo -u можно, но это ещё не вся история: у процесса есть capabilities, no_new_privs и другие параметры безопасности. Для таких экспериментов в Linux есть setpriv. Она позволяет настроить привилегии прямо перед запуском команды. 👨‍💻…

👍8❤4

29 Oct 2026, 17:19 UTC≈2,990 views7 reactionsread 7 November 2026
Photo

🇨🇳 Китайские хакеры построили скрытую сеть из взломанных устройств для атак на инфраструктуру США Привет! Исследователи Black Lotus Labs раскрыли Silent Train - сеть, которую группировка Volt Typhoon использовала для кибершпионажа и эксплуатации уязвимостей нулевого дня. Через неё атаковали телеком-операторов, оборонные компании, государственные организации и объекты критической инфраструктуры. 👨‍💻 Работала сеть до…

👍5🤯1😁1

28 Oct 2026, 18:16 UTC≈3,010 views16 reactionsread 7 November 2026
Photo

❌ Миф: если контейнер запущен без root, он не сможет получить root на хосте Привет! Запустили контейнер с USER 1000, убрали лишние capabilities и убедились, что внутри никто не работает от root. Выглядит безопаснее, но есть нюанс: UID 1000 внутри контейнера не всегда означает изоляцию от привилегий хоста. 👨‍💻 По умолчанию Docker может использовать те же UID и GID, что и хост. Поэтому процесс с UID 1000 внутри конте…

👍13❤1🌚1🤣1

28 Oct 2026, 15:04 UTC≈2,040 views3 reactionsread 31 October 2026
Advertisementerid 2W5zFJNayqjPhoto

К2 Кибербезопасность протестировала Kaspersky NGFW 1.3 и выяснила реальную производительность в трех режимах защиты 🛡 На фоне импортозамещения российских NGFW становится больше, но как оценить их возможности до внедрения ❓ Одних заявленных характеристик недостаточно — важно проверить, какую производительность решение показывает с включенными модулями защиты и насколько она соответствует требованиям инфраструктуры. …

❤3

Showing the 12 most recent of 111 posts we hold for @bezopasno_soft. 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 recorded as deleted after publishing

We recorded 20 posts on @bezopasno_soft 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
16 October 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
3

Polls

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

17 Oct 2026, 11:20 UTCAnonymous Quiz407 voters

SSRF-фильтр проверяет IP при валидации URL, но не при соединении. Какой механизм может обойти такую защиту?

  1. HTTP pipelining25%
  2. TLS renegotiation27%
  3. DNS rebinding37%
  4. DNSSEC downgrade11%

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

3 Oct 2026, 13:32 UTCAnonymous Quiz615 voters

Сервер получает XML и сам делает HTTP-запросы по данным из него. Что проверить?

  1. SSTI10%
  2. SSRF26%
  3. XXE29%
  4. CSRF34%

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

12 Sept 2026, 10:47 UTCAnonymous Quiz426 voters

Веб-приложение принимает redirect после авторизации. Какой вариант наиболее опасен?

  1. URL содержит длинный query string18%
  2. Redirect ведёт на внешний домен64%
  3. URL использует HTTPS4%
  4. Redirect содержит фрагмент #home14%

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

23 Aug 2026, 11:52 UTCAnonymous Quiz552 voters

После фишинга антивирус молчит, хост шлёт DNS с высокой энтропией. Это:

  1. Обновление ПО4%
  2. Легитимный CDN6%
  3. DNS tunneling или C273%
  4. Сломанный резолвер17%

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

22 Aug 2026, 10:59 UTCAnonymous Quiz462 voters

Что ищут при Kerberoasting?

  1. Аккаунты со SPN32%
  2. Пользователей без MFA21%
  3. Хосты без DNS13%
  4. Сессии с NTLMv134%

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

25 Jul 2026, 09:00 UTCAnonymous Quiz516 voters

Зачем используют прямые syscall?

  1. Ускорить сеть10%
  2. Обойти перехват API51%
  3. Изменить права файла18%
  4. Создать службу Windows21%

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 111 most recent posts we hold, published 16 July 2026 to 7 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — 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.

ZeroDay | Кибербезопасность
@cybersec_academy · 42,632
#1
Social Engineering
@Social_engineering · 124,717
#2
infosec
@it_secur · 63,349
#3
Архив Безопасника
@secure_archive · 10,964
#4
Похек
@poxek · 17,272
#5
infosecurity
@tg_infosec · 26,855
#6
Пакет Безопасности
@package_security · 33,775
#7
Mr. Robot
@elliot_cybersec · 38,942
#8
Admin Guides | Сисадмин
@admguides · 12,044
#9
Бункер Хакера
@book_academ · 21,306
#10
Записки Безопасника
@infosec_globe · 17,911
#11
Лаборатория хакера
@lab_hack · 25,449
#12
Не хакинг, а ИБ
@searchack · 18,123
#13
no system is safe // cybersec
@nsis_cybersec · 21,198
#14
SecurityLab.ru
@SecLabNews · 86,455
#15
Архив Программиста
@storage_it · 8,670
#16
Kali Linux
@linuxkalii · 55,825
#17
Inf0 | ИБ, OSINT
@info_cybersecurity · 10,784
#18
Серверная Админа | Компьютерные сети
@school_network · 26,436
#19
Life-Hack - Хакер
@haccking · 63,051
#20
Codeby
@codeby_sec · 37,058
#21
CyberINS // Лаборатория ИБешника
@cyberins · 11,502
#22
IT Portal
@IT_Portal · 118,869
#23
S.E.Reborn
@S_E_Reborn · 22,457
#24
Арсенал Безопасника
@arsenal_security · 15,068
#25
InfoSec Portal
@cybersecinform · 20,027
#26
PRO:PENTEST
@pro_pentest · 10,220
#27
PyLinux | Всё о Linux & Python
@pylinux0 · 11,049
#28
InfoSec Community
@infosec_tg · 10,615
#29
SecAtor
@true_secator · 42,177
#30
Russian OSINT
@Russian_OSINT · 48,484
#31
Хакер — Xakep.RU
@xakep_ru · 40,287
#32
BashMaster
@bash_help · 8,798
#33
Bash Days | Linux | DevOps
@bashdays · 23,627
#34
Cybred
@cybred · 11,419
#35
Сетевик Джонни // Network Admin
@iscode · 5,754
#36
S.E.Book
@S_E_Book · 23,100
#37
White Hat
@kind_hack · 11,927
#38
Управление Уязвимостями и прочее
@avleonovrus · 12,623
#39
OFFZONE
@offzone_moscow · 7,541
#40
Бэкдор
@whackdoor · 1,542,951
#41
GitHub Разработчика
@git_developer · 17,913
#42
RECURA | Программирование & IT
@recura_tech · 14,628 (as read 8 September 2026)
#43
Чёрный Треугольник
@black_triangle_tg · 63,962
#44
КИБЕР МЕДИА
@secmedia · 6,110
#45
IT-KB 🤖
@ITKB_channel · 8,056
#46
Positive Technologies
@Positive_Technologies · 29,430
#47
Пост Лукацкого
@alukatsky · 38,422
#48
NetworkAdmin.ru
@networkadminru · 4,707
#49
Blue (h/c)at Café
@bh_cat · 4,001
#50
Библиотека Кодера
@library_dev · 5,275
#51
GitHub Community
@github · 155,066
#52
Project Omega | ИБ
@omega_cybersec · 8,702
#53
[PYTHON:TODAY]
@python2day · 63,365
#54
SecuriXy.kz
@securixy_kz · 10,377
#55
IT Syndicate
@ITSyndicate_23 · 8,493
#56
BI.ZONE
@bizone_channel · 11,589
#57
Утечки информации
@dataleak · 117,868
#58
Linux Academy
@linuxacademiya · 28,654
#59
YAH
@YAH_Channel · 7,632
#60
Linux / Линукс
@linux_gram · 13,900
#61
Investigation & Forensic TOOLS
@forensictools · 22,599
#62
AP Security
@ap_security · 4,249
#63
Мыслить как безопасник
@artemov_security · 9,213
#64
Библиотека хакера | Hacking, Infosec, ИБ, информационная безопасность
@hackproglib · 12,614
#65
Programmer & IT Memes
@itmemes · 121,960
#66
NetStalkers
@netstalkerscom · 7,805
#67
PurpleBear
@purple_medved · 4,669
#68
Вакансии в ИБ | infosec
@infosec_work · 16,321
#69
Багхантер 2.0
@bughunter_circuit · 16,486
#70
Эксплойт
@exploitex · 2,028,700
#71
Standoff 365
@standoff_365 · 8,438
#72
Open Source
@open_source_friend · 52,614
#73
Network Admin
@networkadm · 12,355
#74
RED Security
@redsecurity_co · 5,196
#75
Python Developer
@python_tg · 21,215
#76
LinuxCamp | DevOps
@linuxcamp_tg · 13,468
#77
Bafoмёд OSINT
@osint_san_framework · 9,374
#78

Read from Telegram’s recommendation API, most recently 8 September 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.

ZeroDay | Кибербезопасность
@cybersec_academy · 42,632
Telegram ranks this channel #1 of 70 here — alongside 69 others — read 29 August 2026
Бункер Хакера
@book_academ · 21,306
Telegram ranks this channel #5 of 72 here — alongside 71 others — read 23 September 2026
Пакет Безопасности
@package_security · 33,775
Telegram ranks this channel #6 of 82 here — alongside 81 others — read 4 September 2026
InfoSec Portal
@cybersecinform · 20,027
Telegram ranks this channel #9 of 75 here — alongside 74 others — read 2 October 2026
infosecurity
@tg_infosec · 26,855
Telegram ranks this channel #9 of 74 here — alongside 73 others — read 11 September 2026
CyberYozh
@cyberyozh_official · 62,574
Telegram ranks this channel #9 of 81 here — alongside 80 others — read 21 August 2026
Серверная Админа | Компьютерные сети
@school_network · 26,436
Telegram ranks this channel #10 of 85 here — alongside 84 others — read 12 September 2026
Mr. Robot
@elliot_cybersec · 38,942
Telegram ranks this channel #10 of 70 here — alongside 69 others — read 31 August 2026
Лаборатория хакера
@lab_hack · 25,449
Telegram ranks this channel #11 of 71 here — alongside 70 others — read 14 September 2026
CYBER HUNTER - Кибербезопасность
@cyberbezopasno · 58,740
Telegram ranks this channel #12 of 50 here — alongside 49 others — read 26 August 2026
Kali Linux
@linuxkalii · 55,825
Telegram ranks this channel #13 of 89 here — alongside 88 others — read 23 August 2026
no system is safe // cybersec
@nsis_cybersec · 21,198
Telegram ranks this channel #15 of 71 here — alongside 70 others — read 23 September 2026
PulSe
@Pulsechanel · 20,003
Telegram ranks this channel #16 of 69 here — alongside 68 others — read 29 September 2026
Termux, please
@termuxplz0x41 · 32,422
Telegram ranks this channel #18 of 54 here — alongside 53 others — read 4 September 2026
Этичный Хакер
@hack_less · 243,215
Telegram ranks this channel #21 of 81 here — alongside 80 others — read 12 August 2026
КиберДед official
@deedcoin_club · 22,983
Telegram ranks this channel #22 of 84 here — alongside 83 others — read 25 September 2026
infosec
@it_secur · 63,349
Telegram ranks this channel #22 of 81 here — alongside 80 others — read 22 August 2026
IT Portal
@IT_Portal · 118,869
Telegram ranks this channel #25 of 78 here — alongside 77 others — read 15 August 2026
Social Engineering
@Social_engineering · 124,717
Telegram ranks this channel #27 of 82 here — alongside 81 others — read 13 August 2026
Mycroft Intelligence
@mycroftintel · 20,700
Telegram ranks this channel #28 of 76 here — alongside 75 others — read 25 September 2026
Интернет-Розыск
@irozysk · 45,743
Telegram ranks this channel #28 of 79 here — alongside 78 others — read 27 August 2026
Linux Academy
@linuxacademiya · 28,654
Telegram ranks this channel #29 of 84 here — alongside 83 others — read 9 September 2026
S.E.Book
@S_E_Book · 23,100
Telegram ranks this channel #30 of 64 here — alongside 63 others — read 19 September 2026
Bash Days | Linux | DevOps
@bashdays · 23,627
Telegram ranks this channel #30 of 94 here — alongside 93 others — read 18 September 2026

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

“Белый хакер” (@bezopasno_soft), 29,631 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/bezopasno_soft.

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.