Channel
@operations_cyber
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
19subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002599443817 |
|---|---|
| Type | Channel |
| Username | @operations_cyber |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/operations_cyber |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 16:30 | 19 | no change |
| 6 Aug 2026, 03:38 | 19 | first reading |
20 posts held, back to 27 July 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 9 August 2026 |
|---|---|
| Posts held | 20 (27 July 2026 – 9 August 2026) |
| Views total | 477 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Aug 2026, 16:30 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.
Lifetime counters from Telegram’s own channel header, read 11 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.
Представь: у тебя в сумке лежит AirTag, чтобы найти её, если потеряешь. Логично же? А теперь представь, что этой же меткой воспользуется вор - заставит трекер пищать по команде и на слух найдёт твою сумку среди сотен других в вагоне метро. Apple добавила в Find My функцию против слежки: любой может заставить чужой «потерянный» AirTag звенеть. Благородно. Исследователи из HKUST развернули эту защиту против владельца.…
You know those little AirTags people toss in bags to track their stuff? They rely on Apple's Find My network to phone home. Turns out that same system can be turned against you. I found research showing how a regular Android phone can spot a nearby AirTag, then make it play a sound on command - no authentication needed - to pinpoint which bag it's hiding in on a packed subway. The culprit? Three structural flaws in …
Все хотят повесить рост шифровальщиков на ИИ - удобно, модно, продаётся. А исследователи говорят другое: экосистема просто фрагментировалась. Крупные картели поразвалились, на их месте расплодилась куча мелких групп, порог входа упал, и все дружно пошли туда, где защиты нет - в небольшие конторы, которые никто и не думал прикрывать. Никакого волшебного AI-оружия, обычная рыночная логика. Спрос есть, барьеры низкие, …
Everyone wants to pin the rise of ransomware on AI — it's convenient, trendy, and it sells. But researchers say otherwise: the ecosystem simply fragmented. The big cartels fell apart, and in their place a bunch of small groups sprouted up, the barrier to entry dropped, and everyone flocked to where there's no defense — small shops that nobody ever thought to protect. No magic AI weapon, just plain market logic. Ther…
Представь: под столом в переговорке приклеен кусочек пластины размером с ноготь. Без батарейки, без проводов, к твоей клавиатуре вообще никак не подключён. А в соседней комнате, за бетонной стеной, сидит приёмник и читает всё, что ты печатаешь - пароли, сообщения, запросы. Атаку назвали RadKey. Самое неприятное в ней - ей не нужны образцы твоих нажатий. Ноль. Обычные акустические атаки без этого разваливаются, а тут…
You know how keyloggers usually need software on your machine or a device plugged into your keyboard? Forget all that. Imagine a tiny sticker, an inch wide, glued under your desk. No battery, no wires, no link to your keyboard at all. And someone in the next room reads every key you press - passwords, messages, searches. The wild part? It works through a 15 cm concrete wall, with no direct radio path. The signal jus…
87 из 109 бюллетеней безопасности Qubes за все годы — это не про баги самого Qubes, а про Xen, микроархитектуру процессоров и прочий upstream. Такой вывод даёт лонгитюдный разбор 109 QSB с 2011 по 2025 год: почти 80% проблем прилетают из компонентов, которые команда Qubes не пишет, а только вынуждена изолировать. И в этом, кстати, вся суть их архитектуры - границы между виртуалками сделаны так, что дыра в Xen станов…
87 out of 109 Qubes security bulletins across all the years aren't about bugs in Qubes itself, but about Xen, CPU microarchitecture, and other upstream stuff. That's the conclusion of a longitudinal analysis of 109 QSBs from 2011 to 2025: nearly 80% of the issues come from components that the Qubes team doesn't write, but is merely forced to isolate. And that, by the way, is the whole essence of their architecture —…
Ты в рабочем чате Signal, договариваетесь о встрече. Все видят «15:00, третий этаж». Все, кроме тебя - тебе приходит другое время и другая комната. А коллегу Кэрол из ветки будто вырезали, она не увидела ничего. И никакого предупреждения ни от клиента, ни от сервера. Сквозное шифрование прячет содержимое от сервера, но есть свойство поскромнее - согласованность транскрипта: все участники группы должны в итоге видеть…
You trust that everyone in your group chat sees the same messages, right? Turns out that assumption can break. I found research showing how someone can send different people different versions of the same message - one colleague gets "3 PM, third floor," you get a totally different time and place, and another person gets silently cut out with zero warnings. I tested this against WhatsApp, Signal, iMessage, and Three…
MAC-адрес меняется за секунду, IMEI перепрошивается, крипто-ключ генерируется заново. А что если тебя опознают вообще не по этому? Любое беспроводное устройство - роутер, дрон, наушники - гонит сигнал через усилитель, осциллятор, смеситель. Ни одна деталь не идеальна: на заводе разброс параметров, микроскопическая кривизна характеристик. И каждый передатчик излучает сигнал с уникальным набором искажений. Отпечаток п…
You can change your MAC address in a second, regenerate crypto keys, even reflash your IMEI. But what if your device could still be tracked - by tiny physical flaws baked into its hardware? Every transmitter has imperfections: amplifier nonlinearity, frequency offset, oscillator defects. These leave a unique fingerprint in the signal itself, right at the physical layer. It's called RFF, and you cannot fake or reset …
Showing the 12 most recent of 20 posts we hold for @operations_cyber. 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 — 133,785 of 1,189,255entries 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.
Named by
Channels on the register whose posts name this channel's handle.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“CyberOps” (@operations_cyber), 19 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/operations_cyber.
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.