Telegram RegisterThe public register of Telegram
Telegram profile photo for Управление Уязвимостями и прочее

Channel

Управление Уязвимостями и прочее

@avleonovrus

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

12,621subscribers

+826 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-1001531395489
TypeChannel
Username@avleonovrus
DescriptionАнализ защищённости, безопасное конфигурирование ИТ-систем, автоматизация связанных ИБ-процессов. Рег. номер РКН: 6841152413 Другие каналы: @avleonovlive, @avleonovcom Личка: @leonov_av
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 November 2026
Measurements held56
Confirmed unchanged1 time, most recently 6 November 2026
On Telegramt.me/avleonovrus

Topic

Technology — 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 85% 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

11,78212,62112,201.56 August 2026 — 11,795 subscribers7 August 2026 — 11,800 subscribers8 August 2026 — 11,797 subscribers9 August 2026 — 11,793 subscribers10 August 2026 — 11,784 subscribers11 August 2026 — 11,782 subscribers12 August 2026 — 11,784 subscribers13 August 2026 — 11,790 subscribers14 August 2026 — 11,791 subscribers16 August 2026 — 11,798 subscribers17 August 2026 — 11,805 subscribers19 August 2026 — 11,802 subscribers20 August 2026 — 11,804 subscribers21 August 2026 — 11,798 subscribers23 August 2026 — 11,806 subscribers24 August 2026 — 11,799 subscribers25 August 2026 — 11,796 subscribers26 August 2026 — 11,802 subscribers27 August 2026 — 11,809 subscribers28 August 2026 — 11,844 subscribers29 August 2026 — 11,849 subscribers31 August 2026 — 11,883 subscribers1 September 2026 — 11,900 subscribers2 September 2026 — 11,904 subscribers4 September 2026 — 11,918 subscribers7 September 2026 — 11,996 subscribers10 September 2026 — 12,028 subscribers12 September 2026 — 12,091 subscribers14 September 2026 — 12,115 subscribers15 September 2026 — 12,125 subscribers17 September 2026 — 12,130 subscribers26 September 2026 — 12,122 subscribers4 October 2026 — 12,148 subscribers9 October 2026 — 12,160 subscribers13 October 2026 — 12,363 subscribers14 October 2026 — 12,360 subscribers15 October 2026 — 12,367 subscribers16 October 2026 — 12,379 subscribers18 October 2026 — 12,373 subscribers19 October 2026 — 12,375 subscribers20 October 2026 — 12,387 subscribers22 October 2026 — 12,402 subscribers23 October 2026 — 12,463 subscribers24 October 2026 — 12,484 subscribers25 October 2026 — 12,493 subscribers26 October 2026 — 12,526 subscribers27 October 2026 — 12,538 subscribers28 October 2026 — 12,547 subscribers29 October 2026 — 12,584 subscribers30 October 2026 — 12,601 subscribers31 October 2026 — 12,599 subscribers1 November 2026 — 12,600 subscribers2 November 2026 — 12,607 subscribers3 November 2026 — 12,613 subscribers4 November 2026 — 12,614 subscribers6 November 2026 — 12,621 subscribers6 August 20266 November 2026
56 measurements spanning 92 days, net +826. 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 11,656–12,747 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, 10:1812,621+7
4 Nov 2026, 04:1912,614+1
3 Nov 2026, 05:1612,613+6
2 Nov 2026, 06:5012,607+7
1 Nov 2026, 07:3912,600+1
31 Oct 2026, 04:2712,599-2
30 Oct 2026, 04:4712,601+17
29 Oct 2026, 03:5112,584+37
28 Oct 2026, 02:3012,547+9
27 Oct 2026, 01:5712,538+12
26 Oct 2026, 02:4512,526+33
25 Oct 2026, 04:1812,493+9
24 Oct 2026, 01:4012,484+21
23 Oct 2026, 01:4512,463+61
22 Oct 2026, 00:4512,402+15
20 Oct 2026, 17:1612,387+12
19 Oct 2026, 13:2912,375+2
18 Oct 2026, 10:3712,373-6
16 Oct 2026, 14:4612,379+12
15 Oct 2026, 18:1812,367first reading

