Telegram RegisterThe public register of Telegram
Telegram profile photo for 0day Alert

Channel

0day Alert

@ZerodayAlert

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

10,948subscribers

+25 since we began measuring on 5 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001921217593
TypeChannel
Username@ZerodayAlert
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 17 September 2026
On Telegramt.me/ZerodayAlert

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 98% 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

10,78110,94910,8655 August 2026 — 10,923 subscribers6 August 2026 — 10,923 subscribers6 August 2026 — 10,922 subscribers7 August 2026 — 10,920 subscribers8 August 2026 — 10,915 subscribers9 August 2026 — 10,914 subscribers10 August 2026 — 10,900 subscribers11 August 2026 — 10,892 subscribers12 August 2026 — 10,889 subscribers13 August 2026 — 10,885 subscribers14 August 2026 — 10,899 subscribers16 August 2026 — 10,889 subscribers17 August 2026 — 10,886 subscribers18 August 2026 — 10,871 subscribers19 August 2026 — 10,878 subscribers20 August 2026 — 10,876 subscribers21 August 2026 — 10,874 subscribers23 August 2026 — 10,872 subscribers24 August 2026 — 10,861 subscribers25 August 2026 — 10,826 subscribers26 August 2026 — 10,804 subscribers28 August 2026 — 10,783 subscribers28 August 2026 — 10,782 subscribers31 August 2026 — 10,781 subscribers1 September 2026 — 10,805 subscribers1 September 2026 — 10,813 subscribers3 September 2026 — 10,820 subscribers4 September 2026 — 10,833 subscribers7 September 2026 — 10,934 subscribers10 September 2026 — 10,949 subscribers12 September 2026 — 10,946 subscribers14 September 2026 — 10,943 subscribers15 September 2026 — 10,949 subscribers17 September 2026 — 10,948 subscribers10,9485 August 202617 September 2026
34 measurements spanning 43 days, net +25. 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,756–10,974 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
17 Sept 2026, 20:5510,948-1
15 Sept 2026, 18:5710,949+6
14 Sept 2026, 04:1610,943-3
12 Sept 2026, 11:1910,946-3
10 Sept 2026, 09:1910,949+15
7 Sept 2026, 05:4210,934+101
4 Sept 2026, 13:3810,833+13
3 Sept 2026, 00:1410,820+7
1 Sept 2026, 22:2710,813+8
1 Sept 2026, 01:3410,805+24
31 Aug 2026, 00:1310,781-1
28 Aug 2026, 22:4610,782-1
28 Aug 2026, 00:2310,783-21
26 Aug 2026, 23:0610,804-22
25 Aug 2026, 21:3310,826-35
24 Aug 2026, 22:0710,861-11
23 Aug 2026, 11:3610,872-2
21 Aug 2026, 20:1410,874-2
20 Aug 2026, 17:4410,876-2
19 Aug 2026, 17:2810,878first reading

Engagement

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

ERR · 30 days
23.1%
avg views ÷ 10,948 subscribers
Avg views / post
2,530
13 posts measured
Reaction rate
0.255%
reactions ÷ views · ER floor
Posts in window
13
of 44 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 1 September 2026
Posts held44 (15 July 20261 September 2026)
Views total32,890
Reactions total84
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken1 Sept 2026, 20:10 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

281 reactions across 38 posts, in 29 distinct kinds. The most used accounts for 13.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍3813.5%
3612.8%
🤡3512.5%
🔥289.96%
👏207.12%
😁196.76%
😱176.05%
👀144.98%
🤯124.27%
💩103.56%
🤬72.49%
❤‍🔥51.78%
💯51.78%
😨51.78%
🆒41.42%
🌚31.07%
🙏31.07%
🥰31.07%
20.712%
👎20.712%
9 further kinds134.63%

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 42 of the 44 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 44 most recent posts we hold, published 15 July 2026 to 1 September 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 44 we hold a reading for · 2%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @ZerodayAlert. 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 44 most recent posts we hold for this entry, published 15 July 2026 to 1 September 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.

Advertising

Ad load
4.55%
2 of 44 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
1,420
over 2 measured posts
Median views · rest
3,040
over 42 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.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2SDnjbz6uhM13 August 20263 August 2026
CQH36pWzJqE1dR7Fsj4EY9f59dnFN6DWRnLFUPMV4vYWKK127 August 202627 August 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 44 most recent posts we hold, published 15 July 2026 to 1 September 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

