Offensive VBA https://github.com/X-C3LL/congresos-slides/blob/master/Offensive%20VBA.pdf
Signed khaled

Channel
@hacker_trick
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
2,862subscribers
+6 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001438526658 |
|---|---|
| Type | Channel |
| Username | @hacker_trick |
| Created | Between 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/hacker_trick |
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 15 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Oct 2026, 09:00 | 2,862 | -1 |
| 5 Oct 2026, 01:58 | 2,863 | +9 |
| 25 Sept 2026, 19:56 | 2,854 | -2 |
| 16 Sept 2026, 18:16 | 2,856 | -1 |
| 9 Sept 2026, 00:21 | 2,857 | +4 |
| 3 Sept 2026, 19:37 | 2,853 | +3 |
| 31 Aug 2026, 20:56 | 2,850 | -3 |
| 28 Aug 2026, 12:48 | 2,853 | +2 |
| 25 Aug 2026, 11:23 | 2,851 | +1 |
| 22 Aug 2026, 01:34 | 2,850 | +2 |
| 18 Aug 2026, 18:17 | 2,848 | +2 |
| 15 Aug 2026, 17:04 | 2,846 | -5 |
| 12 Aug 2026, 02:32 | 2,851 | -5 |
| 9 Aug 2026, 13:01 | 2,856 | +2 |
| 6 Aug 2026, 05:50 | 2,854 | -2 |
| 6 Aug 2026, 05:05 | 2,856 | no change |
| 5 Aug 2026, 22:05 | 2,856 | first reading |
20 posts held, back to 16 September 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 3 April 2025. An engagement rate over an empty window would be a number about nothing.
Offensive VBA https://github.com/X-C3LL/congresos-slides/blob/master/Offensive%20VBA.pdf
Signed khaled
400k Linux servers compromised for cryptotheft and financial gain https://www.welivesecurity.com/en/eset-research/ebury-alive-unseen-400k-linux-servers-compromised-cryptotheft-financial-gain
Signed khaled
DodgeBox: A deep dive into the updated arsenal of APT41 | Part 1 https://www.zscaler.com/blogs/security-research/dodgebox-deep-dive-updated-arsenal-apt41-part-1
Signed khaled
user-kernel-syscall-hook: Combining Kernel and User-Mode Hooks for Enhanced System Monitoring https://github.com/carlos-al/user-kernel-syscall-hook
Signed khaled
Channel name was changed to «Real profit»
Bypass-Four03: is a powerful bash tool designed to help testers bypass HTTP 403 forbidden errors through various path and header manipulation techniques. It also includes fuzzing for HTTP methods and protocol versions, making it a versatile addition to any web security researcher's toolkit https://github.com/nazmul-ethi/Bypass-Four03
PPLrevenant: This is a proof-of-concept that shows how a technique such as Bring Your Own Vulnerable DLL (BYODLL) could be used to bypass LSA Protection, or more generally execute arbitrary code within Protected Processes on Windows https://github.com/itm4n/PPLrevenant
Segugio: allows the execution and tracking of critical steps in the malware detonation process, from clicking on the first stage to extracting the malware's final stage configuration https://github.com/reecdeep/segugio
Generate AES128 and AES256 Kerberos keys from a given username, password, and realm https://github.com/seriotonctf/kerberos_aes_key
SubOwner: A Simple tool check for subdomain takeovers https://github.com/ifconfig-me/subowner
Windows App LSASS Dump - Proof of Concept https://github.com/rweijnen/createdump
Extracting Credentials From Windows Logs https://practicalsecurityanalytics.com/extracting-credentials-from-windows-logs
Showing the 12 most recent of 20 posts we hold for @hacker_trick. 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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“Real profit” (@hacker_trick), 2,862 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/hacker_trick.
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.