Telegram RegisterThe public register of Telegram
Telegram profile photo for Defensive acceleration

Channel

Defensive acceleration

@cybersec_dacc

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

108subscribers

+1 since we began measuring on 26 October 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1004473953016
TypeChannel
Username@cybersec_dacc
Created17 July 2026 — measured — dated from the channel’s first post
First recorded26 October 2026
Last confirmed live2 November 2026
Measurements held3
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/cybersec_dacc

Growth

107108107.526 October 2026 — 107 subscribers27 October 2026 — 107 subscribers2 November 2026 — 108 subscribers26 October 20262 November 2026
3 measurements spanning 7 days, net +1. 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 107–108 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Nov 2026, 06:40108+1
27 Oct 2026, 02:45107no change
26 Oct 2026, 04:22107first reading

Engagement

11 posts held, back to 17 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
88.0%
avg views ÷ 108 subscribers
Avg views / post
95.0
1 post measured
Reaction rate
4.21%
reactions ÷ views · ER floor
Posts in window
1
of 11 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 8 October 2026
Posts held11 (17 July 2026 – 8 October 2026)
Views total95
Reactions total4
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken26 Oct 2026, 04:22 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

35 reactions across 9 posts, in 3 distinct kinds. The most used accounts for 54.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1954.3%
👍1131.4%
❤514.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 9 of the 11 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 35 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 17 July 2026 to 8 October 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.

Recent posts

8 Oct 2026, 06:05 UTC95 views4 reactionsread 26 October 2026

Опубликовано несколько уязвимостей, к поиску которых я приложил руку: 1. Эскалация привилегий в Envoy Gateway от пользователя ns до кластер-админа через абьюз CR EnvoyProxy, который создаёт ворклоад в ns оператора. 2. RCE на машине админа в linkerd cli через инъекцию в отдаваемый кубконфиг из объекта пользовательского неймспейса. Редкий кстати случай реалистичной и простой атаки на клиентов куба, а не наоборот. 3.…

🔥4

23 Sept 2026, 16:30 UTC221 views15 reactionsread 26 October 2026

Намного интереснее мой аудит Talos Linux. Это самый безупречно сделанный с точки зрения безопасности Kubernetes дистрибутив. Образ ОС иммутабелен, поверхность атаки на ОС сведена к минимуму, нету даже sh бинаря. "Kubernetes is just five binaries", золотой стандарт, absolute cinema. Тем не менее, ни одна система не истинно безопасна. На днях были опубликованы сразу 5 найденных мной в нём уязвимостей. Самая интересная…

👍8❤4🔥3

23 Sept 2026, 16:12 UTC152 views3 reactionsread 26 October 2026

Опубликованы найденные мной 2-3 месяца назад уязвимости эскалации привилегий от пользователя Kubernetes до кластер-админа в KEDA и Flagger. KEDA - оператор для автоматического масштабирования подов по внешним событиям и метрикам вроде длины очереди в Kafka. Flagger делает удобную Kubernetes-нативную постепенную выкатку новых версий (A/B-тестирование, canary). Уязвимость Flagger GHSA-c2p2-jpmj-qvr2 тривиальна: польз…

👍3

10 Sept 2026, 12:57 UTC410 views3 reactionsread 26 October 2026

AGI таймлайны всё ближе, а remediation таймлайны остаются старыми. Спустя почти три месяца после отправки информации об уязвимости в Kyverno - самом популярном security-admission-controller'е для Kubernetes - наконец вышел патч найденного мной крита. Эскалация до кластер-админа через Policy ресурс, обходом валидации url-пути старым добрым url encoding. Вообще-то я сообщил о двух уязвимостях: вторая позволяет читать …

🔥3

15 Aug 2026, 15:39 UTC375 views3 reactionsread 26 October 2026

Новый день - новый способ заставить оператор Kubernetes слить пользователю свой собственный привилегированный SA токен. В этот раз дыра в HashiCorp Vault Secrets Operator, CVE-2026-8715. Эскалация до кластер-админа: https://cherez0ff.art/blog/vault-secrets-operator-secretidpath-token-theft/

🔥3

14 Aug 2026, 12:36 UTC311 views3 reactionsread 26 October 2026

https://cherez0ff.art/blog/capsule-tenantresource-cluster-admin-escalation/ История о том, как разработчики Capsule (projectcapsule) дали пользователям возможность создавать и читать любой кластерный ресурс и отказывались признавать, что это уязвимость. Частично исправили через месяц после моего отчёта, заблокировав меня и мой отчёт. Уязвимость чтения кластерных ресурсов по-прежнему не закрыта. Самый тривиальный сп…

🔥3

22 Jul 2026, 13:00 UTC239 views1 reactionsread 26 October 2026

Уязвимость в Strimzi Operator: создав объект Kafka в любом неймспейсе, можно прочитать все Secrets в ванильном k8s-кластере. А в OpenShift - гарантированно получить кластер-админа. Помимо описания самой уязвимости, добавил заметку про defense in depth для такого класса атак на кластер. https://cherez0ff.art/blog/strimzi-operator-cross-namespace-rolebinding/

🔥1

18 Jul 2026, 21:02 UTC192 views1 reactionsread 26 October 2026

Нашёл уязвимость в Grafana Operator, позволяющую угнать k8s-кластер, забрав привилегированный токен оператора через дыру в кастомных ресурсах GrafanaDashboard и GrafanaLibraryPanel. Этот крит был оценён разработчиками Grafana как Medium по причине «админ всего кубера - не админ оператора» (что?), так что многие ИБ/платформенные команды её пропустят. Уязвимы версии до v5.24.0 https://cherez0ff.art/blog/grafana-oper…

❤1

17 Jul 2026, 18:39 UTC153 views2 reactionsread 26 October 2026

d/acc - это подход к будущему, основанный на избирательном ускорении технического прогресса: приоритет отдаётся технологиям защиты над технологиями нападения. Сделать щит сильнее меча. Философия видит в сверхразумном ИИ одновременно потрясающую возможность для расцвета человечества и смертельную угрозу для него: искусственные пандемии, кибератаки на критическую инфраструктуру, манипуляция и подрыв доверия в обществе…

🔥2

Showing the 11 most recent of 11 posts we hold for @cybersec_dacc. 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.

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 2 November 2026 — this entry's latest reading, not the date you are reading this.

“Defensive acceleration” (@cybersec_dacc), 108 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/cybersec_dacc.

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.