1 Sept 2026, 07:11 UTC≈1,150 views5 reactionsread 1 September 2026
Photo

KindaRails2Shell: новая уязвимость затронула механизм загрузки файлов Ruby on Rails Уязвимость получила 9,5 балла из 10 по шкале CVSS и позволяет атаковать сервер без учётной записи. Проблема затрагивает Active Storage — встроенный в Ruby on Rails механизм работы с загружаемыми файлами, использующий библиотеку libvips для обработки изображений. Механика KindaRails2Shell построена на том, что разные части системы по

2💯1🙊1🆒1

1 Sept 2026, 05:44 UTC≈1,370 views7 reactionsread 1 September 2026
Photo

NightmareEclipse опубликовал сразу три PoC Помимо вышеописанного эксплойта к Kaspersky Endpoint Security, хакер NightmareEclipse раскрыл демонстрационный PoC-код также для Avast Antivirus и компонентов NVIDIA. Заявленный риск варьируется от повышения привилегий до повреждения памяти. Ни одна находка пока не получила CVE, независимого подтверждения или бюллетеня производителя. PrettyPrague якобы позволяет получить S

4👀3

31 Aug 2026, 07:15 UTC≈10,200 views7 reactionsread 1 September 2026
Photo

HardBreacher: новый эксплойт обходит Kaspersky Endpoint Security и добирается до System32 Исследователь Nightmare Eclipse опубликовал эксплойт HardBreacher, позволяющий применять корпоративный антивирус для обхода защиты ОС. Тесты на Windows 11 25H2 с KES 14.0.0.504 показали, что обычный пользователь способен записать файл прямо в защищенную директорию System32 и получить полный контроль над созданным объектом. Разр

👀3👍1💯1🙏1🆒1

29 Aug 2026, 12:35 UTC≈1,930 views5 reactionsread 1 September 2026
Photo

Серверы Gitea с открытой регистрацией стали удобной целью для хакеров Shadowserver насчитал 8393 доступных извне сервера Gitea, уязвимых для CVE-2026-60004 с оценкой 9,8 по CVSS 3.1. Уязвимость уже используют в реальных атаках с удалённым выполнением кода, а CISA внесло её в каталог активно эксплуатируемых. Проблема связана с API diffpatch. Пользователь с правом записи может внедрить команды через Git hook и выполн

3🤯2

28 Aug 2026, 11:41 UTC≈2,050 views5 reactionsread 1 September 2026
Photo

В прошивке ZBT нашли ещё два механизма удалённого доступа Специалисты VulnCheck обнаружили бэкдоры DARKLANTERN и SPEAKINGSTONE в маршрутизаторе Deep Orange, купленном у американского поставщика. Устройство оказалось переименованной версией китайского ZBT-WE826-T2 производства Shenzhen Zhibotong Electronics. DARKLANTERN слушает UDP-порт 9992 без шифрования и полноценной аутентификации, позволяя выполнять произвольны

🤬31👾1

28 Aug 2026, 08:48 UTC≈2,010 views3 reactionsread 1 September 2026
Photo

В сервисе LiteLLM, который соединяет приложения компаний с ИИ-моделями, хакеры нашли брешь в защите и проникли внутрь через открытый в интернет доступ. Оттуда они украли пароли и ключи, а на сервере незаметно запустили программу для добычи криптовалюты. В сервисе RAGFlow, который помогает работать с документами и ИИ-моделями, злоумышленники встроили скрытый Python-модуль, перехватывавший новые учётные данные к языко

🆒2🤬1

28 Aug 2026, 07:02 UTC≈1,820 views0 reactionsread 1 September 2026
Photo

ИИ меняет скорость поиска уязвимостей в программном обеспечении Во втором квартале 2026 года число зарегистрированных уязвимостей достигло рекорда на фоне распространения ИИ в разработке и анализе кода. ИИ-инструменты позволяют быстро находить целые классы проблем, что особенно заметно проявилось в Linux с семейством уязвимостей Dirty Frag. Программы с ИИ сами стали крупным источником уязвимостей — у проекта OpenCl

