Channel
@opzero_en
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,113subscribers
+7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001970454686 |
|---|---|
| Type | Channel |
| Username | @opzero_en |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/opzero_en |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 02:58 | 1,113 | +5 |
| 11 Aug 2026, 15:03 | 1,108 | +1 |
| 8 Aug 2026, 19:08 | 1,107 | +1 |
| 8 Aug 2026, 00:03 | 1,106 | no change |
| 7 Aug 2026, 22:51 | 1,106 | first reading |
10 posts held, back to 27 November 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 10 posts for this entry, the most recent from 9 July 2026. An engagement rate over an empty window would be a number about nothing.
158 reactions across 10 posts, in 15 distinct kinds. The most used accounts for 38.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 61 | 38.6% | |
| ❤ | 36 | 22.8% | |
| 🔥 | 28 | 17.7% | |
| ⚡ | 6 | 3.80% | |
| 🫡 | 6 | 3.80% | |
| 👌 | 5 | 3.16% | |
| 😁 | 4 | 2.53% | |
| 👏 | 3 | 1.90% | |
| 👻 | 2 | 1.27% | |
| 🥰 | 2 | 1.27% | |
| 👾 | 1 | 0.633% | |
| 😱 | 1 | 0.633% | |
| 🤔 | 1 | 0.633% | |
| 🤣 | 1 | 0.633% | |
| 🥱 | 1 | 0.633% |
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 10 of the 10 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 158reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 10 most recent posts we hold, published 27 November 2025 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.
Looking for professionals for usermode Windows research projects. Requirements: you have your own private fuzzers for open source and closed source software, and you are proficient with Windows 11 LFH exploitation. Payments are made upon completion of projects. Send your anonymized CV to our email: [email protected] / [email protected] (in case of using Proton or other services banned in Russia) Be sure to encry…
🔥8❤2🥰2
Photo, posted without a caption
👍4
Photo, posted without a caption
👍3❤1
We truly respect what Google and Microsoft do for the security research community. Thanks to them, even such a small companies like OPZERO have been given a chance to work for our country without big expenses: our marketing budget till 2026 was 0 rubles. Fortunately, in 2026 the vendors decided to help the zero-day market grow with decisions that will be written down in marketing books, and perhaps in the annals of h…
❤12
The server is up. DoS for one day? Too weak, colleagues, you can do better. P.S. We kindly ask those who tried to make a submission via the website (by accepting risks of that certificate) or send an email yesterday to retry to do that.
👍4😁4🤔1😱1
Let's Encrypt has banned our certificate and prohibits to release new ones so the website will be unavailable until we get a new certificate from a Russian CA.
👍13🔥2
Recently the amount of submissions generated completely by AI increased drastically. Authors of such submissions themselves often don't understand how their exploits are working and instead of answering our questions provide AI output again. Inability to comprehend how an exploit is working leads to long discussions (if interaction with LLM can be called discussion) with one result: specified capabilities don't match…
👍17❤5👌5
101 Chrome Exploitation — Part 2: Common Browser Vulnerability Patterns We have published a large overview of Chrome vulnerability classes as a part of our browser exploitation series. In the article, we show the attack surface of V8 pipeline and Blink engine, GPU bugs allowing to escape the sandbox, and issues of Mojo IPC and Chrome concurrency. Modern hardware mitigations like PKEYs and MTE are mentioned too. The …
🔥16⚡6❤4👾1🤣1
There are fake Telegram channels "selling" exploits on our behalf. Don't fall for them and follow our official resources only: Website: https://opzero.ru/en X: https://x.com/opzero_en Russian channel: @opzero_ru English channel: @opzero_en
❤11👍4👏3🔥1🥱1
Urgently in demand: — iOS 26 LPE from application to kernel — Up to $500,000 The exploit should work from a user application (Safari isn't required) and give as high privileges as possible, ideally kernel r/w. Zero-days without MIE bypass are still in the scope. Submit: https://opzero.ru/en/submit/
👍16🫡6👻2❤1🔥1
Showing the 10 most recent of 10 posts we hold for @opzero_en. 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 — 69,864 of 1,478,351entries 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.
Named by 2 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“OPERATION ZERO EN” (@opzero_en), 1,113 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/opzero_en.
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.