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 10 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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.
Growth
34 measurements spanning 51 days, net +325. 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 16,465–16,899 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)
Subscribers
Change
26 Sept 2026, 12:59
16,849
+70
17 Sept 2026, 14:19
16,779
+3
15 Sept 2026, 11:20
16,776
-1
13 Sept 2026, 19:01
16,777
+5
12 Sept 2026, 01:19
16,772
+15
9 Sept 2026, 14:57
16,757
+50
6 Sept 2026, 04:18
16,707
+9
4 Sept 2026, 00:01
16,698
+15
2 Sept 2026, 15:59
16,683
-5
1 Sept 2026, 18:38
16,688
+1
31 Aug 2026, 18:48
16,687
+9
30 Aug 2026, 21:43
16,678
+1
28 Aug 2026, 20:13
16,677
+9
27 Aug 2026, 22:34
16,668
+15
27 Aug 2026, 00:45
16,653
+9
26 Aug 2026, 01:56
16,644
+9
24 Aug 2026, 23:58
16,635
+8
23 Aug 2026, 11:25
16,627
+15
21 Aug 2026, 18:48
16,612
+6
20 Aug 2026, 16:25
16,606
first reading
Engagement
31 posts held, back to 23 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 55 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
12.5%
avg views ÷ 16,849 subscribers
Avg views / post
2,110
4 posts measured
Reaction rate
0.735%
reactions ÷ views · ER floor
Posts in window
4
of 31 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
Window
Rolling 30 days · latest post in window 2 September 2026
Posts held
31 (23 July 2026 – 2 September 2026)
Views total
8,440
Reactions total
62
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
3 Sept 2026, 09:46 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
435 reactions across 29 posts, in 15 distinct kinds. The most used accounts for 31.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
137
31.5%
👍
89
20.5%
😁
84
19.3%
custom 5325560534219636578
34
7.82%
⚡
19
4.37%
❤🔥
18
4.14%
👾
14
3.22%
custom 5393222555647646099
11
2.53%
💔
10
2.30%
😈
5
1.15%
🌚
4
0.92%
💯
3
0.69%
😱
3
0.69%
🎉
2
0.46%
🏆
2
0.46%
Custom emoji. 2 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 31 of the 31 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 476 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 23 July 2026 to 2 September 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.
Telegram Stars
Stars received
9
across the posts below
Posts paid on
3
of 31 we hold a reading for · 10%
Most on one post
7
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @poxek. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 31 most recent posts we hold for this entry, published 23 July 2026 to 2 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Advertising
Ad load
9.68%
3 of 31 posts carry an ad marker
Regulatory tokens
2
posts carrying an erid · 2 distinct tokens
Median views · ads
2,130
over 3 measured posts
Median views · rest
3,320
over 28 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2VtzqvwcGu9
1
1 September 2026
1 September 2026
2W5zFHSycHf
1
2 September 2026
2 September 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 31 most recent posts we hold, published 23 July 2026 to 2 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
— А ты динозавров ИБ без MFA видел?
В новом выпуске техно-дискуссий К2 Кибербезопасность сравним, как менялась сфера: от набора уязвимостей и инструментов до подходов к обучению специалистов.
В эфире обсудим:
✅ в чье время кибербезопасность была более понятной и предсказуемой
✅ как менялось отношение к ИБ: отказ, аутсорс, создание внутренних отделов
✅ было ли (и есть ли) сильное ИБ-образование в России и что важне…
вы пробили приложение на Windows IIS и сидите в контексте AppPool
дальше пользуетесь тем, что в сеть этот AppPool ходит уже под машинным аккаунтом
выпускаем на него сертификат в AD CS по дефолтному шаблону Machine, через PKINIT меняете серт на TGT машины -> S4U2Self -> Administrator к CIFS этого же хоста
??????
SYSTEM без картошки и других танцев с SeImpersonatePrivilege
https://www.mannulinux.org/2026/08/Privilege…
Week Offer для инженеров AppSec, InfraSec и SOC L3
Приглашаем инженеров по информационной безопасности с опытом от 2 лет получить офер в Яндекс за неделю.
Как всё устроено:
♒️Зарегистрируйтесь до 4 сентября.
♒️Пройдите технические секции 12 и 13 сентября.
♒️Познакомьтесь с нанимающими менеджерами и получите офер 14–18 сентября.
Формат полностью удалённый, от вас нужен только ноутбук и тихое место, где вас никто н…
Всем привет! Мой коллега Вячеслав Цепенников выступал на OFFZONE с докладом «Living off the Browser». Он наресерчил крутой функционал Direct Sockets внутри Chrome, который позволяет через Isolated Web Apps отправлять полноценные сетевые TCP/UDP-запросы. Путем нескольких бессонных ночей получилось внутрь Isolated Web App портировать большинство самых популярных тулз для пентеста! Теперь вы можете буквально ломать чере…
7-Zip читает заблокированные файлы Windows — дампим SAM
Тестировал один интересный вектор — 7-Zip умеет открывать физический диск напрямую через raw disk access.
Запускаем от администратора, в адресной строке вводим:
\\.\PhysicalDrive0\
Дальше переходим до нужного раздела и находим Windows\System32\config\ — SAM и SYSTEM лежат там как обычные файлы, Windows их не блокирует на этом уровне.
Копируем, извлекаем через se…
ИИ-агент устроил инцидент. Кто и как будет его расследовать?
На E-CODE 2026 об этом поговорят в отдельном треке по информационной безопасности. Один из докладов разберёт применение Defense-in-Depth и DFIR в компании ИИ-агентов: как строить эшелонированную защиту и готовиться к расследованиям в инфраструктуре, где агенты действуют самостоятельно.
Контекст шире одной темы. В программе — создание аналога SLSA одноврем…
Саммари докладов OFFZONE AI.Zone - наши агенты сбегали (ну а как иначе, наши агенты самые сильные хацкеры). Мы их ловили и говорили Ата-та-та, возможно потом даже что-то поменяли в среде работы агента
Похек жесточайше получил бейдж и одним глазком поредтимил площадку
(Остальные инсайды не стал выкладывать, завтра сами увидите)))
Очень советую приехать сегодня и получить бейдж, иначе завтра принудительно придётся практиковать обочечный нетворкинг))
Но берите сегодня, может и 20-21 зонтики на всякий случай или ветровки
*площадка еще строиться, к завтра уже будет бимбо))
Activation Lock и Quick Start: когда миграция данных затрагивает владение
Activation Lock задуман как защита, которая переживает стирание устройства. По документации Apple, после включения Find My состояние блокировки проверяется через серверы активации, а повторная активация требует учётной записи владельца. Apple Support
В полном отчёте от 5 июня 2026 описан кейс на конкретной связке: iPhone 13 с iOS 18.6, заблок…
Опубликовал новую статью: три месяца внутри двух ханипотов
Я три месяца наблюдал за двумя среднеинтерактивными ханипотами: традиционным стендом под легендой инфраструктуры поставщика промышленного оборудования (SCADA короче) и отдельным AI-шлюзом с интерфейсами, совместимыми с Ollama и OpenAI, и минимальным MCP.
На SSH/Bitrix-стенде накопилось 312 932 сессии. Почти 4/5 сессий после входа выполняли одну команду — ча…
👍15🔥8
Signed Сергей Зыбнев
Showing the 12 most recent of 31 posts we hold for @poxek. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Forward network
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.
Mentions
Named by 16 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.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Пакет Безопасности @package_security · 33,011 Telegram ranks this channel #1 of 82 here — alongside 81 others — read 4 September 2026
Codeby @codeby_sec · 37,041 Telegram ranks this channel #1 of 76 here — alongside 75 others — read 1 September 2026
infosecurity @tg_infosec · 26,779 Telegram ranks this channel #3 of 74 here — alongside 73 others — read 11 September 2026
Хакер — Xakep.RU @xakep_ru · 39,610 Telegram ranks this channel #4 of 83 here — alongside 82 others — read 30 August 2026
Белый хакер @bezopasno_soft · 29,706 Telegram ranks this channel #5 of 78 here — alongside 77 others — read 8 September 2026
SecAtor @true_secator · 41,748 Telegram ranks this channel #5 of 78 here — alongside 77 others — read 29 August 2026
infosec @it_secur · 61,761 Telegram ranks this channel #6 of 81 here — alongside 80 others — read 22 August 2026
Life-Hack - Хакер @haccking · 63,183 Telegram ranks this channel #6 of 85 here — alongside 84 others — read 21 August 2026
S.E.Reborn @S_E_Reborn · 22,374 Telegram ranks this channel #7 of 66 here — alongside 65 others — read 20 September 2026
S.E.Book @S_E_Book · 23,146 Telegram ranks this channel #7 of 64 here — alongside 63 others — read 19 September 2026
CyberYozh @cyberyozh_official · 62,701 Telegram ranks this channel #7 of 81 here — alongside 80 others — read 21 August 2026
Russian OSINT @Russian_OSINT · 47,701 Telegram ranks this channel #8 of 82 here — alongside 81 others — read 26 August 2026
Борьба с киберпреступностью | F6 @f6_cybersecurity · 22,318 Telegram ranks this channel #9 of 85 here — alongside 84 others — read 21 September 2026
Разведка в интернете @razvedka_v_internete · 36,398 Telegram ranks this channel #9 of 46 here — alongside 45 others — read 2 September 2026
Пост Лукацкого @alukatsky · 37,862 Telegram ranks this channel #9 of 89 here — alongside 88 others — read 31 August 2026
no system is safe // cybersec @nsis_cybersec · 21,518 Telegram ranks this channel #11 of 71 here — alongside 70 others — read 23 September 2026
Investigation & Forensic TOOLS @forensictools · 22,417 Telegram ranks this channel #11 of 74 here — alongside 73 others — read 20 September 2026
Интернет-Розыск @irozysk · 45,953 Telegram ranks this channel #11 of 79 here — alongside 78 others — read 27 August 2026
ZeroDay | Кибербезопасность @cybersec_academy · 42,838 Telegram ranks this channel #12 of 70 here — alongside 69 others — read 29 August 2026
IT и безопасность @tg_security · 26,560 Telegram ranks this channel #13 of 91 here — alongside 90 others — read 12 September 2026
SecurityLab.ru @SecLabNews · 84,654 Telegram ranks this channel #13 of 90 here — alongside 89 others — read 18 August 2026
Positive Technologies @Positive_Technologies · 29,062 Telegram ranks this channel #14 of 87 here — alongside 86 others — read 9 September 2026
Кладовка Pavlu @KladovkaPavlu · 65,054 Telegram ranks this channel #14 of 76 here — alongside 75 others — read 4 September 2026
Лаборатория хакера @lab_hack · 25,556 Telegram ranks this channel #16 of 71 here — alongside 70 others — read 14 September 2026
This channel appears in 48 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 26 September 2026 — this
entry's latest reading, not the date you are reading this.
“Похек” (@poxek), 16,849 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/poxek.
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.