Telegram RegisterThe public register of Telegram
Telegram profile photo for no system is safe // cybersec

Channel

no system is safe // cybersec

@nsis_cybersec

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

21,198subscribers

-171 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001718662771
TypeChannel
Username@nsis_cybersec
DescriptionЗнайте, что ни одна система не является безопасной. Сотрудничество: @workhouse_price Реклама на Telega.in : https://telega.in/c/nsis_cybersec РКН: https://clck.ru/3FtT8z
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live7 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/nsis_cybersec

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

21,19821,69221,4456 August 2026 — 21,369 subscribers6 August 2026 — 21,387 subscribers7 August 2026 — 21,423 subscribers8 August 2026 — 21,426 subscribers9 August 2026 — 21,428 subscribers10 August 2026 — 21,442 subscribers11 August 2026 — 21,484 subscribers12 August 2026 — 21,487 subscribers14 August 2026 — 21,498 subscribers15 August 2026 — 21,492 subscribers17 August 2026 — 21,505 subscribers18 August 2026 — 21,510 subscribers19 August 2026 — 21,487 subscribers20 August 2026 — 21,485 subscribers21 August 2026 — 21,487 subscribers24 August 2026 — 21,498 subscribers25 August 2026 — 21,499 subscribers26 August 2026 — 21,513 subscribers27 August 2026 — 21,507 subscribers28 August 2026 — 21,505 subscribers29 August 2026 — 21,509 subscribers31 August 2026 — 21,512 subscribers2 September 2026 — 21,515 subscribers3 September 2026 — 21,520 subscribers5 September 2026 — 21,652 subscribers8 September 2026 — 21,676 subscribers11 September 2026 — 21,692 subscribers13 September 2026 — 21,678 subscribers17 September 2026 — 21,653 subscribers27 September 2026 — 21,518 subscribers4 October 2026 — 21,516 subscribers9 October 2026 — 21,446 subscribers13 October 2026 — 21,398 subscribers14 October 2026 — 21,387 subscribers15 October 2026 — 21,359 subscribers16 October 2026 — 21,352 subscribers17 October 2026 — 21,350 subscribers18 October 2026 — 21,341 subscribers19 October 2026 — 21,331 subscribers20 October 2026 — 21,319 subscribers21 October 2026 — 21,301 subscribers22 October 2026 — 21,296 subscribers23 October 2026 — 21,291 subscribers24 October 2026 — 21,278 subscribers25 October 2026 — 21,262 subscribers27 October 2026 — 21,320 subscribers29 October 2026 — 21,296 subscribers30 October 2026 — 21,290 subscribers31 October 2026 — 21,278 subscribers1 November 2026 — 21,265 subscribers2 November 2026 — 21,249 subscribers3 November 2026 — 21,238 subscribers4 November 2026 — 21,224 subscribers5 November 2026 — 21,218 subscribers6 November 2026 — 21,206 subscribers7 November 2026 — 21,198 subscribers6 August 20267 November 2026
56 measurements spanning 93 days, net -171. 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 21,124–21,766 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 56
Measured (UTC)SubscribersChange
7 Nov 2026, 10:5021,198-8
6 Nov 2026, 10:1621,206-12
5 Nov 2026, 10:2921,218-6
4 Nov 2026, 06:5921,224-14
3 Nov 2026, 08:5521,238-11
2 Nov 2026, 07:4521,249-16
1 Nov 2026, 04:4921,265-13
31 Oct 2026, 07:2121,278-12
30 Oct 2026, 04:0821,290-6
29 Oct 2026, 06:1821,296-24
27 Oct 2026, 00:5621,320+58
25 Oct 2026, 21:4421,262-16
24 Oct 2026, 20:0621,278-13
23 Oct 2026, 20:1121,291-5
22 Oct 2026, 18:5721,296-5
21 Oct 2026, 17:3721,301-18
20 Oct 2026, 14:4621,319-12
19 Oct 2026, 17:4821,331-10
18 Oct 2026, 17:0921,341-9
17 Oct 2026, 18:1921,350first reading

Engagement

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

