Telegram RegisterThe public register of Telegram
Telegram profile photo for БДУ ФСТЭК России

Channel

БДУ ФСТЭК России

@bdufstecru

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

10,635subscribers

+86 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-1001623043171
TypeChannel
Username@bdufstecru
Created7 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live6 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/bdufstecru

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 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 the other topics.

Growth

10,54510,63510,5906 August 2026 — 10,549 subscribers6 August 2026 — 10,549 subscribers7 August 2026 — 10,546 subscribers8 August 2026 — 10,547 subscribers10 August 2026 — 10,545 subscribers11 August 2026 — 10,551 subscribers12 August 2026 — 10,550 subscribers13 August 2026 — 10,555 subscribers16 August 2026 — 10,552 subscribers17 August 2026 — 10,550 subscribers18 August 2026 — 10,553 subscribers19 August 2026 — 10,554 subscribers22 August 2026 — 10,555 subscribers23 August 2026 — 10,556 subscribers25 August 2026 — 10,554 subscribers26 August 2026 — 10,556 subscribers27 August 2026 — 10,558 subscribers28 August 2026 — 10,559 subscribers29 August 2026 — 10,555 subscribers30 August 2026 — 10,551 subscribers31 August 2026 — 10,548 subscribers1 September 2026 — 10,547 subscribers3 September 2026 — 10,553 subscribers5 September 2026 — 10,549 subscribers9 September 2026 — 10,554 subscribers11 September 2026 — 10,555 subscribers13 September 2026 — 10,551 subscribers15 September 2026 — 10,561 subscribers16 September 2026 — 10,565 subscribers19 September 2026 — 10,568 subscribers25 September 2026 — 10,589 subscribers4 October 2026 — 10,600 subscribers8 October 2026 — 10,595 subscribers13 October 2026 — 10,599 subscribers14 October 2026 — 10,603 subscribers15 October 2026 — 10,602 subscribers16 October 2026 — 10,601 subscribers17 October 2026 — 10,604 subscribers18 October 2026 — 10,605 subscribers19 October 2026 — 10,602 subscribers20 October 2026 — 10,603 subscribers21 October 2026 — 10,604 subscribers22 October 2026 — 10,609 subscribers23 October 2026 — 10,624 subscribers24 October 2026 — 10,623 subscribers25 October 2026 — 10,621 subscribers27 October 2026 — 10,623 subscribers28 October 2026 — 10,626 subscribers29 October 2026 — 10,631 subscribers30 October 2026 — 10,629 subscribers31 October 2026 — 10,628 subscribers1 November 2026 — 10,629 subscribers2 November 2026 — 10,630 subscribers3 November 2026 — 10,631 subscribers5 November 2026 — 10,630 subscribers6 November 2026 — 10,635 subscribers6 August 20266 November 2026
56 measurements spanning 92 days, net +86. 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,532–10,649 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 56
Measured (UTC)SubscribersChange
6 Nov 2026, 15:3610,635+5
5 Nov 2026, 11:4710,630-1
3 Nov 2026, 11:1910,631+1
2 Nov 2026, 14:3410,630+1
1 Nov 2026, 14:5610,629+1
31 Oct 2026, 12:5010,628-1
30 Oct 2026, 16:0610,629-2
29 Oct 2026, 18:3910,631+5
28 Oct 2026, 18:2010,626+3
27 Oct 2026, 18:1010,623+2
25 Oct 2026, 22:0610,621-2
24 Oct 2026, 20:4910,623-1
23 Oct 2026, 18:0010,624+15
22 Oct 2026, 15:3910,609+5
21 Oct 2026, 11:3710,604+1
20 Oct 2026, 10:1910,603+1
19 Oct 2026, 11:1010,602-3
18 Oct 2026, 08:5010,605+1
17 Oct 2026, 11:5410,604+3
16 Oct 2026, 15:1110,601first reading

Engagement

97 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 45 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
16.1%
avg views ÷ 10,635 subscribers
Avg views / post
1,710
23 posts measured
Reaction rate
0.206%
reactions ÷ views · ER floor
Posts in window
23
of 97 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 3 November 2026
Posts held97 (27 July 2026 – 3 November 2026)
Views total39,360
Reactions total81
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 08:34 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

