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 12 September 2026 and assigned it the closest of 31 fixed categories, at 90% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
22 measurements spanning 94 days, net +273. 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 5,751–6,175 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)
Subscribers
Change
8 Nov 2026, 06:57
6,091
-19
5 Nov 2026, 01:59
6,110
+1
29 Oct 2026, 20:30
6,109
-8
26 Oct 2026, 12:27
6,117
-3
23 Oct 2026, 21:06
6,120
-3
20 Oct 2026, 17:27
6,123
-3
14 Oct 2026, 17:38
6,126
+49
10 Oct 2026, 22:36
6,077
+141
4 Oct 2026, 20:57
5,936
+34
25 Sept 2026, 20:17
5,902
-13
15 Sept 2026, 11:19
5,915
-5
11 Sept 2026, 16:20
5,920
-9
7 Sept 2026, 01:20
5,929
+129
2 Sept 2026, 10:16
5,800
-4
30 Aug 2026, 10:56
5,804
-3
24 Aug 2026, 06:33
5,807
+2
18 Aug 2026, 06:52
5,805
+2
14 Aug 2026, 21:35
5,803
-6
11 Aug 2026, 19:58
5,809
-7
9 Aug 2026, 06:41
5,816
first reading
Engagement
56 posts held, back to 29 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 13 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
8.80%
avg views ÷ 6,091 subscribers
Avg views / post
536
20 posts measured
Reaction rate
1.21%
reactions ÷ views · ER floor
Posts in window
20
of 56 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 18 of 20 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 5 November 2026
Posts held
56 (29 July 2026 – 5 November 2026)
Views total
10,725
Reactions total
119
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
5 Nov 2026, 16:49 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.
Reaction mix
247 reactions across 48 posts, in 19 distinct kinds. The most used accounts for 21.1% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
52
21.1%
🤔
34
13.8%
😁
31
12.6%
❤
21
8.50%
🔥
16
6.48%
🤯
16
6.48%
🙈
12
4.86%
💯
10
4.05%
😢
10
4.05%
🙏
9
3.64%
👌
8
3.24%
💊
6
2.43%
🎉
5
2.02%
👏
5
2.02%
🤝
4
1.62%
🤬
3
1.21%
🏆
2
0.81%
😍
2
0.81%
🕊
1
0.405%
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 53 of the 56 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 292 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 56 most recent posts we hold, published 29 July 2026 to 5 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
3.57%
2 of 56 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
1,470
over 2 measured posts
Median views · rest
422
over 54 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
erid
Posts
First seen
Last seen
2SDnjdTjNe8
1
5 November 2026
5 November 2026
2SDnjeMZEbe
1
3 November 2026
3 November 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 56 most recent posts we hold, published 29 July 2026 to 5 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: 1 of 20 posts held from the last 30 days (5.00%) 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).
🗣 Как выстроить эффективный AppSec?
Даже с развитием ИИ ключевым остаётся вопрос управления процессами: от сканирования кода до выпуска релизов.
➡ Читайте интервью на сайте
Максим Козлов, технический директор GitFlic, рассказал:
▫ почему внедрение SAST, DAST и SCA ещё не гарантирует безопасность разработки,
▫ как выстроить контроль уязвимостей в CI/CD и технически блокировать небезопасные релизы,
▫ какие риски не…
Конференция «Сетевая безопасность 2026» — для тех, кто строит сети и кто их защищает
⏺ 24 ноября, Москва | Регистрация
Сетевикам нужна быстрая и управляемая сеть, безопасникам — сеть под контролем. Конференция «Сетевая безопасность» в равной мере ориентирована на обе команды. В прошлом году её посетили более 1000 специалистов по кибербезопасности, сетевых инженеров и архитекторов, разработчиков ИБ-решений. В програ…
⚠️ Бэкдор в прошивках заразил более 1,3 млн устройств
Исследователи раскрыли ботнет XCPE, который распространялся через цепочку поставок. Производитель приставок намеренно встраивал вредонос в прошивки, а затем продавал доступ к ним.
Бэкдор работал с правами android.uid.system, восстанавливался после удаления и использовал HTTP и MQTT для связи с C2. Операторы могли выполнять shell-команды, отключать Play Protect, …
🔎 Злоумышленник вошёл под чужой учетной записью
Как обнаружить подмену?
Традиционные СЗИ не всегда могут отличить действия пользователя от активности атакующего.
UEBA-системы анализируют поведение сотрудников и устройств, выявляют подозрительные отклонения, которые другие средства защиты могли пропустить.
➡️ Подробности — в материале.
😎 Здесь о кибербезе
🔐 Почему администраторы стали главной целью киберпреступников?
39% киберинцидентов за январь–сентябрь 2025 года связаны с использованием или компрометацией привилегированных учётных записей.
Как защитить администраторские учётки? Вместе с экспертом разбираем основные способы атак, возможности PAM-систем и требования регуляторов — в материале.
😎 Здесь о кибербезе
🔎 Найти уязвимость — полдела. А что дальше?
Современные VM-системы помогают определять приоритеты устранения уязвимостей, контролировать небезопасные конфигурации и автоматизировать применение исправлений. Однако далеко не все решения поддерживают эти возможности.
Какие решения предлагают отечественные разработчики — в нашем исследовании.
😎 Здесь о кибербезе
⚠️ Beget сообщил о потере всех данных в облаке после кибератаки
В ночь на 2 ноября злоумышленники получили доступ к управляющему контуру инфраструктуры Beget и запустили обнуляющие скрипты. Данные VPS, S3 и Kubernetes утрачены, как и настройки CDN и IP. При этом файловые резервные копии сохранились, а бинарные бэкапы VPS потеряны полностью.
По данным провайдера, признаков скачивания пользовательских данных пока не …
✅️ Удобные ответы про XDR
12 ноября в 11:00 «Лаборатория Касперского» проведёт стрим «Удобные ответы про XDR» для тех, кто строит комплексную киберзащиту бизнеса. В прямом эфире команда продукта покажет новые возможности единой платформы безопасности в решении Kaspersky Symphony XDR и поделится планами по его развитию.
А чтобы лучше подготовиться к стриму – смотрите одноименный видеопроект, в котором специальная по…
🚗 Хакеры блокируют автомобили Li Auto в России и требуют выкуп
Злоумышленники перехватывают мастер-аккаунты владельцев китайских кроссоверов, через которые можно управлять функциями автомобиля. После компрометации учётной записи у некоторых машин гаснут экраны, отключается климат-контроль, а иногда возникают проблемы с запуском двигателя.
За возвращение доступа мошенники требуют 35–45 тысяч рублей. По данным Autone…
🔎 Киберриск высокий: сколько денег из-за него может потерять компания?
Одни SGRC помогают оценивать вероятность угроз и возможный финансовый ущерб, в том числе по методике FAIR. А вот моделирование рисков методом Монте-Карло поддерживает только одна из шести систем в нашем исследовании.
Какие инструменты оценки рисков предлагают российские SGRC и чем отличаются их возможности? Исследование — в подробном обзоре.
😎 …
🌐 Российским сервисам разрешили временно использовать зарубежные дата-центры
Указ подписал Владимир Путин. Использовать иностранные дата-центры можно будет только по решению правительственной подкомиссии, согласованному с ФСБ.
Кроме того, частные российские дата-центры должны зарезервировать 10% площадей и мощностей. Зарезервированные мощности по решению подкомиссии должны быть предоставлены для поддержки работы ро…
⚠️ Масштабный сбой Beget нарушил работу сайтов по всему Рунету
Ночью 2 ноября у одного из крупнейших российских хостинг-провайдеров произошёл серьёзный сбой. Пользователи столкнулись с недоступностью сайтов, VPS, почтовых сервисов и DNS. Проблемы затронули даже сайт системы маркировки товаров «Честный знак». На серверах провайдера размещено более 450 тысяч сайтов, однако сколько из них пострадало, пока неизвестно.
…
🤔3👌2
Showing the 12 most recent of 56 posts we hold for @secmedia. 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.
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 6 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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.
Пакет Безопасности @package_security · 33,728 Telegram ranks this channel #5 of 82 here — alongside 81 others — read 4 September 2026
КиберДед official @deedcoin_club · 23,011 Telegram ranks this channel #23 of 84 here — alongside 83 others — read 25 September 2026
Kaspersky @kasperskylab_ru · 28,873 Telegram ranks this channel #29 of 96 here — alongside 95 others — read 9 September 2026
Листок бюрократической защиты информации @bureaucraticsecurity · 19,134 Telegram ranks this channel #32 of 98 here — alongside 97 others — read 4 October 2026
Positive Hack Days Media @positivehackmedia · 30,042 Telegram ranks this channel #32 of 88 here — alongside 87 others — read 6 September 2026
Борьба с киберпреступностью | F6 @f6_cybersecurity · 22,363 Telegram ranks this channel #34 of 85 here — alongside 84 others — read 21 September 2026
Хакер — Xakep.RU @xakep_ru · 40,313 Telegram ranks this channel #34 of 83 here — alongside 82 others — read 30 August 2026
Positive Technologies @Positive_Technologies · 29,449 Telegram ranks this channel #35 of 87 here — alongside 86 others — read 9 September 2026
SecAtor @true_secator · 42,213 Telegram ranks this channel #42 of 78 here — alongside 77 others — read 29 August 2026
Вестник Киберполиции России @cyberpolice_rus · 82,852 Telegram ranks this channel #43 of 92 here — alongside 91 others — read 18 August 2026
S.E.Reborn @S_E_Reborn · 22,459 Telegram ranks this channel #45 of 66 here — alongside 65 others — read 20 September 2026
IT и безопасность @tg_security · 26,812 Telegram ranks this channel #45 of 91 here — alongside 90 others — read 12 September 2026
Белый хакер @bezopasno_soft · 29,601 Telegram ranks this channel #45 of 78 here — alongside 77 others — read 8 September 2026
Пост Лукацкого @alukatsky · 38,465 Telegram ranks this channel #46 of 89 here — alongside 88 others — read 31 August 2026
SecurityLab.ru @SecLabNews · 86,532 Telegram ranks this channel #48 of 90 here — alongside 89 others — read 18 August 2026
Codeby @codeby_sec · 37,083 Telegram ranks this channel #52 of 76 here — alongside 75 others — read 1 September 2026
infosec @it_secur · 63,440 Telegram ranks this channel #53 of 81 here — alongside 80 others — read 22 August 2026
OSINT mindset @osint_mindset · 64,889 Telegram ranks this channel #53 of 83 here — alongside 82 others — read 21 August 2026
Life-Hack - Хакер @haccking · 63,021 Telegram ranks this channel #54 of 85 here — alongside 84 others — read 21 August 2026
no system is safe // cybersec @nsis_cybersec · 21,166 Telegram ranks this channel #57 of 71 here — alongside 70 others — read 23 September 2026
Этичный Хакер @hack_less · 243,065 Telegram ranks this channel #61 of 81 here — alongside 80 others — read 12 August 2026
This channel appears in 21 seed channels' Telegram-generated recommendation lists in total. 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 8 November 2026 — this
entry's latest reading, not the date you are reading this.
“КИБЕР МЕДИА” (@secmedia), 6,091 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/secmedia.
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.