Telegram RegisterThe public register of Telegram
Telegram profile photo for White Hat

Channel

White Hat

@kind_hack

On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

12,094subscribers

-78 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001568124702
TypeChannel
Username@kind_hack
CreatedBetween 1 August 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live18 August 2026
Measurements held12
Confirmed unchanged1 time, most recently 18 August 2026
On Telegramt.me/kind_hack

Growth

12,09412,17212,1336 August 2026 — 12,172 subscribers7 August 2026 — 12,171 subscribers8 August 2026 — 12,164 subscribers9 August 2026 — 12,152 subscribers10 August 2026 — 12,142 subscribers11 August 2026 — 12,137 subscribers11 August 2026 — 12,134 subscribers12 August 2026 — 12,127 subscribers14 August 2026 — 12,121 subscribers16 August 2026 — 12,110 subscribers17 August 2026 — 12,107 subscribers18 August 2026 — 12,094 subscribers6 August 202618 August 2026
12 measurements spanning 12 days, net -78. 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 12,082–12,184 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
18 Aug 2026, 22:5712,094-13
17 Aug 2026, 22:0212,107-3
16 Aug 2026, 18:2512,110-11
14 Aug 2026, 01:1612,121-6
12 Aug 2026, 21:0312,127-7
11 Aug 2026, 22:5512,134-3
11 Aug 2026, 01:5212,137-5
10 Aug 2026, 00:0212,142-10
9 Aug 2026, 02:3512,152-12
8 Aug 2026, 02:2012,164-7
7 Aug 2026, 05:2612,171-1
6 Aug 2026, 22:3312,172first reading

Engagement

30 posts held, back to 21 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 22 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
6.59%
avg views ÷ 12,094 subscribers
Avg views / post
797
30 posts measured
Reaction rate
0.485%
reactions ÷ views · ER floor
Posts in window
30
of 30 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 17 August 2026
Posts held30 (21 July 202617 August 2026)
Views total23,916
Reactions total116
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Aug 2026, 09:40 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

116 reactions across 30 posts, in 3 distinct kinds. The most used accounts for 56.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6556.0%
👍2824.1%
🔥2319.8%

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 30 of the 30 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 116reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 30 most recent posts we hold, published 21 July 2026 to 17 August 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

17 Aug 2026, 10:37 UTC284 views4 reactionsread 18 August 2026
Photo

☁️ Какой фреймворк выбрать под операцию C2 Matrix – открытый проект Хорхе Орчильеса при поддержке SANS, сравнивающий все публично доступные C2-фреймворки в единой таблице по десяткам параметров. — Решает конкретный вопрос «что взять под эту операцию»: не Sliver против Havoc абстрактно, а фильтрация по тому, нужен ли DNS-транспорт, domain fronting, поддержка macOS и работа без агента, — и получаешь список подходящих

2👍1🔥1

16 Aug 2026, 13:25 UTC436 views3 reactionsread 18 August 2026
Photo

📷 8 агентов, 12 волн, 4 дня | Первый задокументированный AI-пентест против государства Мультиагентный AI-фреймворк – недооценённый вектор, потому что все обсуждают джейлбрейки моделей, а здесь обошлись без них: операцию оформили как авторизованный пентест, и защита, обученная читать намерения по формулировке, приняла это за чистую монету. Фреймворк на Hermes и OpenClaw за четыре дня провёл 12 волн по 8 агентов пара

2🔥1

15 Aug 2026, 12:10 UTC498 views3 reactionsread 18 August 2026
Photo

🔸 Скриншотит тысячи веб-сервисов, чтобы увидеть цель глазами Gowitness – открытая утилита визуальной разведки от SensePost на Go, которая через безголовый Chrome снимает скриншоты веб-страниц пачками по списку хостов. — Это как облёт территории с квадрокоптера перед штурмом: вместо того чтобы вручную открывать сотни IP и портов, ты скармливаешь ему диапазон или вывод nmap и разом видишь, где забытая админка, тесто

3

14 Aug 2026, 13:10 UTC544 views4 reactionsread 18 August 2026
Photo

🤒 Trezor утекла через логиста | ~14 000 клиентов и дыра в Metabase Производитель кошельков Trezor сообщил об утечке почти 14 000 клиентов, но взломали не его, а логиста ShipMonk. У 11 742 утекли имена, email, телефоны и адреса, у 1947 — частично. — Первопричина не в Trezor: по BleepingComputer, ShipMonk взломали через критическую SQLi в Metabase, дающую админа без аутентификации. Тот же 0-day уже задел Framework и

2👍1🔥1

13 Aug 2026, 14:20 UTC597 views3 reactionsread 18 August 2026
Photo

☁️ Google Hacking Database | Находит то, что торчит наружу, одним запросом Google Hacking Database – открытый каталог дорков от Offensive Security на Exploit-DB, начатый Джонни Лонгом, где собрано 8000+ запросов, вытаскивающих из индекса Google то, что владельцы не собирались светить. Дорк ничего не ломает – он фильтрует уже проиндексированное: комбинация site, filetype, inurl и intitle превращает обычный поиск в р