290 reactions across 97 posts, in 9 distinct kinds. The most used accounts for 85.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍24985.9%
🔥175.86%
❤124.14%
😱51.72%
👏20.69%
😈20.69%
👎10.345%
💅10.345%
😢10.345%

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

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

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 97 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 97 most recent posts we hold for this entry, published 27 July 2026 to 3 November 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

Telegram’s own ‘edited’ marker: 4 of 23 posts held from the last 30 days (17.4%) 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).

3 Nov 2026, 12:18 UTC≈1,530 views7 reactionsread 6 November 2026

Уязвимость компонента AuthenticatorActivity облачного программного обеспечения для создания и использования хранилища данных Nextcloud связана с неправильным экспортом компонентов приложений. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, обойти существующие механизмы безопасности BDU:2026-18076 CVE-2026-107059 Компенсирующие меры: - использование средств межсетевого экранирования для ог…

👍6💅1

3 Nov 2026, 12:17 UTC≈1,310 views3 reactionsread 6 November 2026

Уязвимость средства виртуализации VMmanager 6 связанная с непоследовательной интерпретацией HTTP-запросов. Эксплуатация уязвимости может позволить нарушителю, действующему удалённо, выполнить подмену и передачу HTTP-запросов в обход механизмов безопасности BDU:2026-17394 Обновление программного обеспечения, применение оперативного обновления «Vmmanager 6» 2026.09.1-4 Regular, 6.2.2026.05.2-2, предоставляемого в лич…

👍3

3 Nov 2026, 12:16 UTC≈1,270 views2 reactionsread 6 November 2026

Обновление БДУ Обновлены сведения об уязвимостях программного обеспечения Добавлена информация о 100 уязвимостях программного обеспечения Внесены изменения в 354 записи об уязвимостях программного обеспечения 🔶БДУ ФСТЭК России в MAX

👍2

2 Nov 2026, 14:16 UTC≈1,480 views3 reactionsread 6 November 2026

Уязвимость функции AWS2S3Utils.determineKey() компонента camel-aws2-s3 java-фреймворка Apache Camel связана с непринятием мер по нейтрализации специальных элементов, используемых в операторе языка выражений. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, выполнить произвольный код BDU:2026-17946 CVE-2026-95664 Использование рекомендаций производителя: https://camel.apache.org/security/CV…

👍3

2 Nov 2026, 14:15 UTC≈1,450 views3 reactionsread 6 November 2026

Уязвимость компонента SMTP платформы для управления проектами OpenProject связана с недостаточной проверкой запросов на стороне сервера. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, осуществить SSRF-атаку BDU:2026-17944 CVE-2026-31974 Использование рекомендаций производителя: https://www.openproject.org/docs/release-notes/17-2-0/

👍3

2 Nov 2026, 14:15 UTC≈1,440 views3 reactionsread 6 November 2026

Уязвимость функции evalAction() компонента Remotedev Server библиотеки Redux DevTools связана с неверной нейтрализация особых элементов в выходных данных. Эксплуатация уязвимости может позволить нарушителю получить несанкционированный доступ к защищаемой информации и выполнить произвольный код BDU:2026-17941 CVE-2026-117526 Компенсирующие меры: - ограничение возможности использования библиотеки; - минимизация польз…

👍3

2 Nov 2026, 14:13 UTC≈1,390 views2 reactionsread 6 November 2026

Обновление БДУ Обновлены сведения об уязвимостях программного обеспечения Добавлена информация о 136 уязвимостях программного обеспечения 🔶БДУ ФСТЭК России в MAX

👍2

30 Oct 2026, 15:05 UTC≈1,820 views3 reactionsread 6 November 2026

Уязвимость компонента MozJS системы управления базами данных MongoDB связана с недостатками процедуры авторизации. Эксплуатация уязвимости может позволить нарушителю, действующему удалённо, получить несанкционированный доступ к защищаемой информации BDU:2026-17911 CVE-2026-13078 Использование рекомендаций производителя: https://jira.mongodb.org/browse/SERVER-128832

👍3

30 Oct 2026, 15:02 UTC≈1,800 views7 reactionsread 6 November 2026

