Telegram RegisterThe public register of Telegram

Channel

BELYAEV_SECURITY

@belyaevsec

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

2,882subscribers

-10 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001983611306
TypeChannel
Username@belyaevsec
CreatedBetween 1 March 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/belyaevsec

Growth

2,8822,8922,8876 August 2026 — 2,892 subscribers6 August 2026 — 2,892 subscribers9 August 2026 — 2,889 subscribers12 August 2026 — 2,882 subscribers6 August 202612 August 2026
4 measurements spanning 6 days, net -10. 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 2,881–2,894 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 00:422,882-7
9 Aug 2026, 11:022,889-3
6 Aug 2026, 05:042,892no change
6 Aug 2026, 04:352,892first reading

Engagement

30 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 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.40%
avg views ÷ 2,882 subscribers
Avg views / post
184
27 posts measured
Reaction rate
1.81%
reactions ÷ views · ER floor
Posts in window
30
of 30 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 August 2026
Posts held30 (29 July 20267 August 2026)
Views total4,981
Reactions total90
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 16:05 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

57 reactions across 17 posts, in 9 distinct kinds. The most used accounts for 35.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥2035.1%
👍1322.8%
712.3%
🤔610.5%
😁35.26%
🏆23.51%
🐳23.51%
👏23.51%
🤝23.51%

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

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

Telegram Stars

Stars received
2
across the posts below
Posts paid on
2
of 27 we hold a reading for · 7%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @belyaevsec. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 30 most recent posts we hold for this entry, published 29 July 2026 to 7 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

7 Aug 2026, 10:46 UTC72 views5 reactionsread 7 August 2026
Forwarded from @EgidaTelecomPhoto

АУУУДИТ уже сделали? 🐺 Большинство компаний узнают об уязвимостях после инцидента. Аудит позволяет найти их раньше. Мы проводим аудит информационной безопасности для государственных организаций, образовательных учреждений и коммерческих компаний. Проверяем, как злоумышленник может попасть в инфраструктуру и какие риски действительно существуют. Что проверяем: • внешний периметр: сайты, VPN, почтовые сервисы и друг

2🔥2🐳1

7 Aug 2026, 09:03 UTC90 views1 reactionsread 7 August 2026

Идентификация снова под прицелом SharePoint и AD FS в июльских и августовских сводках упоминаются не случайно. Идентификационная инфраструктура - это не «еще один сервис», а пропуск в полкомпании. А когда пропуск взломан, атакующий уже ходит почти как сотрудник, только без отдела кадров и совести. Особенно неприятно то, что такие уязвимости часто приводят либо к удаленному выполнению кода, либо к повышению привилег

🔥1

7 Aug 2026, 09:00 UTC73 views1 reactionsread 7 August 2026

VMware: когда падает не сервер, а опора В свежих киберисследованиях снова всплыли критические уязвимости в стеке VMware, в том числе обходной путь аутентификации и потенциальный RCE в компонентах управления. И это не тот случай, когда можно спокойно сказать: «У нас просто один уязвимый хост». Виртуализация - это основа инфраструктуры. Если злоумышленник доберется до vCenter или соседних компонентов управления, посл

👍1

7 Aug 2026, 07:07 UTC73 views2 reactionsread 7 August 2026
Forwarded from @codeibnewsPhoto

В подкасте Дмитрия Беляева вышла серия выпусков, в которых обсуждаются ключевые темы для специалистов по информационной безопасности — от построения команд и коммуникаций до развития ИБ-сообществ и роли публичности в профессии. Собрали их в одной подборке. 🎙 Выпуск №19. Что скрывают про офлайн в кибербезопасности? Гость — Мария Шимко, основатель Unlim Events Соведущая — Екатерина Бузаева Гости обсудили, как меняют

👏1🔥1

7 Aug 2026, 06:31 UTC80 views0 reactions1 Starread 7 August 2026

Друзья, теперь я есть и на Дзене, расширяемся 🎉 Полный перечень медиа-площадок опубликован тут.

7 Aug 2026, 04:00 UTC102 views2 reactionsread 7 August 2026
Photo

Уязвимость с максимальным баллом опасности нашли в оборудовании Arista - и её уже используют CVSS 10 из 10 - это как получить от школьного учителя не пятёрку с плюсом, а формальное признание, что хуже просто не бывает. Именно такую оценку получила уязвимость CVE-2026-16812 в Arista VeloCloud Orchestrator - критическая инъекция команд операционной системы, позволяющая захватить устройство без всякой авторизации. CIS

🔥1🤔1

6 Aug 2026, 09:50 UTCviews —

BELYAEV_SECURITY pinned «Запись декабрьская, а выходит только сейчас - самое время посмотреть, как мы уже тогда предупреждали о киберугрозах 2026. В этом выпуске 8 канала, на пронрамме «Калейдоскопа» мы с ведущими разбираем реальные кейсы мошенников, фишинг через мессенджеры, сливы…»

6 Aug 2026, 09:16 UTC138 views3 reactionsread 7 August 2026
Photo

Hyundai Turkey и старый добрый вымогатель CRPx0 заявили о взломе Hyundai Turkey и выложили на сайт с утечками историю о якобы похищенных 1,5 ГБ данных. Для стороннего наблюдателя это очередной эпизод с вымогателем. Для бизнеса - знакомая до дрожи схема: либо платишь, либо твои внутренности становятся контентом на витрине. Почему тема цепляет: - автомобильная отрасль завязана на подрядчиков, HR, производство и ИТ о

🐳1🔥1🤔1

6 Aug 2026, 08:54 UTC127 views2 reactions1 Starread 7 August 2026
Photo

Пока не публиковал, но вы даже не представляете, какие фичи и функции появились в версии 5.5 😏🎉

🏆1🔥1

6 Aug 2026, 05:20 UTC109 views3 reactionsread 7 August 2026
Forwarded from @Belyaev_ST

Запись декабрьская, а выходит только сейчас - самое время посмотреть, как мы уже тогда предупреждали о киберугрозах 2026. В этом выпуске 8 канала, на пронрамме «Калейдоскопа» мы с ведущими разбираем реальные кейсы мошенников, фишинг через мессенджеры, сливы денег в онлайн-играх и схемы, из‑за которых за 2025 год банкам пришлось спасать сотни миллиардов рублей. Говорим простым языком о том, как хакеры читают вашу пс

🏆1👏1🔥1

6 Aug 2026, 04:00 UTC150 views4 reactionsread 7 August 2026
Photo

Хакер запустил ИИ-агента в режиме "без тормозов" - и тот сам взломал Минфин Таиланда Разница между "у нас есть автономный ИИ-агент" и "мы дали ему полный контроль без вопросов" всегда казалась теоретической - до этой недели. Команда Hunt.io и исследователь Bob Diachenko нашли на сервере в Гонконге три открытые директории: 585 файлов, около 470 мегабайт инструментов для атак, украденных учётных данных и, что важнее в

2👍1🤔1

5 Aug 2026, 09:09 UTC161 views1 reactionsread 7 August 2026
Photo

Check Point и неприятный сюрприз для администраторов Check Point SmartConsole тоже оказался в зоне активной эксплуатации: уязвимость CVE-2026-16232 позволяла злоумышленнику получить токен и войти в консоль с правами администратора. Да, это именно тот класс багов, который мгновенно превращает управление безопасностью в зону максимального риска. Особенно неприятно, что уязвимость затронула среды, в которых интерфейсы

👍1

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 24,973 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

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 12 August 2026 — this entry's latest reading, not the date you are reading this.

“BELYAEV_SECURITY” (@belyaevsec), 2,882 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/belyaevsec.

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.