Telegram RegisterThe public register of Telegram
Telegram profile photo for MalDev | GaK3r

Channel

MalDev | GaK3r

@gak3r

On this record: Growth · Engagement · Reactions · Posts · Cite this entry

734subscribers

+2 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001913733737
TypeChannel
Username@gak3r
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live22 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 22 August 2026
On Telegramt.me/gak3r

Growth

7327347337 August 2026 — 732 subscribers8 August 2026 — 732 subscribers22 August 2026 — 734 subscribers7 August 202622 August 2026
3 measurements spanning 15 days, net +2. 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 732–734 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 09:44734+2
8 Aug 2026, 02:04732no change
7 Aug 2026, 12:36732first reading

Engagement

20 posts held, back to 20 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.

ERR · 30 days
25.4%
avg views ÷ 734 subscribers
Avg views / post
187
2 posts measured
Reaction rate
2.14%
reactions ÷ views · ER floor
Posts in window
2
of 20 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 29 July 2026
Posts held20 (20 November 202529 July 2026)
Views total373
Reactions total8
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:04 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

48 reactions across 16 posts, in 5 distinct kinds. The most used accounts for 33.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤‍🔥1633.3%
🔥1225.0%
👍1020.8%
816.7%
👏24.17%

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 16 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 48reactions 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 20 November 2025 to 29 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.

Recent posts

29 Jul 2026, 21:48 UTC136 views4 reactionsread 8 August 2026
Photo

The Post-Ex Tech Tree: Four Ages of Payload Execution Every generation of post-exploitation tooling was shaped by a different constraint. Lay it out as a tech tree and the pattern is hard to miss. Dark Age — Purpose (1995–2010). Payloads did one thing. A shellcode array was the whole product: position-independent, hand-tuned, disposable. The fork in the road appears here — native code on one side, interpreted on the

🔥3👍1

25 Jul 2026, 14:19 UTC237 views4 reactionsread 8 August 2026

FalkonC2 is Getting Ridiculously Stealthy 🛡️ Flare Research breaks down FalkonC2 — a commercial C2 framework written from scratch in C++/MASM64, built around sub-35 KB memory-only stubs with zero disk footprint and no CRT dependencies. Rotemelli2 targets enterprise EDR/XDR, rotating 17 private C2 servers with full domain burn every 72 hours, falling back across HTTP/HTTPS (MM4 + ChaCha20), DNS tunneling and ICMP beac

🔥4

23 Jul 2026, 13:49 UTC239 views3 reactionsread 8 August 2026

kimi k3 also did a zero-click arbitrary command execution in Telegram Desktop and iOS app (aslr pinned, one gadget away from full rce). https://x.com/fried_rice/status/2080200610985689222

❤‍🔥3

22 Jul 2026, 12:07 UTC253 views3 reactionsread 8 August 2026

CET-Compliant Callstack Spoofing via Thread Pool Enum Callback Trampolining 🛡️ New research shows a CET‑compliant call‑stack spoofing trick that hijacks Windows thread‑pool enum callbacks as syscall trampolines—bypassing EDR stack telemetry while keeping Intel shadow‑stack invariants intact. Dive into the methodology, timeline of syscall evasion, and the underlying mechanics (RtlVirtualUnwind, TEB tricks, etc.) in t

2❤‍🔥1

13 Jul 2026, 23:03 UTC366 views1 reactionsread 8 August 2026

https://github.com/Astharot15/COMLoaderAstharot/ 🕹Subscribe to MalDev | GaK3r

❤‍🔥1

30 Jun 2026, 15:39 UTC476 views3 reactionsread 8 August 2026
Photo

Accelerating EDR Evasion with LLM-Driven Analysis SpecterOps (Adam Chester) shows how a dead-simple LLM harness running in a loop—GPT‑5.5‑Cyber in Codex with Binary Ninja exposed over MCP—reverse engineers Palo Alto’s Cortex XDR to pull out its YARA rules, behavioral detections (DSE/BIOC, CLIPS), and local ML models, auto-generating the Python decryption tooling and evasion test harnesses along the way. No multi-age

❤‍🔥2👏1

17 Jun 2026, 13:00 UTC525 views3 reactionsread 8 August 2026

WindowsSentinel WindowsSentinel is a lightweight C# utility that continuously monitors key Windows system events—such as file, process, and registry changes—and logs them in real‑time for easy auditing and troubleshooting. 🔗 Link 🕹Subscribe to MalDev | GaK3r

👍21

12 Jun 2026, 17:37 UTC542 viewsread 8 August 2026
Photo

Mini Shai-Hulud / Miasma / Hades 🚨 Malware is now weaponizing your own AI scanner against you. A new wave of worms — Mini Shai-Hulud, Miasma, and Hades — ship with a fake “CLASSIFIED BRIEFING” header stuffed with nuclear & bioweapon design text, placed as a non-executing JavaScript comment at the top of _index.js. The point isn’t to run anything — it’s to trip the safety refusals of LLM-based malware triage so the

1 Jun 2026, 14:43 UTC564 views1 reactionsread 8 August 2026
Photo

HijackLibs.net 🚨 DLL Hijacking just got a lot easier to track (and exploit). HijackLibs.net is a curated database mapping vulnerable executables to exploitable DLLs—complete with metadata for defenders to detect attacks and red teamers to plan operations. It covers key techniques like DLL Sideloading, Phantom DLL Hijacking, and Search Order Hijacking—all critical for modern threat hunting and red teaming. 👉 Dive i

❤‍🔥1

31 Mar 2026, 15:05 UTC811 views2 reactionsread 8 August 2026

Claude Code Source Code Leaked Online While publishing the packages, someone at Anthropic made a ✨slight miscalculation✨. An obfuscated cli.js build ended up in the public npm package alongside a full cli.js.map—something that definitely shouldn't have been there. Essentially, anyone who installed or downloaded the package could easily reconstruct the source code using the sourcemap. Naturally, the code spread across

❤‍🔥2

26 Jan 2026, 09:14 UTC≈1,010 views4 reactionsread 8 August 2026
Photo

Hacking Humans: Social Engineering and the Psychology - SpecterOps 🚀 Dive into the mind‑game of cyber‑attacks! In “Hacking Humans: Social Engineering and the Psychology,” John Wotton shows how the real breach starts the moment an employee decides “Who belongs here?” – from OSINT sleuthing to exploiting decision‑making patterns. 📖 https://specterops.io/blog/2026/01/23/hacking-humans-social-engineering-and-the-psycho

❤‍🔥2👏1🔥1

14 Jan 2026, 11:29 UTC≈3,760 views5 reactionsread 8 August 2026
Photo

CVE-2025-54918-POC This GitHub project provides a proof-of-concept (POC) and technical demonstration for CVE-2025-54918, showcasing a security vulnerability in a system or application. It is intended for researchers and developers to understand the exploit mechanism and assess potential risks. 🔗 Link 🕹Subscribe to MalDev | GaK3r

5

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

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

“MalDev | GaK3r” (@gak3r), 734 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/gak3r.

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.