Channel
@critical_bug
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
3,316subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001926698340 |
|---|---|
| Type | Channel |
| Username | @critical_bug |
| Created | Between 1 March 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/critical_bug |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 14:08 | 3,316 | -1 |
| 7 Aug 2026, 18:00 | 3,317 | +1 |
| 7 Aug 2026, 11:47 | 3,316 | first reading |
20 posts held, back to 5 May 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 3 pagesof 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 20 posts for this entry, the most recent from 9 July 2026. An engagement rate over an empty window would be a number about nothing.
7 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 3 | 42.9% | |
| ❤ | 2 | 28.6% | |
| 🔥 | 2 | 28.6% |
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 6 of the 20 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 5 May 2026 to 9 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.
Где кибериспытания от Т-Банка, там и 50 миллионов 🥂 Перед тобой уникальная возможность проверить, сможешь ли ты повлиять на устойчивость бизнес-процессов одного из крупнейших российских банков и получить вознаграждение до 12 млн рублей за реализацию одного недопустимого события! Рассказываем, как участвовать: 🟡 Подай заявку 🟡 Получи приглашение и доступ к программе 🟡 Продемонстрируй реализацию недопустимого события…
Программа «Точка Банка» теперь доступна всем исследователям 🔎 Что можно изучать: ▫️ tochka.com — основной сайт ▫️ allo.tochka.com — Справочная ▫️ shop.tochka.com — Универмаг ▫️ *.tochka-tech.com — технические сервисы 💸 За найденные баги можно получить до 450 000 рублей. Расставь точки над уязвимостями и забирай баунти в программе ⬅️
📄 Полное объяснение Dirty Frag (CVE-2026-43284)
🔥 CVE-2026-43284: "Dirty Frag" — Новый способ стать root в Linux 😱 Пока вы патчили "Copy Fail", подъехала новая критическая дыра. Исследователи обнаружили уязвимость "Dirty Frag", которая позволяет локальному пользователю получить полные права root на большинстве современных дистрибутивов. 💥 В чем прикол? Это логическая ошибка в подсистемах xfrm-ESP и RxRPC. Используя системный вызов splice(), атакующий может заста…
🔥2
Photo, posted without a caption
📄 Полное объяснение CVE-2026-41940 (cPanel Auth Bypass)
🔥 CVE-2026-41940: Массовый взлом cPanel через обход авторизации! 😱 Пока админы спали, хакеры из группировки Mr_Rot13 начали захватывать тысячи серверов по всему миру. Критическая дыра в cPanel & WHM позволяет получить права root без пароля. Буквально. 💥 Суть бага: Ошибка в логике проверки токенов. Атакующий шлет хитрый запрос и вуаля — он в системе. 🚨 Что происходит: Ставят бэкдоры на Go, крадут SSH-ключи и пароли …
👍1
📄 Полное объяснение CVE-2026-33825 (BlueHammer)
❤1
🔥 CVE-2026-33825: BlueHammer & RedSun — LPE в Windows Defender! 😱 В Microsoft Defender нашли критическую дыру (CVE-2026-33825), позволяющую любому пользователю получить права SYSTEM! 😈 💥 Суть: Баг в механизме Time-of-Check to Time-of-Use (TOCTOU). Атакующий может подменить файл во время очистки угроз через NTFS-соединения, заставляя Defender перезаписать системные файлы своим кодом. 🚨 Почему это опасно? — Полный к…
👍1
📄 Полный технический разбор CVE-2026-25592
🔥 RCE в AI-агентах через промты! (CVE-2026-25592) 🔥 Друзья! Сегодня разбираем свежую критическую уязвимость в Semantic Kernel от Microsoft. 🤯 Что произошло? Злоумышленники могут добиться удаленного выполнения кода (RCE) на хосте, просто манипулируя промтами AI-агентов. Это проблема архитектуры, позволяющая превратить инъекцию промтов в полный захват системы. 🛠️ Как это работает? Функция DownloadFileAsync была ошиб…
❤1
📄 Полное объяснение CVE-2026-0300 (Palo Alto RCE)
👍1
Showing the 12 most recent of 20 posts we hold for @critical_bug. 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.
Citation-graph rank — 614,301 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by 1 registered channel — 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Репорты простым языком” (@critical_bug), 3,316 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/critical_bug.
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.