28 Aug 2026, 05:11 UTC≈1,760 views2 reactionsread 1 September 2026
Photo

Более 100000 сайтов WordPress оказались под угрозой из-за плагина Pods Уязвимость CVE-2026-19598 (9,8) обнаружена в AJAX-маршрутизаторе pods_admin популярного плагина Pods для WordPress. Проблема затрагивает версии плагина начиная с 2.8 и вплоть до 3.3.9 включительно, а сам плагин насчитывает более 100 000 активных установок. Функция pods_error() при обработке JSON в одном из режимов не останавливала выполнение зап

👍2

28 Aug 2026, 03:04 UTC≈1,890 views1 reactionsread 1 September 2026
Photo

Две уязвимости SharePoint позволяют обойти аутентификацию и выполнить код Специалисты Rapid7 обнаружили уязвимость CVE-2026-55040 (9,1) в механизме проверки JWT-токенов SharePoint. Несколько недочётов в проверке токенов позволяют неавторизованному пользователю сформировать поддельный JWT и действовать от имени любого пользователя, включая администратора сайта. Полученные права открывают путь ко второй уязвимости —

1

27 Aug 2026, 19:12 UTC≈1,830 views5 reactionsread 1 September 2026
Photo

Новая брешь затронула все версии GNU Wget до 1.25.0 Уязвимость CVE-2026-16599 (5,1) обнаружена в механизме FTP-аутентификации OPIE/S-KEY, который используется в GNU Wget. Проблема связана с тем, что Wget не проверял верхнюю границу порядкового номера, полученного от сервера при вычислении MD5-хеша. Для эксплуатации достаточно контролировать FTP-сервер или перехватывать трафик между сервером и клиентом. При передаче

🥰2🙈21

27 Aug 2026, 18:22 UTC≈1,830 views3 reactionsread 1 September 2026
Photo

Ubiquiti закрыла 21 критическую уязвимость в экосистеме UniFi Ubiquiti исправила 21 уязвимость в UniFi Protect, Network, Access, Talk, Connect, UniFi OS Server и других продуктах. Все ошибки получили от 8,2 до 10 баллов CVSS, а наиболее опасные позволяли обходить аутентификацию и выполнять произвольные команды. Главный риск связан с недостаточной проверкой входных данных. CVE-2026-77537 в UniFi Protect получила 10

🔥2😨1

27 Aug 2026, 17:24 UTC≈1,420 views31 reactionsread 1 September 2026
Advertisementerid CQH36pWzJqE1dR7Fsj4EY9f59dnFN6DWRnLFUPMV4vYWKKForwarded from @SecLabNewsPhoto

Что делать компании, если привычные сайты банков, контрагентов или госплощадок внезапно начинают открываться с предупреждением «Подключение не защищено»? Одна из причин связана с переходом российских организаций на сертификаты Национального удостоверяющего центра Минцифры. GlobalSign постепенно отзывает сертификаты российских компаний, а Chrome, Safari, Firefox и Edge по умолчанию не доверяют сертификатам НУЦ. В рез

🤡21💩8🤬2

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

SecurityLab.ru
@SecLabNews · 84,459
Telegram ranks this channel #6 of 90 here — alongside 89 others — read 18 August 2026
Техно педали!
@Technical_R_D · 41,170
Telegram ranks this channel #17 of 40 here — alongside 39 others — read 2 September 2026
ИгорёХа
@igortv · 43,169
Telegram ranks this channel #23 of 38 here — alongside 37 others — read 11 September 2026
Positive Hack Days Media
@positivehackmedia · 30,694
Telegram ranks this channel #34 of 88 here — alongside 87 others — read 6 September 2026
Хакер — Xakep.RU
@xakep_ru · 39,506
Telegram ranks this channel #37 of 83 here — alongside 82 others — read 30 August 2026
Positive Technologies
@Positive_Technologies · 28,968
Telegram ranks this channel #43 of 87 here — alongside 86 others — read 9 September 2026
SecAtor
@true_secator · 41,700
Telegram ranks this channel #45 of 78 here — alongside 77 others — read 29 August 2026
restore:
@restore_ru · 119,981
Telegram ranks this channel #55 of 84 here — alongside 83 others — read 3 September 2026

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

“0day Alert” (@ZerodayAlert), 10,948 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/ZerodayAlert.

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.