Telegram RegisterThe public register of Telegram
Telegram profile photo for КИБЕР МЕДИА

Channel

КИБЕР МЕДИА

@secmedia

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

5,929subscribers

+111 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001515177728
TypeChannel
Username@secmedia
Created16 November 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live7 September 2026
Measurements held10
Confirmed unchanged1 time, most recently 7 September 2026
On Telegramt.me/secmedia

Growth

5,8005,9295,864.56 August 2026 — 5,818 subscribers6 August 2026 — 5,819 subscribers9 August 2026 — 5,816 subscribers11 August 2026 — 5,809 subscribers14 August 2026 — 5,803 subscribers18 August 2026 — 5,805 subscribers24 August 2026 — 5,807 subscribers30 August 2026 — 5,804 subscribers2 September 2026 — 5,800 subscribers7 September 2026 — 5,929 subscribers6 August 20267 September 2026
10 measurements spanning 32 days, net +111. 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,781–5,948 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Sept 2026, 01:205,929+129
2 Sept 2026, 10:165,800-4
30 Aug 2026, 10:565,804-3
24 Aug 2026, 06:335,807+2
18 Aug 2026, 06:525,805+2
14 Aug 2026, 21:355,803-6
11 Aug 2026, 19:585,809-7
9 Aug 2026, 06:415,816-3
6 Aug 2026, 09:115,819+1
6 Aug 2026, 04:355,818first reading

Engagement

36 posts held, back to 29 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.44%
avg views ÷ 5,929 subscribers
Avg views / post
323
7 posts measured
Reaction rate
1.15%
reactions ÷ views · ER floor
Posts in window
7
of 36 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 11 August 2026
Posts held36 (29 July 202611 August 2026)
Views total2,259
Reactions total26
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 03:50 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

128 reactions across 30 posts, in 18 distinct kinds. The most used accounts for 19.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2519.5%
😁2217.2%
🤔2116.4%
118.59%
😢86.25%
🔥75.47%
💊64.69%
🎉53.91%
🙈53.91%
👌43.13%
🤬32.34%
🏆21.56%
💯21.56%
😍21.56%
🤯21.56%
👏10.781%
🕊10.781%
🤝10.781%

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

Measured over the 36 most recent posts we hold, published 29 July 2026 to 11 August 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.

Recent posts

11 Aug 2026, 17:30 UTC169 views1 reactionsread 12 August 2026
Video

⌨️ Почти 40% запросов сотрудников к публичным ИИ содержат конфиденциальные данные — исследование Обращения содержали: ▪️ 41% — исходный код и конфигурации, ▪️ 30% — персональные, финансовые и другие чувствительные сведения, ▪️ 18% — интеллектуальную собственность, ▪️ 11% — пароли, токены и API-ключи. И о каком кибербезе мы говорим... 😎 Здесь о кибербезе

💯1

11 Aug 2026, 12:40 UTC328 views11 reactionsread 12 August 2026
Photo

👀 11-летняя школьница обошла родительский контроль с помощью Claude Когда YouTube упёрся в лимит экранного времени, девочка попросила нейросеть собрать отдельный браузер на Electron и Chromium — на него ограничение уже не распространялось. 😎 Здесь о кибербезе

😁6🎉2😍2🤔1

11 Aug 2026, 08:02 UTC353 views5 reactionsread 12 August 2026
Photo

🗃 Для M2M-SIM-карт в России хотят ввести отдельные правила Минцифры предлагает создать специальный реестр таких SIM-карт и обязать операторов передавать данные о подключённых устройствах. Это должно отделить машинные подключения от обычных абонентских номеров, упростить их контроль и повысить безопасность IoT-инфраструктуры. 😎 Здесь о кибербезе

😢5

10 Aug 2026, 16:15 UTC364 views1 reactionsread 12 August 2026
Photo

🤖 Российским разработчикам ИИ готовят льготы Власти обсуждают упрощённые условия господдержки (от подачи документов до аренды ЦОД) и единые критерии, по которым модели смогут получать национальный или суверенный статус. Основные нормы закона начнут действовать с 1 сентября 2026 года, часть требований — с марта 2027-го. 😎 Здесь о кибербезе

🤔1

10 Aug 2026, 11:03 UTC351 views2 reactionsread 12 August 2026
Photo

🎼 Когда ИБ-инструменты играют вразнобой: зачем защите нужен «дирижёр» Решения могут хорошо выполнять свои задачи по отдельности, но без интеграции не складываются в единую систему защиты. В итоге аналитикам приходится переключаться между консолями, вручную собирать контекст и тратить время на рутину. ➡️ Разобрались с экспертами: почему так происходит и какие «дирижёры» могут собрать ИБ-инфраструктуру в единый оркес

1💯1

10 Aug 2026, 07:56 UTC329 views5 reactionsread 12 August 2026
Photo