Уязвимость гипервизора VMware ESX связана с ошибками в настройках безопасности. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, выполнить произвольный код BDU:2026-17873 CVE-2026-41709 Использование рекомендаций производителя: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017

😱5👍2

30 Oct 2026, 14:59 UTC≈1,740 views3 reactionsread 6 November 2026

Уязвимость пакета реализации набора стандартов JWE, JWS, JWT go-jose для языка программирования Go связана с распределением ресурсов без ограничений и регулирования. Эксплуатация уязвимости может позволить нарушителю, действующему удаленно, вызвать отказ в обслуживании BDU:2026-17870 CVE-2026-116587 Использование рекомендаций: https://github.com/go-jose/go-jose/commit/a0111f82742fa92bceec9ede40845e73319e6230 https:…

👍3

30 Oct 2026, 14:56 UTC≈1,610 views2 reactionsread 6 November 2026

Обновление БДУ Обновлены сведения об уязвимостях программного обеспечения Добавлена информация о 63 уязвимостях программного обеспечения Внесены изменения в 24 записи об уязвимостях программного обеспечения 🔶БДУ ФСТЭК России в MAX

👍2

30 Oct 2026, 14:54 UTC≈1,520 views2 reactionsread 6 November 2026

Опубликованы новые результаты тестирования обновлений ПО 🔶БДУ ФСТЭК России в MAX

🔥2

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

Листок бюрократической защиты информации
@bureaucraticsecurity · 19,140
Telegram ranks this channel #35 of 98 here — alongside 97 others — read 4 October 2026
Утечки информации
@dataleak · 117,908
Telegram ranks this channel #43 of 83 here — alongside 82 others — read 14 August 2026
Об ЭП и УЦ
@ep_uc · 21,399
Telegram ranks this channel #54 of 97 here — alongside 96 others — read 24 September 2026
SecAtor
@true_secator · 42,179
Telegram ranks this channel #58 of 78 here — alongside 77 others — read 29 August 2026
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,367
Telegram ranks this channel #65 of 85 here — alongside 84 others — read 21 September 2026
SecurityLab.ru
@SecLabNews · 86,494
Telegram ranks this channel #65 of 90 here — alongside 89 others — read 18 August 2026
Хакер — Xakep.RU
@xakep_ru · 40,262
Telegram ranks this channel #66 of 83 here — alongside 82 others — read 30 August 2026
Волгоград | События | Подслушано
@Volgograd_podslushal · 35,769
Telegram ranks this channel #67 of 73 here — alongside 72 others — read 2 September 2026
Privacy Advocates
@prv_adv · 21,859
Telegram ranks this channel #68 of 98 here — alongside 97 others — read 22 September 2026
Positive Technologies
@Positive_Technologies · 29,423
Telegram ranks this channel #69 of 87 here — alongside 86 others — read 9 September 2026
Пост Лукацкого
@alukatsky · 38,417
Telegram ranks this channel #70 of 89 here — alongside 88 others — read 31 August 2026
Life-Hack - Хакер
@haccking · 63,053
Telegram ranks this channel #77 of 85 here — alongside 84 others — read 21 August 2026
Вестник Киберполиции России
@cyberpolice_rus · 82,871
Telegram ranks this channel #78 of 92 here — alongside 91 others — read 18 August 2026
Russian OSINT
@Russian_OSINT · 48,467
Telegram ranks this channel #81 of 82 here — alongside 81 others — read 26 August 2026
Positive Hack Days Media
@positivehackmedia · 30,114
Telegram ranks this channel #85 of 88 here — alongside 87 others — read 6 September 2026
IT и безопасность
@tg_security · 26,847
Telegram ranks this channel #91 of 91 here — alongside 90 others — read 12 September 2026
Kaspersky
@kasperskylab_ru · 28,901
Telegram ranks this channel #95 of 96 here — alongside 95 others — read 9 September 2026
РоскомнадZор
@rkn_tg · 62,100
Telegram ranks this channel #95 of 96 here — alongside 95 others — read 21 August 2026

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

“БДУ ФСТЭК России” (@bdufstecru), 10,635 subscribers as measured 6 November 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.