Channel
@kiberdruzhinnik
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
548subscribers
-6 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001851619299 |
|---|---|
| Type | Channel |
| Username | @kiberdruzhinnik |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/kiberdruzhinnik |
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 21 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 11:39 | 548 | -1 |
| 8 Sept 2026, 09:21 | 549 | -2 |
| 29 Aug 2026, 19:07 | 551 | +2 |
| 21 Aug 2026, 20:16 | 549 | -1 |
| 15 Aug 2026, 15:13 | 550 | -4 |
| 7 Aug 2026, 15:03 | 554 | no change |
| 7 Aug 2026, 03:03 | 554 | first reading |
20 posts held, back to 27 March 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.
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 31 July 2026. An engagement rate over an empty window would be a number about nothing.
1️⃣ 🔍 WhaleSecret Анализируем компрометацию внутреннего сервиса, запущенного в докере. https://boosty.to/kiberdruzhinnik/posts/bec28ab3-6241-45bc-b283-db8f891706b4 2️⃣ 🖥️ DarkZeroReturns Эксплуатируем SSTI-to-RCE и путешествуем между трастами для полного захвата контроллеров домена. https://boosty.to/kiberdruzhinnik/posts/28c88a44-e8db-40f7-be39-663f37590e81
1️⃣ 🔍 TaskForce Получаем базовые навыки работы с ELK-стеком для поиска персиста и дальнейшего продвижения. https://boosty.to/kiberdruzhinnik/posts/b59f1092-6bbd-4c76-ab0d-cea1d2c09014 2️⃣ 🖥️ Bedside Находим способы пробросить Pickle-модель для полной компрометации системы. https://boosty.to/kiberdruzhinnik/posts/903ccc1d-16a0-4c82-ab93-a2dc3e89704c
1️⃣ 🔍 PhantomRing Анализируем простой вредоносный сэмпл под Linux с некоторыми интересными командами eBPF. https://boosty.to/kiberdruzhinnik/posts/1741cfb6-ac01-4b42-934d-4fad68e4e4e3 2️⃣ 🖥️ Paperwork Разбираемся с атакой на принтер в простой машине на Linux. https://boosty.to/kiberdruzhinnik/posts/eb4ffe4c-3027-4c06-8c34-8d8bf8ffd18d
1️⃣ 🔍 Opportunist Рекрутер оказался атакующим — разбираемся с атакой. https://boosty.to/kiberdruzhinnik/posts/8191dfe7-ecec-42ac-851c-6ed24b7481d6 2️⃣ 🖥️ MakeSense Эксплуатируем XSS в CSFR и добиваемся доступа в систему. https://boosty.to/kiberdruzhinnik/posts/88c641ee-ec56-4f7e-b2d9-fc847eb54665
1️⃣ 🔍 CorpDown-2 Форензика четырех хостов компании, которая подверглась взлому. https://boosty.to/kiberdruzhinnik/posts/982e64ec-f357-4305-b874-6fedf4cd4dd2 2️⃣ 🖥️ Enigma Классическая история с паролем по умолчанию, и к чему это может привести. https://boosty.to/kiberdruzhinnik/posts/9e1870d7-86e8-40c9-a006-8c8cca489b47
1️⃣ 🔍 ShadowMonarch Разбираемся с BPFDoor — бэкдором с кодом на виртуальной машине BPF. https://boosty.to/kiberdruzhinnik/posts/8ae90de4-6028-4603-9632-8cde9f9d192e 2️⃣ 🖥️ Nimbus Используем SSRF для доступа к внутреннему порту управления сервисами AWS. https://boosty.to/kiberdruzhinnik/posts/9bafaf2e-2443-48cd-998f-c152cc2cf442
1️⃣ 🔍 KitsuneHook Пользуемся браузером, чтобы почитать отчеты об Winnti. https://boosty.to/kiberdruzhinnik/posts/0e969975-27b5-42a8-bf04-9a0829c1c862 2️⃣ 🖥️ Checkpoint Готовим свое расширение для Visual Studio Code и пробуем эксплуатировать BetterSuccessor. https://boosty.to/kiberdruzhinnik/posts/2994916e-e61e-4d40-9b90-16beb32db18a
https://youtu.be/bAR0XWYnMtU?si=antUPnLAAJW1ik9A
1️⃣ 🔍 Kraken Пользователь запустил RAT-файл, но наш SOC задетектил подозрительные действия, начал реагирование, и ничего страшного не случилось. Соберем индикаторы компрометации (IOC). https://boosty.to/kiberdruzhinnik/posts/176bc4b5-7c5c-42fe-ac24-0b0807cecdd9 2️⃣ 🖥️ Connected Атакуем FreePBX, получаем RCE через SQLi. Если он у вас есть — стоит обновиться. https://boosty.to/kiberdruzhinnik/posts/fdb0274e-6aed-4…
1️⃣ 🔍 CAMouflage Смотрим, почему не стоит использовать подлеченный софт. https://boosty.to/kiberdruzhinnik/posts/dabf63f8-045e-4635-9d50-241f5aa7bd52 2️⃣ 🖥️ DevHub Применим публичный эксплоит для неаутентифицированного RCE для MCPJam, получим токен пользователя из списка процессов для получения доступа в основную систему. Повышение привилегий выполним через открытый токен для OpsMCP. https://boosty.to/kiberdruzh…
1️⃣ 🔍 JobApplicant Расследуем проблему с HR-порталом, которая приводит к эксплуатации AD CS. https://boosty.to/kiberdruzhinnik/posts/49d6a742-648f-48b0-ba5c-9c333c2c598b 2️⃣ 🖥️ Reactor Начали 11 сезон эксплуатацией React2Shell. https://boosty.to/kiberdruzhinnik/posts/5910aea1-4685-4661-8df7-9300b34a87a2
1️⃣ 🔍 Stonks Расследуем финансовый фрод и ковыряемся с Windows Data Deduplication. Два вопроса не доделано в видео, но бравые подписчики не дают запостить райтап без ответов. https://boosty.to/kiberdruzhinnik/posts/1a2ec361-fbb1-4565-b717-66a356fad500 2️⃣ 🖥️ SmartHire Эксплуатация RCE в старой версии MLFlow и повышение привилегий через автоматический запуск нашего кода. https://boosty.to/kiberdruzhinnik/posts/5e…
Showing the 12 most recent of 20 posts we hold for @kiberdruzhinnik. 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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Константин Романов: Кибердружинник 🤖” (@kiberdruzhinnik), 548 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/kiberdruzhinnik.
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.