11 measurements spanning 31 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 1,843–1,861 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
7 Sept 2026, 21:20
1,857
+1
2 Sept 2026, 15:59
1,856
+2
30 Aug 2026, 05:36
1,854
-1
27 Aug 2026, 05:02
1,855
-4
24 Aug 2026, 06:12
1,859
+4
20 Aug 2026, 17:54
1,855
+2
17 Aug 2026, 10:26
1,853
+6
14 Aug 2026, 04:19
1,847
+2
10 Aug 2026, 23:21
1,845
-3
7 Aug 2026, 22:52
1,848
no change
7 Aug 2026, 11:33
1,848
first reading
Engagement
20 posts held, back to 2 December 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pages 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 13 January 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
190 reactions across 20 posts, in 4 distinct kinds. The most used accounts for 55.8% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
106
55.8%
🔥
47
24.7%
👍
36
18.9%
😁
1
0.526%
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 20 of the 20 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 190 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 2 December 2024 to 13 January 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
22
across the posts below
Posts paid on
7
of 20 we hold a reading for · 35%
Most on one post
11
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @road_to_oscp. 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 20 most recent posts we hold for this entry, published 2 December 2024 to 13 January 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.
#network #nmap #nse
[ Nmap Scripting Engine (NSE) - useful scripts collection ]
The Nmap Scripting Engine (NSE) is one of Nmap's most powerful and flexible features. It allows users to write (and share) simple scripts (using the Lua programming language ) to automate a wide variety of networking tasks.
We collected some of useful (and mostly unknown or not popular) scripts in one post (that will be regularly updat…
#mobile #frida
[ Advanced Frida Series ]
📱 Ready to level up your Mobile Reversing & Dynamic Instrumentation game? Most Frida tutorials cover the basics. 8ksec.io built this Frida series for advanced instrumentation against complex iOS and Android targets.
🔎 Topics include:
🔹 Hooking Objective-C and Swift methods
🔹 Extracting secrets from encrypted iOS databases
🔹 Tracing Signal and Telegram message handling
🔹 Ana…
#responder #internal
[ Responder 3.2.0.0 ]
Responder 3.2.0.0 is out!
All new year updates +
- IMAP and SMTP StartTLS
- IMAPS TLS server on port 993
- DHCPv6 poisoning (pure python) using _dirkjan
mitm6 attacks
- Kerberos, DNS server updates
- Etc.
https://github.com/lgandx/Responder
[ Conditional Access bypasses ]
All Conditional Access bypasses in a single blog post. It contains not only the documented bypasses, but also the results of new research.
https://cloudbrothers.info/en/conditional-access-bypasses
#proxmox
[ Living off the Hypervisor - LOLPROX ]
Curated catalog of native Proxmox VE binaries and techniques that adversaries can abuse for post-exploitation operations.
Proxmox is at its core just a Debian image with some hypervisor tooling but the hyper visor tooling is what makes it unique from an attacker perspective.
https://lolprox.yxz.red
Blogpost: https://blog.zsec.uk/lolprox
LOLPROX - Through a Defend…
[ Living Off the Land: Windows Post-Exploitation Without Tools ]
Blog about post-exploitation using only built-in, signed Microsoft tools (PowerShell, WMI, certutil, bitsadmin, and more), without uploading any custom binaries or dropping suspicious artifacts.
https://xbz0n.sh/blog/living-off-the-land-windows
(note from admin: don't forget that PS/WMIC and other things that are described in this article will also b…
[ Cobalt Strike 4.12: Fix Up, Look Sharp! ]
Cobalt Strike 4.12 is LIVE, complete with a new look for the GUI! Additionally:
- A REST API
- User Defined Command and Control (UDC2)
- New process injection options
- New UAC bypasses
- and more!
Check out the release blog for details.
https://www.cobaltstrike.com/blog/cobalt-strike-412-fix-up-look-sharp
#ssh #windows
[ Windows' Built-in OpenSSH for Offensive Security ]
Windows includes OpenSSH by default - ssh.exe. This means all those wonderful tricks we used as washed-up *nix sysadmins, we can now revisit as Offensive Security Consultants! This article shows how Windows’ OpenSSH can be used as a network proxy implant, deployed as a “remote-access trojan” for lower privileged users, and as a data exfiltration too…
#exec #lateral
[ GoExec - Remote Execution Multitool ]
GoExec is a new take on some of the methods used to gain remote execution on Windows devices. GoExec implements a number of largely unrealized execution methods and provides significant OPSEC improvements overall.
https://github.com/FalconOpsLLC/goexec
P.S. From here on, this channel is now live again. Expect more posts soon.
❤8🔥6
Showing the 12 most recent of 20 posts we hold for @road_to_oscp. 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
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.
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
@road_to_oscp 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.
@hybgl named in 1 post, 8 August 2026 – 8 August 2026
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 7 September 2026 — this
entry's latest reading, not the date you are reading this.
“road to OSCP” (@road_to_oscp), 1,857 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/road_to_oscp.
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.