ERR · 30 days
9.33%
avg views ÷ 21,198 subscribers
Avg views / post
1,980
36 posts measured
Reaction rate
0.368%
reactions ÷ views · ER floor
Posts in window
36
of 153 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 7 November 2026
Posts held153 (28 July 2026 – 7 November 2026)
Views total71,168
Reactions total262
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Nov 2026, 04:08 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
≈2,340
Videos
≈64
Links
≈2,360

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

Reaction mix

1,214 reactions across 153 posts, in 5 distinct kinds. The most used accounts for 36.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍44436.6%
❤39732.7%
🔥21818.0%
👎1149.39%
😁413.38%

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

Measured over the 153 most recent posts we hold, published 28 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
1.96%
3 of 153 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
1,820
over 3 measured posts
Median views · rest
1,810
over 150 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
2VtzqwZFfxg122 September 202622 September 2026
2W5zFHPtuBP113 August 202613 August 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 153 most recent posts we hold, published 28 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: 2 of 36 posts held from the last 30 days (5.56%) 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, 17:21 UTC≈1,070 views5 reactionsread 8 November 2026
Photo

😈 Автоматизируем поиск уязвимостей в исходном коде Bandit — инструмент статического анализа безопасности (SAST), который помогает находить потенциально опасные конструкции в Python-проектах ещё до запуска приложения Утилита анализирует исходный код через AST (абстрактное синтаксическое дерево) и проверяет его на распространённые проблемы безопасности Что умеет находить: 🔵Hardcoded Secrets — пароли и другие секрет…

❤5

7 Nov 2026, 13:38 UTC≈1,290 views5 reactionsread 8 November 2026
Photo

😈 ИИ-агенты OpenAI создали эксплоиты для 948 уязвимостей в ядре Linux В OpenAI рассказали о масштабном эксперименте, проведенном с моделью GPT-6 Cyber, предназначенной для решения задач в области кибербезопасности Для тестирования создали агентный пайплайн, который самостоятельно выбирал доступные непривилегированным пользователям участки ядра, искал в них потенциальные уязвимости, воспроизводил их в песочнице, про…

❤3👎1🔥1

6 Nov 2026, 18:39 UTC≈1,680 views4 reactionsread 8 November 2026
Photo

😈 Большая база по Threat Hunting и Detection Engineering Awesome Threat Detection — это курируемый список, содержащий подборку полезных инструментов, руководств, учебных материалов, платформ и фреймворков для обнаружения киберугроз и «охоты на угрозы» Внутри собраны: 🔵Threat Hunting tools — HELK, DetectionLab, Security Onion и другие 🔵Detection Rules — Sigma, Elastic, Splunk, MITRE CAR, YARA 🔵Windows и Sysmon — …

👍2🔥2

6 Nov 2026, 13:42 UTC≈1,750 views7 reactionsread 8 November 2026
Photo

😈 Сети с нулевым доверием. Построение безопасных систем в ненадежных сетях | 2-е издание 🔵Раскрыта парадигма информационной безопасности сетей с нулевым доверием (Zero Trust), полностью пересматривающая традиционные подходы к защите данных; 🔵Изложены фундаментальные принципы, включая непрерывную верификацию, минимальные привилегии и микросегментацию; 🔵Приведены практические сценарии внедрения Zero Trust, включая …

❤4👍2👎1

5 Nov 2026, 15:01 UTC≈1,980 views5 reactionsread 8 November 2026
Photo

😈 Как настроить Windows для запуска любых нейросетей на своём компьютере Сегодня мы рассмотрим: 1. Можно ли запускать локальные нейросети на Windows 2. Установка видеодрайвера 3. Установка CUDA (не требуется) 4. Установка WSL 2 и основные команды по работе с дистрибутивами Linux 5. Установка Linux в WSL 2 6. Доступ к видеокарте и CUDA из WSL 7. Установка в Linux в WSL необходимых пакетов для запуска не…

🔥5

5 Nov 2026, 08:01 UTC≈1,960 views5 reactionsread 8 November 2026
Photo