Engagement

64 posts held, back to 28 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 55 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
12.1%
avg views ÷ 12,621 subscribers
Avg views / post
1,520
25 posts measured
Reaction rate
0.586%
reactions ÷ views · ER floor
Posts in window
25
of 64 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 6 November 2026
Posts held64 (28 July 2026 – 6 November 2026)
Views total38,045
Reactions total223
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Nov 2026, 19:16 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.

What this channel posts

Photos
≈2,650
Videos
≈13
Links
≈1,920

Lifetime counters from Telegram’s own channel header, read 6 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

528 reactions across 64 posts, in 6 distinct kinds. The most used accounts for 34.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤18234.5%
👍18234.5%
⚡7213.6%
👏468.71%
💯438.14%
🙏30.568%

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

Measured over the 64 most recent posts we hold, published 28 July 2026 to 6 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.13%
2 of 64 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
1,290
over 2 measured posts
Median views · rest
1,210
over 62 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.

Measured over the 64 most recent posts we hold, published 28 July 2026 to 6 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: 10 of 25 posts held from the last 30 days (40.0%) 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).

6 Nov 2026, 11:38 UTC608 views4 reactionsread 6 November 2026
Photo

Почему инцидентов с эксплуатацией PHP2Shell так мало? С самого начала PHP2Shell сравнивали с громкой уязвимостью Log4Shell (CVE-2021-44228). Однако механизмы эксплуатации этих уязвимостей существенно различаются. В случае Log4Shell злоумышленникам достаточно было отправить короткий фрагмент текста уязвимому приложению. Если приложение записывало этот текст в журнал, атака срабатывала. Один и тот же текст работал прак…

❤2👍1💯1

5 Nov 2026, 16:03 UTC851 views8 reactionsread 6 November 2026
Photo

Что там слышно по инцидентам, связанным с эксплуатацией PHP2Shell, спустя две недели? Когда 21 октября разработчики PHP готовились к релизу версий PHP с исправлением PHP2Shell (CVE-2026-109618, CVE-2026-109619), эксперты прогнозировали, что буквально через 15 минут после публикации обновления начнутся массовые атаки на уязвимые серверы. Эксперты Amazon даже сообщали о попытках эксплуатации за четыре дня до выхода пат…

⚡4❤3💯1

4 Nov 2026, 18:02 UTC911 views10 reactionsread 6 November 2026
Photo

С Днём народного единства! Единство народов - фундамент устойчивости и суверенитета нашей страны, а многообразие - наше главное конкурентное преимущество. Пусть уязвимости в наших взаимоотношениях детектируются и своевременно устраняются. Пусть внутренние и внешние угрозы согласию успешно нейтрализуются. Пусть сплочённость, взаимопомощь и готовность действовать сообща остаются основой нашей безопасности. Желаю креп…

❤7👏2💯1

4 Nov 2026, 08:32 UTC≈1,090 views5 reactionsread 6 November 2026
Photo

Я в прошлом посте про взлом Binance предполагал, что у них в инфраструктуре колхоз и адище, а сотрудники творят безответственную дичь, но реальность оказалась даже веселее. 🙂 🔻 В сентябре 2026 года через легитимную платформу для поиска работы с инженером-программистом B связался человек, представившийся директором проекта. В профиле инженера был указан опыт работы в Binance, что, вероятно, привлекло внимание злоумыш…

❤2👍2💯1

3 Nov 2026, 17:58 UTC955 views11 reactionsread 6 November 2026
Photo

Видеозапись моего выступления на Positive Security Day 15 октября под названием "Отделить зёрна от плевел: подходы к автоматизированной оценке опасности уязвимостей". В выступлении я рассказал о существующих методах оценки и приоритизации уязвимостей (CVSS, методике ФСТЭК, KEV-каталогах, EPSS, SSVC и Tenable VPR), рассмотрел трендовые уязвимости 2026 года и представил методику PVSS от Positive Technologies, применяем…

❤5👍4👏2

