This channel’s posts match, word for word or near enough, posts on 2 other registered channels, found by comparing text fingerprints across every channel on the register. That matching has been checked by hand against the live Telegram pages and found reliable — 0 wrong of 45 pairs re-read.
Which channel, if either, published first is deliberately not shown. The same hand-check found that reading wrong 18 of 45 times — 60%, no better than a coin flip — because it depends on how deep our own crawl happened to reach into each channel’s history, not on when the content was actually first posted. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Word-for-word matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
16 measurements spanning 17 days, net +348. 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 15,728–16,180 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
23 Aug 2026, 04:57
16,128
+24
21 Aug 2026, 17:46
16,104
+22
20 Aug 2026, 12:26
16,082
+30
19 Aug 2026, 09:47
16,052
+16
18 Aug 2026, 12:53
16,036
+32
17 Aug 2026, 11:14
16,004
+35
15 Aug 2026, 19:04
15,969
+35
14 Aug 2026, 05:27
15,934
+26
12 Aug 2026, 19:25
15,908
+50
11 Aug 2026, 16:26
15,858
+23
10 Aug 2026, 13:36
15,835
+16
9 Aug 2026, 12:36
15,819
+20
8 Aug 2026, 11:25
15,799
+11
7 Aug 2026, 08:54
15,788
+8
6 Aug 2026, 11:50
15,780
no change
6 Aug 2026, 08:21
15,780
first reading
Engagement
22 posts held, back to 25 August 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 34 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
31.5%
avg views ÷ 16,128 subscribers
Avg views / post
5,080
3 posts measured
Reaction rate
0.538%
reactions ÷ views · ER floor
Posts in window
3
of 22 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 17 August 2026
Posts held
22 (25 August 2025 – 17 August 2026)
Views total
15,250
Reactions total
82
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
23 Aug 2026, 12:25 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.
What this channel posts
Photos
564
Videos
28
Links
908
Lifetime counters from Telegram’s own channel header, read 23 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Reaction mix
520 reactions across 21 posts, in 11 distinct kinds. The most used accounts for 48.7% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
253
48.7%
❤
109
21.0%
👍
92
17.7%
❤🔥
26
5.00%
😁
15
2.88%
🤔
11
2.12%
👏
5
0.962%
🤯
4
0.769%
👎
3
0.577%
🎉
1
0.192%
😱
1
0.192%
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 22 of the 22 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 544reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 25 August 2025 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.
Telegram Stars
Stars received
10
across the posts below
Posts paid on
8
of 22 we hold a reading for · 36%
Most on one post
2
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @APT_Notes. 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 22 most recent posts we hold for this entry, published 25 August 2025 to 17 August 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
18.2%
4 of 22 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
12,400
over 4 measured posts
Median views · rest
10,700
over 18 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
2SDnjcU32Jn
1
1 July 2026
1 July 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 22 most recent posts we hold, published 25 August 2025 to 17 August 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.
🔒 Citrix NetScaler Pre-Auth RCE (CVE-2026-8452)
Unauthenticated heap overflow in SAML signature canonicalization. An oversized PrefixList inside the <ds:SignedInfo> InclusiveNamespaces element overflows a fixed-size buffer, corrupting adjacent nsb chunk metadata. This yields a write-what-where primitive (controlled memcpy src/dst), allowing overwrite of tx_pkt_complete_fptr and jump to attacker shellcode on the exec…
ResetNightmare
ResetNightmare (CVE-2026-27912) is a validation flaw in the Kerberos Change Password protocol that allows for resetting the password of any target user/computer account, without knowing the current one. The attack requires an unpatched domain controller, and the ability to write a userPrincipalName (UPN) on any account you control. Alternatively, the vulnerability can also be abused by an attacker hav…
🔒 Certighost (CVE-2026-54121) — AD CS Domain Controller Impersonation
Low-privileged domain user can impersonate a Domain Controller via an AD CS enrollment chase fallback. By supplying cdc (Client DC) and rmd (Remote Domain) request attributes, an attacker forces the Enterprise CA to query an attacker-controlled host over SMB and LDAP.
The CA then blindly trusts the returned directory objects (objectSid + dNSHostN…
💉 P³ — Shellcode Loader: Process Parameter Poisoning
This loader implements a code injection technique that leverages the Windows Process Parameters structure (PEB) as a staging and execution location for remote shellcode injection.
By passing payload data implicitly through standard parameters like CommandLine, Environment, or ShellInfo, it bypasses EDR detection because it doesn't touch heavily monitored APIs lik…
GhostLock — CVE-2026-43499
This is a Linux kernel vulnerability found by VEGA that exists in every major distribution since 2011. Triggering the bug does not require any special kernel config or privilege. By turning it into a 97% stable privilege escalation and container escape, Google has rewarded us $92,337 in kernelCTF. This writeup covers the technical details of the exploit.
🔗 Research:
https://nebusec.ai/res…
🛠 Всем привет.
Выкатил небольшой “living off the land” для кред с не самым креативным названием LOLCreds - Living Off the Land Credentials.
Это каталог публичных кред по умолчанию и мест где они обитают.
Что-то для ответа на вопросы какие пароли идут статичными из коробки, генерятся на этапе установки, а какие задает сам пользователь, где в каких конфигах и переменных окружения они обычно хранятся и тому подобное.
…
Pentest award 2026 ждет твою заявку!
Меньше двух недель остается чтобы отправить заявки на «хакерский оскар». Не упускайте шанс получить признание отрасли, классные призы и просто провести время на закрытой церемонии награждения вместе с лучшими представителями отрасли. Вручении состоится в зале на «Красном Октябре» с панорамной террасой с видом на набережную и город.
Чтобы подать заявку достаточно обезличенного ра…
DirtyClone — CVE-2026-43503
A Linux kernel local privilege escalation and page-cache write. DirtyClone is the fourth public member of the DirtyPipe / DirtyFrag family: it forces the kernel to run an in-place ESP (IPsec) decrypt over a file-backed page-cache page the attacker only has read access to, mutating that page in RAM. With the AES-CBC key/IV chosen so the decrypt writes attacker-controlled bytes, /usr/bin/su…
🔑 Onelogon: Taking over Active Directory Accounts via Netlogon
We analyzed Netlogon, bypassed the Zerologon patch, resulting in a full auth bypass. An attacker can leverage this to compromise computer accounts, or even the entire AD. Non-standard config must be present tho
Exploit: https://github.com/rub-softsec/onelogon
https://github.com/Pennyw0rth/NetExec/pull/1291
From: https://x.com/al3x_n3ff/status/206948262…
ssh-keysign-pwn — CVE-2026-46333
A critical race condition flaw in pre-31e62c2ebbfd Linux kernels. Due to a window during process exit where the memory management structure is cleared before file descriptors are closed, an unprivileged user can use pidfd_getfd(2) to steal open file descriptors of privileged processes, enabling unauthorized reading of root-owned files.
🔗 Exploit:
https://github.com/0xdeadbeefnetwork…
🧑🚒 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/
🔥15👍12👏5❤3🤔2
Showing the 12 most recent of 22 posts we hold for @APT_Notes. 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 — 151,988 of 1,584,486entries 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.
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 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.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@APT_Notes named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@codewhisperer84 named in 2 posts, 8 August 2026 – 9 August 2026
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.
The Hacker News @thehackernews · 162,179 Telegram ranks this channel #14 of 58 here — alongside 57 others — read 13 August 2026
Life-Hack - Хакер @haccking · 63,208 Telegram ranks this channel #17 of 85 here — alongside 84 others — read 21 August 2026
infosec @it_secur · 61,174 Telegram ranks this channel #25 of 81 here — alongside 80 others — read 22 August 2026
Cyber Security News @Cyber_Security_Channel · 56,427 Telegram ranks this channel #29 of 71 here — alongside 70 others — read 23 August 2026
Social Engineering @Social_engineering · 125,151 Telegram ranks this channel #30 of 82 here — alongside 81 others — read 13 August 2026
Этичный Хакер @hack_less · 228,029 Telegram ranks this channel #41 of 81 here — alongside 80 others — read 12 August 2026
OSINT mindset @osint_mindset · 64,477 Telegram ranks this channel #62 of 83 here — alongside 82 others — read 21 August 2026
CyberYozh @cyberyozh_official · 62,423 Telegram ranks this channel #70 of 81 here — alongside 80 others — read 21 August 2026
SecurityLab.ru @SecLabNews · 83,697 Telegram ranks this channel #76 of 90 here — alongside 89 others — read 18 August 2026
This channel appears in 9 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 23 August 2026 — this
entry's latest reading, not the date you are reading this.
“APT” (@APT_Notes), 16,128 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/APT_Notes.
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.