Telegram RegisterThe public register of Telegram
Telegram profile photo for AlexRedSec

Channel

AlexRedSec

@alexredsec

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

4,003subscribers

-1 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-1001424917406
TypeChannel
Username@alexredsec
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live10 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 10 September 2026
On Telegramt.me/alexredsec

Growth

3,9994,0104,004.56 August 2026 — 4,004 subscribers7 August 2026 — 4,003 subscribers10 August 2026 — 3,999 subscribers12 August 2026 — 4,001 subscribers16 August 2026 — 3,999 subscribers19 August 2026 — 4,001 subscribers23 August 2026 — 4,007 subscribers26 August 2026 — 4,010 subscribers29 August 2026 — 4,007 subscribers1 September 2026 — 4,008 subscribers5 September 2026 — 4,005 subscribers10 September 2026 — 4,003 subscribers4,0036 August 202610 September 2026
12 measurements spanning 35 days, net -1. 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 3,997–4,012 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Sept 2026, 18:394,003-2
5 Sept 2026, 10:374,005-3
1 Sept 2026, 20:164,008+1
29 Aug 2026, 15:344,007-3
26 Aug 2026, 19:024,010+3
23 Aug 2026, 08:144,007+6
19 Aug 2026, 10:384,001+2
16 Aug 2026, 05:473,999-2
12 Aug 2026, 23:234,001+2
10 Aug 2026, 08:203,999-4
7 Aug 2026, 03:424,003-1
6 Aug 2026, 08:214,004first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 14 posts for this entry, the most recent from 30 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
52s
Average length
26s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

158 reactions across 13 posts, in 5 distinct kinds. The most used accounts for 50.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍8050.6%
🔥5534.8%
138.23%
😁74.43%
😍31.90%

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

Measured over the 14 most recent posts we hold, published 20 May 2026 to 30 July 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
1
of 14 we hold a reading for · 7%
Most on one post
2
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @alexredsec. 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 14 most recent posts we hold for this entry, published 20 May 2026 to 30 July 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

30 Jul 2026, 05:01 UTC550 views5 reactionsread 8 August 2026
Photo

🥇 KPMG и TAG Infosphere недавно выпустили совместное руководство (скорее набор статей с рекомендациями) по пересмотру подходов к формированию бюджетов на кибербезопасность. Ключевые тезисы вынесены в иллюстрацию к посту, а ниже немного распишу общие (не отраслевые) рекомендации. Бюджетирование на принципах «Нулевого доверия» ➡️Ни одно средство защиты/услуга не должны автоматически пролонгироваться только потому, что

👍5

19 Jul 2026, 09:25 UTC960 views18 reactionsread 8 August 2026

✅ Здесь, кстати, исправил несколько ошибок и разместил веб-версию курса по адресу sa.alexredsec.ru. p.s. Еще подборку ресурсов на тему управления уязвимостями положил в репозиторий и продублировал по адресу vm.alexredsec.ru ❤️ #awareness #training #vm #bookmarks

🔥12👍42

9 Jul 2026, 05:45 UTC≈4,250 views9 reactionsread 8 August 2026
Photo

Pillar Security выпустили обновленную версию своего фреймворка SAIL, разработанного для обеспечения безопасности ИИ-систем на всех этапах их жизненного цикла. Для практического использования фреймворка SAIL авторы поделились также скиллом для ИИ-агентов, с помощью которого можно: ➡️Провести оценку по фреймворку, например, своих ИИ-агентов, чтобы выявить присущие риски (сформировать модель угроз). ➡️Сформировать план

👍72

26 Jun 2026, 06:31 UTC≈1,810 views6 reactionsread 8 August 2026
Photo