😈 Автоматизируем веб-скрейпинг сайтов Requests-HTML — это библиотека для Python, созданная Кеннетом Рейтцем (автором самой библиотеки Requests) для упрощения веб-скрейпинга Веб-скрейпинг — это автоматизированный процесс сбора и извлечения данных с веб-сайтов. Вместо ручного копирования информации с каждой страницы этим занимаются специальные программы или боты-скрейперы Они загружают HTML-код страницы, анализируют…

👍3❤2

4 Nov 2026, 17:50 UTC≈2,050 views4 reactionsread 8 November 2026
Photo

😈 MEGANews: самые важные события в мире инфосека за октябрь В этом месяце: 🔵Кри­тичес­кие уяз­вимос­ти PHP2Shell и Node2Shell пос­тавили под угро­зу мил­лионы сер­веров и при­ложе­ний; 🔵Хакеры зах­ватили более 300 выход­ных узлов Tor для перех­вата SSH-соеди­нений; 🔵Спе­циалис­ты ком­пании Bitdefender выяви­ли вре­донос­ную кам­панию Midnight Mimosa, которая зат­ронула тысячи бюд­жетных Android-смар­тфо­нов более…

👍4

4 Nov 2026, 12:10 UTC≈2,090 views6 reactionsread 8 November 2026
Photo

😈 Сильная подборка для DFIR / Incident Respons Awesome Incident Response — один из самых известных GitHub-списков по Incident Response и Digital Forensics Incident Response (реагирование на инциденты в информационной безопасности) — это структурированный процесс обнаружения, анализа, сдерживания, устранения и расследования кибератак, утечек данных или других нарушений безопасности Внутри собраны инструменты и мате…

👍4❤2

3 Nov 2026, 18:22 UTC≈2,210 views6 reactionsread 8 November 2026
Photo

🟦 Защита ядра операционных систем в условиях противодействия Книга посвящена решению одной из наиболее актуальных проблем безопасности — защите ядра Windows от сложных низкоуровневых угроз ➖Исследование выполнено в двух взаимосвязанных направлениях: защите памяти ядра от манипуляций со стороны драйверов и обнаружении скрытых гипервизоров, использующих технологию аппаратной виртуализации Основана на многолетних ис…

👍4👎2

3 Nov 2026, 09:51 UTC≈2,310 views8 reactionsread 8 November 2026
Photo

😈 Троян в твоих ушах: как угнать WhatsApp и Amazon через беспроводные наушники Содержание статьи: 🔵Искали медь, а нашли золото — Сюрпризы в прошивке — «Хирургическая операция» и сопоставление чипов 🔵Android как Розеттский камень — Попытки эксплуатации протокола RACE и Bumble 🔵Grand Theft Headphones — Кража Link Key и угон аккаунта — Прослушка: микрофон как оружие 🔵Угон WhatsApp 🔵Экосистема безответственнос…

👍8

2 Nov 2026, 18:36 UTC≈2,370 views9 reactionsread 8 November 2026
Photo

😈 Инструмент обфускации кода Обфускация — это преднамеренное запутывание кода программы, при котором он становится трудночитаемым для человека и автоматических анализаторов, но сохраняет свою исходную функциональность JSFuck — это эзотерический стиль программирования и инструмент для JavaScript, который позволяет написать и выполнить любой код, используя всего шесть символов: [, ], (, ), ! и + В JavaScript действу…

❤5👍3🔥1

2 Nov 2026, 13:36 UTC≈2,430 views6 reactionsread 8 November 2026
Photo

😈 Официальное расширение Claude Code на маркетплейсе Cursor подменили версией с бэкдором — Через маркетплейс расширений для Cursor на протяжении почти 12 часов распространялась вредоносная версия официального расширения Anthropic Claude Code, за это время ее успели установить примерно 5000 пользователей Малварь пыталась развернуть SSH-бэкдор в Windows, macOS и Linux. Запускалась автоматически при загрузке расширен…

❤3🔥3

Showing the 12 most recent of 153 posts we hold for @nsis_cybersec. 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

@nsis_cybersec 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
6 November 2026
Most recent edit
6 November 2026

Posts recorded as deleted after publishing

We recorded 11 posts on @nsis_cybersec 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
6 November 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
4

Forward network

