Channel
@z3rblog
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
191subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002335787252 |
|---|---|
| Type | Channel |
| Username | @z3rblog |
| Description | Взломы |
| Created | 18 May 2025 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/z3rblog |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 06:48 | 191 | no change |
| 6 Aug 2026, 08:23 | 191 | first reading |
9 posts held, back to 18 May 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 9 posts for this entry, the most recent from 9 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
92 reactions across 8 posts, in 2 distinct kinds. The most used accounts for 70.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ⚡ | 65 | 70.7% | |
| 🌭 | 27 | 29.3% |
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 8 of the 9 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 92reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 18 May 2025 to 9 March 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.
Собственно, видимо это был последний мой баг на h1, потому что аккаунт забанили. И скорее всего это не локальная проблема, у меня есть еще как минимум один знакомый с такой жа проблемой. Что довольно интересно, т.к. официально они прекратили только выплаты гражданам РФ, но не прием багов: Have Russian and Belarusian hackers been suspended from HackerOne? No, although we continue to evaluate all interactions with ha…
🌭12
Опубликовали еще одну мою CVE - CVE-2026-3125. Тут особо про саму уязвимость рассказывать нечего, но можно рассказать про окуржение. Дело в том, что opennextjs-cloudflare запускается в cloudflare worker, а у них довольно сильная и интересная модель безопасности. Большая часть ее описания посвящена проблемам запуска нагрузок разных тенантов в одном процессе и борьбе с spectre/metdown атаками которые из этого вытекаю…
⚡13
Ура, наконец опубликовали еще одну мою CVE! Я конечно устал их пинговать, починили сразу, заплатили и потом морозили 2 месяца, хз чего добивались. Приманка для читателей: полузабытая но все еще полезная техника arbitrary file append to RCE. Истинная цель поста - показать как меня (и не только!) обидела платформа huntr.com. Ошибочно посчитали мой репорт дубликатом и задисклоузили RCE до фикса (уязвимые сервера есть,…
⚡17🌭6
Чел из Китая нашел, как докрутить это CVE до file inclusion и SSRF. Ну значит не будет CTF таска, эх. https://rce.moe/2025/09/29/CVE-2025-41243/
🌭9
Написал некоторые заметки про недавно опубликованное CVE-2025-41243, которое нашел еще летом. Все еще не покидает ощущение что это было RCE, но я не докрутил. Предлагаю ознакомиться! CW: java, SpEL
⚡9
В этом году делал таск на VolgaCTF. Вот небольшой райтап, показалось что спойтили только одну вулну. https://blog.z3r.ru/posts/volgactf2025-s3waaas/
⚡11
Недавно мы играли в SAS CTF и очень обидно не решили таск. Настолько обидно, что пришлось разбираться почему не получилось. Разбор затянулся и закончился исходниками хромиума. Так что сегодня вы можете прочитать про известные мне техники обхода Content-Dispositon: attachment. Может есть и другие?
⚡9
Сегодня на PHDays буду рассказывать про особенность Apport, которая позволяет при определенных конфигурациях системы сделать LPE. Более подробный разбор можно почитать в блоге.
⚡6
Channel created
Showing the 9 most recent of 9 posts we hold for @z3rblog. 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 — 552,124 of 1,481,217entries 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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“blog.z3r.ru” (@z3rblog), 191 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/z3rblog.
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.