2 Nov 2026, 15:49 UTC≈1,140 views13 reactionsread 6 November 2026
Photo

Попался на глаза мем "объясните Управление Уязвимостями своими словами" - перевёл его в виде комикса. В целом, типичный процесс Управления Уязвимостями в организации (с точки зрения VM-щика, естественно 🙂) - это разгребание постоянных косяков: 🔻 в работе инструментов детектирования уязвимостей (в принципе неподдерживаемое ПО и типы активов, фолсы, баги); 🔻 в качестве информации об уязвимостях (вроде эксплуатируется…

👍5💯5❤3

2 Nov 2026, 11:36 UTC≈1,140 views7 reactionsread 6 November 2026
Photo

По поводу ночных ложных оповещений о ракетно-ядерном нападении через мобильные приложения и соответствующие системы в России и в сопредельном вражеском государстве. Ничего удивительного в этом нет. Любые IT-системы, любые приложения содержат уязвимости, и их можно взломать. 💯 Если для государственного заказчика рассылка такого рода массовых ложных уведомлений является недопустимым событием, значит, вероятность его н…

👍4💯2❤1

2 Nov 2026, 08:47 UTC≈1,170 views5 reactionsread 6 November 2026
Photo

Про уязвимость Denial of Service - Android "SMS of Death" (CVE-2026-58882). Уязвимость позволяет удалённо нарушить работу мобильной связи на Android-смартфоне с помощью специально сформированного SMS-сообщения. Для эксплуатации не требуется взаимодействие с пользователем (zero-click). Для атаки используется WAP Push - специальный тип бинарного SMS, предназначенный для автоматической передачи служебной информации или …

❤3⚡1👍1

30 Oct 2026, 18:03 UTC≈1,280 views4 reactionsread 6 November 2026
Photo

Октябрьский Linux Patch Wednesday. Всего 4946 уязвимостей. Для сравнения, в сентябре было 2653. Рост на 86%! В Linux Kernel на этот раз 1954 уязвимости, в Chromium - 814. Вместе они составляют 56% от общего количества уязвимостей. Для шести уязвимостей есть признаки эксплуатации в реальных атаках: 🔻 RCE - PHP "PHP2Shell" (CVE-2026-109618, CVE-2026-109619). PHP - популярный язык программирования, используемый для раз…

👏2⚡1❤1

30 Oct 2026, 11:50 UTC≈1,090 views6 reactionsread 6 November 2026
Photo

StopPhish опубликовали исследование о тенденциях в развитии мошеннических схем (с моим комментарием). В исследование вошли 5 083 публикации, для которых удалось найти первоисточники. Период исследования - с 1 января 2022 года по 30 июня 2026 года. 📈 Наблюдается устойчивый рост количества публикаций (публ.) и разновидностей мошеннических схем (разн.) 2022 год - 389 публ., 135 разн. 2023 год - 718 публ., 254 разн. 20…

❤3👍2⚡1

30 Oct 2026, 09:35 UTC≈1,150 views10 reactionsread 6 November 2026
Photo

На фоне сообщений о взломе Binance появился повод поделиться своим мнением о криптовалютах. 🔹 29 октября Binance - самая большая криптовалютная биржа в мире по объёму торгов - начала расследование инцидента безопасности, который аналитики называют крупнейшим в истории криптовалютной индустрии. Биржа оценила общий объём затронутых средств примерно в $6,3 млрд, а аналитики Chainalysis оценили объём похищенных средств …

💯5👍3❤2

28 Oct 2026, 10:14 UTC≈1,420 views4 reactionsread 6 November 2026
Photo

Октябрьский "В тренде VM": уязвимости Windows и Check Point. Представляю традиционную ежемесячную подборку трендовых уязвимостей по версии Positive Technologies. В прошлом сентябрьском выпуске было шесть уязвимостей. В этот раз их всего две. 🗞 Пост на Хабре 🗒 Дайджест на сайте PT 🔻 EoP - Windows ALPC (CVE-2026-85880). Активно эксплуатируемая уязвимость в механизме межпроцессного взаимодействия Windows, позволяющая …

❤2⚡1👍1

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

Posts recorded as deleted after publishing

We recorded 1 post on @avleonovrus as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
31 August 2026
Most recent seen missing
31 August 2026
Median time before seen missing
4 days
Seen missing in the last 30 days
0

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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

Пост Лукацкого
@alukatsky · 38,417
Telegram ranks this channel #3 of 89 here — alongside 88 others — read 31 August 2026
SecAtor
@true_secator · 42,179
Telegram ranks this channel #6 of 78 here — alongside 77 others — read 29 August 2026
Positive Technologies
@Positive_Technologies · 29,423
Telegram ranks this channel #10 of 87 here — alongside 86 others — read 9 September 2026
Хакер — Xakep.RU
@xakep_ru · 40,262
Telegram ranks this channel #11 of 83 here — alongside 82 others — read 30 August 2026
SecurityLab.ru
@SecLabNews · 86,455
Telegram ranks this channel #14 of 90 here — alongside 89 others — read 18 August 2026
S.E.Reborn
@S_E_Reborn · 22,461
Telegram ranks this channel #20 of 66 here — alongside 65 others — read 20 September 2026
Positive Hack Days Media
@positivehackmedia · 30,114
Telegram ranks this channel #21 of 88 here — alongside 87 others — read 6 September 2026
S.E.Book
@S_E_Book · 23,100
Telegram ranks this channel #22 of 64 here — alongside 63 others — read 19 September 2026
Life-Hack - Хакер
@haccking · 63,053
Telegram ranks this channel #22 of 85 here — alongside 84 others — read 21 August 2026
Codeby
@codeby_sec · 37,057
Telegram ranks this channel #23 of 76 here — alongside 75 others — read 1 September 2026
Social Engineering
@Social_engineering · 124,752
Telegram ranks this channel #34 of 82 here — alongside 81 others — read 13 August 2026
Утечки информации
@dataleak · 117,908
Telegram ranks this channel #36 of 83 here — alongside 82 others — read 14 August 2026
Offensive Xwitter
@OffensiveTwitter · 21,289
Telegram ranks this channel #37 of 53 here — alongside 52 others — read 25 September 2026
Листок бюрократической защиты информации
@bureaucraticsecurity · 19,140
Telegram ranks this channel #38 of 98 here — alongside 97 others — read 4 October 2026
Белый хакер
@bezopasno_soft · 29,631
Telegram ranks this channel #39 of 78 here — alongside 77 others — read 8 September 2026
no system is safe // cybersec
@nsis_cybersec · 21,206
Telegram ranks this channel #41 of 71 here — alongside 70 others — read 23 September 2026
Информация опасносте
@alexmakus · 18,755
Telegram ranks this channel #45 of 85 here — alongside 84 others — read 5 October 2026
КиберДед official
@deedcoin_club · 22,979
Telegram ranks this channel #47 of 84 here — alongside 83 others — read 25 September 2026
Борьба с киберпреступностью | F6
@f6_cybersecurity · 22,367
Telegram ranks this channel #53 of 85 here — alongside 84 others — read 21 September 2026
Russian OSINT
@Russian_OSINT · 48,467
Telegram ranks this channel #54 of 82 here — alongside 81 others — read 26 August 2026
infosecurity
@tg_infosec · 26,860
Telegram ranks this channel #55 of 74 here — alongside 73 others — read 11 September 2026
Лаборатория хакера
@lab_hack · 25,457
Telegram ranks this channel #56 of 71 here — alongside 70 others — read 14 September 2026
Интернет-Розыск
@irozysk · 45,746
Telegram ranks this channel #58 of 79 here — alongside 78 others — read 27 August 2026
IT и безопасность
@tg_security · 26,847
Telegram ranks this channel #59 of 91 here — alongside 90 others — read 12 September 2026

This channel appears in 34 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. 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.

“Управление Уязвимостями и прочее” (@avleonovrus), 12,621 subscribers as measured 6 November 2026. Telegram Register, tgregister.com/channel/avleonovrus.

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.