Republished by

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

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

Архив Безопасника
@secure_archive · 10,973
#1
infosec
@it_secur · 63,375
#2
Social Engineering
@Social_engineering · 124,717
#3
Mr. Robot
@elliot_cybersec · 38,931
#4
Лаборатория хакера
@lab_hack · 25,449
#5
Записки Безопасника
@infosec_globe · 17,903
#6
CyberINS // Лаборатория ИБешника
@cyberins · 11,502
#7
S.E.Reborn
@S_E_Reborn · 22,458
#8
Inf0 | ИБ, OSINT
@info_cybersecurity · 10,784
#9
White Hat
@kind_hack · 11,927
#10
Похек
@poxek · 17,283
#11
Admin Guides | Сисадмин
@admguides · 12,049
#12
SecurityLab.ru
@SecLabNews · 86,460
#13
ИБ Книга | Библиотека ИБ
@itbook_library · 15,945
#14
Белый хакер
@bezopasno_soft · 29,628
#15
S.E.Book
@S_E_Book · 23,100
#16
ZeroDay | Кибербезопасность
@cybersec_academy · 42,632
#17
infosecurity
@tg_infosec · 26,848
#18
Codeby
@codeby_sec · 37,055
#19
Life-Hack - Хакер
@haccking · 63,033
#20
Kali Linux
@linuxkalii · 55,832
#21
Open Source
@open_source_friend · 52,630
#22
Чёрный Треугольник
@black_triangle_tg · 63,954
#23
Russian OSINT
@Russian_OSINT · 48,496
#24
SecAtor
@true_secator · 42,182
#25
Бункер Хакера
@book_academ · 21,298
#26
Project Omega | ИБ
@omega_cybersec · 8,702
#27
Cybred
@cybred · 11,416
#28
AP Security
@ap_security · 4,249
#29
Сетевик Джонни // Network Admin
@iscode · 5,754
#30
Арсенал Безопасника
@arsenal_security · 15,060
#31
Хакер — Xakep.RU
@xakep_ru · 40,287
#32
Серверная Админа | Компьютерные сети
@school_network · 26,426
#33
Пакет Безопасности
@package_security · 33,788
#34
Пост Лукацкого
@alukatsky · 38,422
#35
Архив Программиста
@storage_it · 8,660
#36
SecuriXy.kz
@securixy_kz · 10,377
#37
INSPECTOR | OSINT
@it_fullstak · 11,074
#38
Investigation & Forensic TOOLS
@forensictools · 22,603
#39
PyLinux | Всё о Linux & Python
@pylinux0 · 11,048
#40
Управление Уязвимостями и прочее
@avleonovrus · 12,623
#41
Библиотека Программиста
@code_library · 17,524
#42
NetStalkers
@netstalkerscom · 7,805
#43
Network Admin
@networkadm · 12,355
#44
APT
@APT_Notes · 17,319
#45
Linux Academy
@linuxacademiya · 28,653
#46
Библиотека хакера | Hacking, Infosec, ИБ, информационная безопасность
@hackproglib · 12,614
#47
Blue (h/c)at Café
@bh_cat · 4,001
#48
InfoSec Portal
@cybersecinform · 20,046
#49
Секреты сисадмина | DevOps, Linux, SRE
@sysadmin_library · 25,727
#50
T.Hunter
@tomhunter · 14,173
#51
Склад айтишки
@skladitshki · 7,203
#52
Мыслить как безопасник
@artemov_security · 9,213
#53
GigaHackers
@GigaHack · 2,701
#54
IT Syndicate
@ITSyndicate_23 · 8,493
#55
[PYTHON:TODAY]
@python2day · 63,355
#56
КИБЕР МЕДИА
@secmedia · 6,091
#57
k8s (in)security
@k8security · 13,317
#58
InfoSec Community
@infosec_tg · 10,615
#59
AM Live
@anti_malware · 13,172
#60
Вакансии в ИБ | infosec
@infosec_work · 16,330
#61
PRO:PENTEST
@pro_pentest · 10,225
#62
Утечки информации
@dataleak · 117,811
#63
Бэкдор
@whackdoor · 1,541,494
#64
Python и 1000 уязвимостей
@osint_pythons · 36,471
#65
Bash Days | Linux | DevOps
@bashdays · 23,626
#66
SHADOW:Group
@shadow_group_tg · 11,459
#67
GitHub Community
@github · 155,035
#68
BeholderIsHere Media HUB
@BeholderIsHereHub · 3,250
#69
True OSINT
@trueosint · 10,089
#70
Эксплойт
@exploitex · 2,028,700
#71

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

