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 11 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 why it has no browse page of its own yet.
Growth
30 measurements spanning 44 days, net +19. 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 10,542–10,571 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 30
Measured (UTC)
Subscribers
Change
19 Sept 2026, 07:54
10,568
+3
16 Sept 2026, 21:41
10,565
+4
15 Sept 2026, 03:16
10,561
+10
13 Sept 2026, 12:58
10,551
-4
11 Sept 2026, 17:17
10,555
+1
9 Sept 2026, 00:59
10,554
+5
5 Sept 2026, 18:58
10,549
-4
3 Sept 2026, 21:18
10,553
+6
1 Sept 2026, 10:26
10,547
-1
31 Aug 2026, 07:12
10,548
-3
30 Aug 2026, 05:47
10,551
-4
29 Aug 2026, 05:13
10,555
-4
28 Aug 2026, 05:58
10,559
+1
27 Aug 2026, 06:56
10,558
+2
26 Aug 2026, 05:33
10,556
+2
25 Aug 2026, 03:13
10,554
-2
23 Aug 2026, 18:17
10,556
+1
22 Aug 2026, 01:19
10,555
+1
19 Aug 2026, 19:26
10,554
+1
18 Aug 2026, 18:03
10,553
first reading
Engagement
74 posts held, back to 27 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 38 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
11.9%
avg views ÷ 10,568 subscribers
Avg views / post
1,260
18 posts measured
Reaction rate
0.261%
reactions ÷ views · ER floor
Posts in window
18
of 74 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
Window
Rolling 30 days · latest post in window 28 August 2026
Posts held
74 (27 July 2026 – 28 August 2026)
Views total
22,607
Reactions total
59
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
29 Aug 2026, 13:24 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
209 reactions across 74 posts, in 7 distinct kinds. The most used accounts for 85.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
179
85.6%
🔥
15
7.18%
❤
9
4.31%
👏
2
0.957%
😈
2
0.957%
👎
1
0.478%
😢
1
0.478%
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 74 of the 74 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 209 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 74 most recent posts we hold, published 27 July 2026 to 28 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
1
across the posts below
Posts paid on
1
of 74 we hold a reading for · 1%
Most on one post
1
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @bdufstecru. 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 74 most recent posts we hold for this entry, published 27 July 2026 to 28 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.
Уязвимость программно-определяемой сети Cisco Catalyst SD-WAN (ранее Cisco SD-WAN) связана с хранением информации в открытом виде. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации
BDU:2026-12787
CVE-2026-20312
Использование рекомендаций производителя:
https://sec.cloudapps.cisco.com/security/center/c…
Уязвимость драйвера SQLite программного обеспечения для управления базами данных Adminer связана с неверным ограничением имени пути к каталогу. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, получить доступ на удаление произвольных файлов путем отправки специально сформированного POST-запроса
BDU:2026-12714
CVE-2026-34968
Использование рекомендаций производителя:
https://github.com/vrana…
Уязвимость функции validatePublicHttpUrl() инструмента визуализации и анализа данных Lightdash связана с недостаточной проверкой запросов на стороне сервера. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, получить несанкционированный доступ к защищаемой информации и вызвать отказ в обслуживании путем отправки специально сформированного POST-запроса
BDU:2026-12707
CVE-2026-72846
Использов…
Уязвимость функции punkt_pickle_load() пакета библиотек для символьной и статистической обработки естественного языка NLTK связана с недостатками механизма десериализации. Эксплуатация уязвимости может позволить нарушителю. действующему удаленно, выполнить произвольный код
BDU:2026-12702
CVE-2026-79657
Использование рекомендаций производителя:
https://github.com/nltk/nltk/releases#release-v3.10.3
Обновление БДУ
Обновлены сведения об уязвимостях программного обеспечения
Добавлена информация о 212 уязвимостях программного обеспечения
Внесены изменения в 32 записи об уязвимостях программного обеспечения
🔶БДУ ФСТЭК России в MAX
Уязвимость функции Lz4Decode файла NanaZip.Core/SevenZip/CPP/7zip/Archive/SquashfsHandler.cpp компонента SquashFS архиватора на базе 7-Zip NanaZip связана с чтением за пределами допустимого диапазона в памяти. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, раскрыть защищаемую информацию и вызвать отказ в обслуживании
BDU:2026-12653
CVE-2026-54616
Использование рекомендаций производителя:…
Уязвимость функции find_base_path() клиента файловой системы SSHFS связана с внедрением или модификацией аргументов. Эксплуатация уязвимости может позволить нарушителю выполнить произвольные команды
BDU:2026-12650
CVE-2026-48711
Использование рекомендаций производителя:
https://github.com/libfuse/sshfs/security/advisories/GHSA-mm85-q63v-4476
https://github.com/libfuse/sshfs/commit/29bb565ea6405e2dd5a0ea65fe64da117e…
Уязвимость модуля child_process программного средства преобразования json-данных JSONata связана с неверным управлением генерацией кода. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, выполнить произвольный код
BDU:2026-12628
CVE-2026-77415
Использование рекомендаций производителя:
https://github.com/jsonata-js/jsonata/releases/tag/v1.8.8
https://github.com/jsonata-js/jsonata/releases/ta…
Уязвимость консоли управления системы обнаружения и реагирования MaxPatrol EDR связана с ошибками разграничения доступа. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, вызвать отказ в обслуживании
BDU:2026-11660
PT-2026-22
Использование рекомендаций производителя:
https://ptsecurity.com/research/threatscape/PT-2026-22/
Обновление БДУ
Обновлены сведения об уязвимостях программного обеспечения
Добавлена информация о 449 уязвимостях программного обеспечения
Внесены изменения в 28 записей об уязвимостях программного обеспечения
🔶БДУ ФСТЭК России в MAX
👏2
Showing the 12 most recent of 74 posts we hold for @bdufstecru. 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.
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.
Утечки информации @dataleak · 119,401 Telegram ranks this channel #43 of 83 here — alongside 82 others — read 14 August 2026
SecAtor @true_secator · 41,700 Telegram ranks this channel #58 of 78 here — alongside 77 others — read 29 August 2026
Борьба с киберпреступностью | F6 @f6_cybersecurity · 22,323 Telegram ranks this channel #65 of 85 here — alongside 84 others — read 21 September 2026
SecurityLab.ru @SecLabNews · 84,459 Telegram ranks this channel #65 of 90 here — alongside 89 others — read 18 August 2026
Хакер — Xakep.RU @xakep_ru · 39,506 Telegram ranks this channel #66 of 83 here — alongside 82 others — read 30 August 2026
Волгоград | События | Подслушано @Volgograd_podslushal · 35,809 Telegram ranks this channel #67 of 73 here — alongside 72 others — read 2 September 2026
Privacy Advocates @prv_adv · 21,945 Telegram ranks this channel #68 of 98 here — alongside 97 others — read 22 September 2026
Positive Technologies @Positive_Technologies · 28,968 Telegram ranks this channel #69 of 87 here — alongside 86 others — read 9 September 2026
Пост Лукацкого @alukatsky · 37,862 Telegram ranks this channel #70 of 89 here — alongside 88 others — read 31 August 2026
Life-Hack - Хакер @haccking · 63,203 Telegram ranks this channel #77 of 85 here — alongside 84 others — read 21 August 2026
Вестник Киберполиции России @cyberpolice_rus · 83,750 Telegram ranks this channel #78 of 92 here — alongside 91 others — read 18 August 2026
Russian OSINT @Russian_OSINT · 47,701 Telegram ranks this channel #81 of 82 here — alongside 81 others — read 26 August 2026
Positive Hack Days Media @positivehackmedia · 30,694 Telegram ranks this channel #85 of 88 here — alongside 87 others — read 6 September 2026
IT и безопасность @tg_security · 26,613 Telegram ranks this channel #91 of 91 here — alongside 90 others — read 12 September 2026
Kaspersky @kasperskylab_ru · 28,858 Telegram ranks this channel #95 of 96 here — alongside 95 others — read 9 September 2026
РоскомнадZор @rkn_tg · 63,811 Telegram ranks this channel #95 of 96 here — alongside 95 others — read 21 August 2026
This channel appears in 16 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 19 September 2026 — this
entry's latest reading, not the date you are reading this.
“БДУ ФСТЭК России” (@bdufstecru), 10,568 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/bdufstecru.
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.