AI SOC Evaluation Framework – еще один вендор-независимый фреймворк для оценки применимости и эффективности AI SOC. На сайте проекта также есть онлайн-калькулятор. Ключевые компоненты ASEF: 🟠Shift Map (карта жизненного цикла инцидента) Позволяет оценить применимость ИИ на каждом этапе обработки данных и угроз: 🟠Evaluator Scale (шкала автономности) – каждая функция оценивается по уровню автоматизации от 0 (ручной реж

👍6

19 Jun 2026, 05:25 UTC≈11,800 views38 reactionsread 8 August 2026
Photo

Дошли руки до русификации интерактивного курса по кибербезопасности с открытым исходным кодом, про который писал в прошлом году: помимо банального перевода, адаптировали с коллегами под отечественные реалии (152-ФЗ) модуль по защите персональных данных, а в модуле про безопасное программирование обновили описание OWASP TOP 10 под версию 2025 года. Русифицированную версию положил в репозиторий на гитхабе. В LMS-платф

🔥266👍6

13 Jun 2026, 08:32 UTC≈1,660 views6 reactionsread 8 August 2026
Video

Наконец-то полезный ресурс – APT & Threat Name Generator! Теперь исследователям не придется ломать голову над названием для новой группировки или очередного вредоноса🤤 p.s. Сгенерированное имя можно даже застолбить у автора ресурса, чтобы он исключил его генератора👍 #humor

😁6

11 Jun 2026, 05:02 UTC≈2,110 views12 reactionsread 8 August 2026
Photo

⚡️Агентство CISA выпустило директиву для гос.учреждений США (а для всех остальных – хороший гайд🙂) о приоритизации устранения уязвимостей на основе риск-ориентированного подхода. Критерии оценки рисков: 1️⃣Доступность системы из сети Интернет. 2️⃣Наличие уязвимости в каталоге KEV CISA. 3️⃣Возможность автоматизации процесса эксплуатации уязвимости (шаги 1-4 цепочки атаки, kill chain). 4️⃣Уровень воздействия на систем

👍12

9 Jun 2026, 05:24 UTC≈1,450 views11 reactionsread 8 August 2026
Photo

🔤🔤🔤🔤 🔤5️⃣ Через неделю выйдет очередная версия EPSS (пятая), но уже сейчас есть информация о некоторых изменениях, сравнение с действующей четвертой версией, да и фиды ежедневные уже как пару недель можно скачать. Разработчики EPSS ожидаемо заявляют, что: "Модель EPSS V5 представляет собой значительное обновление системы прогнозирования эксплуатации уязвимостей" Из более "осязаемых" изменений: 🔗Улучшили поиск экспло

👍83

7 Jun 2026, 07:05 UTC≈1,660 views11 reactionsread 8 August 2026
Video

AIRQ Framework – очень классное исследование и подход оценки безопасности использования ИИ-агентов в корпоративной среде: в рамках работы изучили сотню агентов, которые предварительно разбили на десять классов (по специфике работы), на предмет выявления рисков, связанных с предоставлением доступа к данным и выполнению критичных операций. В итоге все агенты разнесли на четыре профиля риска, основываясь на определенной

👍6🔥5

3 Jun 2026, 04:59 UTC≈1,600 views6 reactionsread 8 August 2026
Photo

Небольшой портал со статистикой и аналитикой по уязвимостям, обнаруженным с помощью автономных ИИ-агентов. Ключевые выводы: ➡️В 2026 году наблюдается резкое сокращение (–68%) количества обнаруженных агентами классических веб-уязвимостей, таких как XSS, SQLi и CSRF, по сравнению с 2025 годом. ➡️Уязвимости, найденные ИИ, чаще (по сравнению с остальными) получают высокие или критические оценки по CVSS, однако, вероятно

👍6

Showing the 12 most recent of 14 posts we hold for @alexredsec. 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 3 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 · 37,763
Telegram ranks this channel #20 of 89 here — alongside 88 others — read 31 August 2026
SecAtor
@true_secator · 41,636
Telegram ranks this channel #29 of 78 here — alongside 77 others — read 29 August 2026
Пакет Безопасности
@package_security · 33,138
Telegram ranks this channel #46 of 82 here — alongside 81 others — read 4 September 2026
Codeby
@codeby_sec · 36,955
Telegram ranks this channel #53 of 76 here — alongside 75 others — read 1 September 2026
Russian OSINT
@Russian_OSINT · 47,581
Telegram ranks this channel #74 of 82 here — alongside 81 others — read 26 August 2026
Positive Technologies
@Positive_Technologies · 28,874
Telegram ranks this channel #79 of 87 here — alongside 86 others — read 9 September 2026
Positive Hack Days Media
@positivehackmedia · 30,805
Telegram ranks this channel #79 of 88 here — alongside 87 others — read 6 September 2026

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

“AlexRedSec” (@alexredsec), 4,003 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/alexredsec.

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.