Mr. Robot
@elliot_cybersec · 38,931
Telegram ranks this channel #3 of 70 here — alongside 69 others — read 31 August 2026
Лаборатория хакера
@lab_hack · 25,449
Telegram ranks this channel #4 of 71 here — alongside 70 others — read 14 September 2026
Termux, please
@termuxplz0x41 · 32,422
Telegram ranks this channel #4 of 54 here — alongside 53 others — read 4 September 2026
CyberYozh
@cyberyozh_official · 62,570
Telegram ranks this channel #8 of 81 here — alongside 80 others — read 21 August 2026
Бункер Хакера
@book_academ · 21,298
Telegram ranks this channel #9 of 72 here — alongside 71 others — read 23 September 2026
S.E.Book
@S_E_Book · 23,100
Telegram ranks this channel #11 of 64 here — alongside 63 others — read 19 September 2026
ZeroDay | Кибербезопасность
@cybersec_academy · 42,632
Telegram ranks this channel #11 of 70 here — alongside 69 others — read 29 August 2026
CYBER HUNTER - Кибербезопасность
@cyberbezopasno · 58,760
Telegram ranks this channel #11 of 50 here — alongside 49 others — read 26 August 2026
Open Source
@open_source_friend · 52,630
Telegram ranks this channel #11 of 87 here — alongside 86 others — read 24 August 2026
Этичный Хакер
@hack_less · 243,215
Telegram ranks this channel #12 of 81 here — alongside 80 others — read 12 August 2026
infosec
@it_secur · 63,375
Telegram ranks this channel #13 of 81 here — alongside 80 others — read 22 August 2026
Белый хакер
@bezopasno_soft · 29,628
Telegram ranks this channel #14 of 78 here — alongside 77 others — read 8 September 2026
Kali Linux
@linuxkalii · 55,832
Telegram ranks this channel #14 of 89 here — alongside 88 others — read 23 August 2026
Кладовка Pavlu
@KladovkaPavlu · 64,670
Telegram ranks this channel #15 of 76 here — alongside 75 others — read 4 September 2026
S.E.Reborn
@S_E_Reborn · 22,458
Telegram ranks this channel #16 of 66 here — alongside 65 others — read 20 September 2026
PulSe
@Pulsechanel · 20,003
Telegram ranks this channel #17 of 69 here — alongside 68 others — read 29 September 2026
Mycroft Intelligence
@mycroftintel · 20,698
Telegram ranks this channel #19 of 76 here — alongside 75 others — read 25 September 2026
InfoSec Portal
@cybersecinform · 20,046
Telegram ranks this channel #20 of 75 here — alongside 74 others — read 2 October 2026
Серверная Админа | Компьютерные сети
@school_network · 26,426
Telegram ranks this channel #21 of 85 here — alongside 84 others — read 12 September 2026
Linux Academy
@linuxacademiya · 28,653
Telegram ranks this channel #21 of 84 here — alongside 83 others — read 9 September 2026
Life-Hack - Хакер
@haccking · 63,033
Telegram ranks this channel #24 of 85 here — alongside 84 others — read 21 August 2026
Social Engineering
@Social_engineering · 124,717
Telegram ranks this channel #25 of 82 here — alongside 81 others — read 13 August 2026
infosecurity
@tg_infosec · 26,848
Telegram ranks this channel #26 of 74 here — alongside 73 others — read 11 September 2026
Интернет-Розыск
@irozysk · 45,743
Telegram ranks this channel #29 of 79 here — alongside 78 others — read 27 August 2026

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

“no system is safe // cybersec” (@nsis_cybersec), 21,198 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/nsis_cybersec.

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.