Telegram RegisterThe public register of Telegram

Channel

Pentester`s Notes

@hackn0tes

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Cite this entry

491subscribers

+9 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001562137382
TypeChannel
Username@hackn0tes
CreatedBetween 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/hackn0tes

Growth

482491486.56 August 2026 — 482 subscribers6 August 2026 — 482 subscribers13 August 2026 — 491 subscribers6 August 202613 August 2026
3 measurements spanning 7 days, net +9. 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 481–492 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 08:58491+9
6 Aug 2026, 18:49482no change
6 Aug 2026, 08:22482first reading

Engagement

19 posts held, back to 13 November 2025the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 10 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

155 reactions across 17 posts, in 13 distinct kinds. The most used accounts for 46.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥7246.5%
3723.9%
👍2012.9%
❤‍🔥42.58%
🤝42.58%
👨‍💻31.94%
😁31.94%
😱31.94%
🤣31.94%
👏21.29%
🤗21.29%
👾10.645%
😘10.645%

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

Measured over the 19 most recent posts we hold, published 13 November 2025 to 10 July 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
21
across the posts below
Posts paid on
8
of 19 we hold a reading for · 42%
Most on one post
13
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @hackn0tes. 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 19 most recent posts we hold for this entry, published 13 November 2025 to 10 July 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.

Recent posts

10 Jul 2026, 15:37 UTC302 views5 reactionsread 6 August 2026
Forwarded from @s0ld13r_chPhoto

И таааааак сойдет😅 Давно ничего не постил. За это время успел увидеть как все резко стали экспертами по мультиагентным системам, MCP, A2A и еще двадцати новым аббревиатурам которые появляются быстрее чем новые модели у OpenAI ⭕️ Но как бы то ни было, жизнь ироничная штука. В какой-то момент я тоже решил посмотреть, что вообще происходит в мире AI для Offensive Security. Перетестил разные инструменты, поковырял open

🤝3🔥2

9 Jun 2026, 10:38 UTC606 views2 reactionsread 6 August 2026
Photo

Интересный проект, позволяет двум ИИ мусолить какую-то тему и спорить между собой, приходя к каким-то более объективным результам. Но токены ест много (можно запускать, если лимиты остались, а потратить надо) Статья: https://jfmaes.me/blog/crossfire-when-one-llm-isnt-enough/ Проект: https://github.com/jfmaes/crossfire

👍1🔥1

7 Jun 2026, 18:49 UTC648 views6 reactionsread 6 August 2026

Ооо, доработали Netexec для простой реализации этой техники😁 SPN-less RBCD with NetExec🔥 While classic RBCD requires a computer account, you can use U2U authentication to perform RBCD with a normal user account, if a computer account is not available. Thanks to @azoxlpf, you can now perform this attack with NetExec as well🚀 https://x.com/i/status/2063651501982031926 (Не помню, что нужно писать, если упоминаешь р

😁3🔥2🤝1

4 Jun 2026, 14:45 UTC667 views7 reactionsread 6 August 2026

🧦 Запилил proxykit — маленькую Go-библиотеку для исходящих соединений через прокси. Стандартный net/http умеет в прокси ровно одно — прочитать HTTP_PROXY из окружения. А за корпоративным прокси начинается боль: настройки спрятаны в реестре Windows, в GNOME/KDE, в scutil на маке; авторизация по NTLM или Kerberos; маршрут выбирает PAC-скрипт. proxykit закрывает именно этот разрыв. Что умеет: 🔌 Транспорты: HTTP/HTTPS

🔥7

4 May 2026, 15:29 UTC823 views7 reactionsread 6 August 2026
Photo

Выкатил небольшую тулзу для анализа AppLocker-политик — AppLocker Viewer 🛠. Суть: Скармливаете ей XML от Get-AppLockerPolicy, и она сразу показывает, где защита реально держит периметр, а где админы оставили удобные форточки для обхода 🔓. Что внутри: - CLI для парсинга, фильтрации и выгрузки результатов в таблицу, JSON или CSV 📊. - Поиск рисков (сразу подсветит writable paths, слишком широкие маски, LOLBins и прави

🔥7

30 Apr 2026, 09:07 UTC536 views3 reactionsread 6 August 2026
Forwarded from @ptswarmPhoto

🧑‍🚒 Our researcher Mikhail Sukhov shares his knowledge and experience in analyzing FreeIPA environments. He also introduces his new tool, IPAHound 💪 Go ’n see the details ➡️ https://swarm.ptsecurity.com/thinking-in-graphs-with-ipahound/

1👍1🔥1

22 Apr 2026, 12:43 UTC858 views11 reactions1 Starread 6 August 2026

В общем, есть такой скрипт - ultimate_nmap_parser (как-то так). Он парсит результаты nmap (в формате gnmap) и выдаёт файл, содержащий ip:port. Работает достаточно долго. Я написал однострочник, который работает во много-много раз быстрее. for i in `cat networks.gnmap | grep '/open/' | awk '{print $2}'`; do for j in `cat networks.gnmap | grep $i' ' | grep -oP '\d+(?=/open/)'`; do echo $i:$j >> ip_port.txt; done; done

👍9🔥2

17 Mar 2026, 12:05 UTC≈1,150 views5 reactionsread 6 August 2026
Photo

🛡 AMSI + ETW bypass via PAGE_GUARD + VEH Написал реализацию на C++ техники из shigshag.com/blog/amsi_page_guard (спасибо ИИ😁) Вместо патча байт функции — ставим PAGE_GUARD на страницу AmsiScanBuffer. CPU кидает STATUS_GUARD_PAGE_VIOLATION до исполнения первой инструкции. VEH перехватывает, пишет AMSI_RESULT_CLEAN в output-параметр, эмулирует return. Trap Flag переприменяет PAGE_GUARD через STATUS_SINGLE_STEP. Расш

❤‍🔥4🔥1

17 Mar 2026, 10:55 UTC≈4,460 views10 reactions1 Starread 6 August 2026
Photo

🛡 AMSI Bypass via Page Guard Patchless-техника обхода AMSI — без перезаписи байтов AmsiScanBuffer и без hardware breakpoints в базовом варианте. Суть: через NtProtectVirtualMemory на страницу памяти, содержащую AmsiScanBuffer, ставится PAGE_GUARD. При доступе к этой странице возникает STATUS_GUARD_PAGE_VIOLATION, который перехватывается через VEH. ​ Если исключение пришло именно на AmsiScanBuffer, хэндлер подменяет

🔥8👏2

9 Feb 2026, 11:36 UTC≈21,700 views14 reactions1 Starread 6 August 2026
Photo

Всем привет! Все сталкивались с ситуациями, когда в корпоративной среде используются в качестве ядра DFS (Distributed File System). Стандартный базовый инструмент для прогулки по корпоративным ресурсам (в обычном пентесте, про redteam ничего не говорю) - smbclient.py в impacket. Соответственно, при попытке перейти в DFS-директорию (когда папка физически располагается на другом файловом ресурсе), получали ошибку STATU

10🔥3👾1

6 Feb 2026, 15:34 UTC≈1,180 views16 reactionsread 6 August 2026
Photo

Всем привет! На одном redteam‑проекте я в бою раздобыл low‑priv учётку в Zabbix. Вспомнил давние изыскания Zer0Way про заббикс. Выяснилось, что на винде агент Zabbix крутится от SYSTEM (в данном конкретно случае), и "посмотреть метрики" внезапно превращается в "а давай-ка аккуратно посмотрим файлики". 📁 Первые попытки делать это через веб‑морду были в духе "суп вилкой": вроде возможно, но удовольствие сомнительное.

6🔥5🤗2👍1👨‍💻1😘1

21 Jan 2026, 09:03 UTC≈1,150 views12 reactions1 Starread 6 August 2026
Photo

Выкатил PR в NetExec: модуль rdpcache — вытаскиваем и разбираем RDP Bitmap Cache с удалённых Windows по SMB. Если коротко: RDP-кэш — это 64×64 тайлы (фрагменты экрана), которые клиент складывает «для оптимизации». Иногда эта оптимизация оптимизирует ещё и расследование: в тайлах остаются куски UI, имена файлов/окон, элементы интерфейса и фрагменты вывода команд. Что делает модуль: - Enum RDP-настроек из реестра: cl

5🔥4👍3

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

Citation-graph rank

Citation-graph rank — 349,455 of 1,160,990entries 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.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Republishes

Channels on the register whose posts this channel has forwarded.

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

Names

Channels on the register whose handles appear in this channel's posts.

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.

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

“Pentester`s Notes” (@hackn0tes), 491 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/hackn0tes.

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.