✉️ Обычный CSS в письмах научился вмешиваться в интерфейс Gmail и Outlook Вредоносный CSS внутри HTML-письма может выходить за его границы: например, подменять элементы веб-почты или помогать красть данные. Часть уязвимостей исправили, но некоторые на момент исследования всё ещё работали. 😎 Здесь о кибербезе

🤔2🕊1🤬1🤯1

8 Aug 2026, 17:34 UTC359 views1 reactionsread 12 August 2026
Photo

Полезные интервью и статьи недели одним списком ⤵️ ➡️ Безопасная автоматизация процессов в 2026 году: почему классической изоляции уже недостаточно ➡️ Невидимый щит: как выбрать и настроить DNS-сервер для защиты и ускорения домашней сети в 2026 году ➡️ Собственный антифрод против коробочных решений: когда финтеху пора писать систему самостоятельно ➡️ SSL/TLS и HTTPS 2026: анатомия протоколов, новые правила сертиф

1

8 Aug 2026, 12:45 UTC334 views4 reactionsread 12 August 2026

🏦 Банки будут блокировать переводы при обнаружении вредоносного ПО на устройстве С 1 марта наличие вредоноса на устройстве клиента станет новым признаком подозрительной операции. Банк должен будет остановить перевод и запросить подтверждение. При этом проверять устройства на вредоносное ПО банки смогут только с согласия клиентов. 😎 Здесь о кибербезе

🎉2🤔1🤬1

7 Aug 2026, 18:35 UTC362 views1 reactionsread 12 August 2026
Photo

Список интересных мероприятий от Кибер Медиа ➡️ Вебинар «Надёжность, качество, безопасность ПО: методология и инструменты» Вебинар о создании безопасного ПО: DevSecOps, качественный код, ИИ-инструменты, регуляторика и методы анализа программ. 12 августа онлайн. ➡️ Финансовая устойчивость бизнеса: управление цифровыми рисками Панельная дискуссия о том, как оценивать цифровые риски, снижать ущерб от инцидентов и прев

1

7 Aug 2026, 12:50 UTC323 views2 reactionsread 12 August 2026
Photo

📱 Как проверить смартфон перед покупкой и не нарваться на проблемное устройство Проверка IMEI помогает отсеять часть рисков, но сама по себе не гарантирует, что телефон юридически и технически чист: за внешне исправным смартфоном могут скрываться проблемы с прошивкой, материнской платой или происхождением. В материале разобрали, где искать оригинальный IMEI, как его проверить и какие ещё признаки помогут заметить с

👍1🤔1

7 Aug 2026, 08:00 UTC333 views7 reactionsread 12 August 2026
Photo

🤖 Джеффри Хинтон предупредил о риске потери контроля над ИИ Нобелевский лауреат считает, что по мере развития модели будут становиться сложнее и эффективнее обходить ограничения разработчиков. Отдельный риск он видит в автономных ИИ-агентах, которые уже способны находить уязвимости и действовать за пределами ожидаемого сценария. Как считаете, риск реален или пока больше страшилка? 👍 — Все так и будет 🤔 — Пока преув

👍3🤔3💊1

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

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.

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,214
Telegram ranks this channel #5 of 82 here — alongside 81 others — read 4 September 2026
Positive Hack Days Media
@positivehackmedia · 30,846
Telegram ranks this channel #32 of 88 here — alongside 87 others — read 6 September 2026
Хакер — Xakep.RU
@xakep_ru · 39,389
Telegram ranks this channel #34 of 83 here — alongside 82 others — read 30 August 2026
SecAtor
@true_secator · 41,627
Telegram ranks this channel #42 of 78 here — alongside 77 others — read 29 August 2026
Вестник Киберполиции России
@cyberpolice_rus · 83,951
Telegram ranks this channel #43 of 92 here — alongside 91 others — read 18 August 2026
Белый хакер
@bezopasno_soft · 29,691
Telegram ranks this channel #45 of 78 here — alongside 77 others — read 8 September 2026
Пост Лукацкого
@alukatsky · 37,739
Telegram ranks this channel #46 of 89 here — alongside 88 others — read 31 August 2026
SecurityLab.ru
@SecLabNews · 83,998
Telegram ranks this channel #48 of 90 here — alongside 89 others — read 18 August 2026
Codeby
@codeby_sec · 36,935
Telegram ranks this channel #52 of 76 here — alongside 75 others — read 1 September 2026
infosec
@it_secur · 61,439
Telegram ranks this channel #53 of 81 here — alongside 80 others — read 22 August 2026
OSINT mindset
@osint_mindset · 64,457
Telegram ranks this channel #53 of 83 here — alongside 82 others — read 21 August 2026
Life-Hack - Хакер
@haccking · 63,216
Telegram ranks this channel #54 of 85 here — alongside 84 others — read 21 August 2026
Этичный Хакер
@hack_less · 228,204
Telegram ranks this channel #61 of 81 here — alongside 80 others — read 12 August 2026

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

“КИБЕР МЕДИА” (@secmedia), 5,929 subscribers as measured 7 September 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.