2🔥1

12 Aug 2026, 13:10 UTC658 views4 reactionsread 18 August 2026
Photo

🤒 Guardrails для LLM обходят, поэтому одних их мало Фильтры на входе модели обходят с частотой до 100% – одна прослойка prompt injection не держит, и SOC нужна не стена, а глубина обороны и детект самих попыток инъекции. Guardrails ловят типовое, но не дают гарантии: пропущенный обход бесполезно фильтровать, если за ним никто не наблюдает. — В статье мы разберем четырёхслойную архитектурау защиты LLM, правила корр

2👍1🔥1

11 Aug 2026, 11:06 UTC664 views4 reactionsread 18 August 2026
Photo

🤒 Быстрый рекурсивный обход скрытых путей веб-сервера Feroxbuster – открытый инструмент разведки контента на Rust от разработчика epi052, который перебором по словарю ищет скрытые каталоги, файлы и эндпоинты на веб-сервере. — Если dirb и gobuster просто дёргают пути из списка, feroxbuster идёт вглубь сам: нашёл каталог — тут же рекурсивно прочёсывает и его, разматывая структуру сайта до эндпоинтов, которых нет ни в

👍21🔥1

10 Aug 2026, 17:30 UTC690 views5 reactionsread 18 August 2026
Photo

⚔️ Критический баг в Check Point вскрывает файрвол без пароля Уязвимость CVE-2026-16232 с рейтингом 9.1 бьёт по серверам управления Check Point Security Management и Multi-Domain, где задаются правила файрволов. Без пароля атакующий удалённо получает служебный токен и входит в SmartConsole админом, меняя политики и конфигурацию. — Условие успеха сервер управления смотрит в интернет, а в Trusted Clients стоит Any. У

2👍2🔥1

9 Aug 2026, 13:10 UTC699 views2 reactionsread 18 August 2026
Photo

🤒 Реверс-шеллы с общим доступом между операторами Villain – открытый фреймворк управления реверс-шеллами от t3l3machus, который не просто ловит сессии, а раздаёт их между несколькими C2-инстансами. Фишка в «сиблинг-серверах»: два оператора на разных машинах связывают свои Villain-ы в одну сеть и работают с чужими сессиями как со своими, будто это общий пульт на всю команду. Имеет генерацию обфусцированных Windows

2

8 Aug 2026, 11:10 UTC695 views4 reactionsread 18 August 2026
Photo

😵‍💫 HTTP request smuggling | Контрабанда запроса в чужой сессии Контрабанда HTTP-запросов — недооценённый класс багов: фронтенд и бэкенд по-разному считают, где кончается запрос, и в этот зазор атакующий прячет второй, невидимый первому серверу. Недооценён потому, что баг не в коде, а на стыке инфраструктуры: прокси и апстрим спорят из-за Content-Length против Transfer-Encoding. — В данной статье разберем анатомию

2👍1🔥1

7 Aug 2026, 11:34 UTC739 views4 reactionsread 18 August 2026
Photo

📝 Шпаргалка по внутрянке и Active Directory InternalAllTheThings – открытая шпаргалка Swissky, автора PayloadsAllTheThings, но заточенная не под веб, а под внутренний пентест и эксплуатацию Active Directory. — Если PayloadsAllTheThings арсенал под веб-баги, то этот справочник настольная книга по внутрянке: там, где онлайн-гайдов мало, собраны готовые команды и пути атаки на домен под копипаст в бою. Что внутри: ат

2👍1🔥1

6 Aug 2026, 15:20 UTC760 views5 reactionsread 18 August 2026
Photo

🛡 Один ключ на 2,2 млн машин | Bluetooth-взлом сигнализаций KARR и SWDS Дилерские охранные системы KARR и SWDS от Acrisure, стоящие минимум в 2,2 млн машин, используют один общий ключ для Bluetooth-аутентификации, установили в UCSD. Зная ключ и находясь в 4,5 метра, атакующий открывает двери, сигналит и не даёт завести заглушенную машину. — Устройство ставит дилер как доп-опцию, и оно слушает Bluetooth, даже если в

3👍1🔥1

Showing the 12 most recent of 30 posts we hold for @kind_hack. 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

Citation-graph rank — 1,028,461 of 1,550,164entries 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.

Mentions

Named by 3 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.

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.

Этичный Хакер
@hack_less · 227,939
Telegram ranks this channel #25 of 81 here — alongside 80 others — read 12 August 2026
Social Engineering
@Social_engineering · 125,151
Telegram ranks this channel #42 of 82 here — alongside 81 others — read 13 August 2026

This channel appears in 2 seed channels' Telegram-generated recommendation lists in total. 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 18 August 2026 — this entry's latest reading, not the date you are reading this.

“White Hat” (@kind_hack), 12,094 subscribers as measured 18 August 2026. Telegram Register, tgregister.com/channel/kind_hack.

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.