Telegram RegisterThe public register of Telegram
Telegram profile photo for Pentester

Channel

Pentester

@news4hack

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

3,106subscribers

+41 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001235276739
TypeChannel
Username@news4hack
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live5 September 2026
Measurements held12
Confirmed unchanged1 time, most recently 5 September 2026
On Telegramt.me/news4hack

Growth

3,0623,1063,0847 August 2026 — 3,065 subscribers7 August 2026 — 3,065 subscribers7 August 2026 — 3,064 subscribers10 August 2026 — 3,062 subscribers13 August 2026 — 3,065 subscribers16 August 2026 — 3,070 subscribers19 August 2026 — 3,075 subscribers23 August 2026 — 3,072 subscribers25 August 2026 — 3,084 subscribers29 August 2026 — 3,094 subscribers1 September 2026 — 3,102 subscribers5 September 2026 — 3,106 subscribers7 August 20265 September 2026
12 measurements spanning 29 days, net +41. 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 3,055–3,113 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Sept 2026, 02:363,106+4
1 Sept 2026, 01:383,102+8
29 Aug 2026, 04:383,094+10
25 Aug 2026, 21:093,084+12
23 Aug 2026, 03:153,072-3
19 Aug 2026, 15:523,075+5
16 Aug 2026, 21:233,070+5
13 Aug 2026, 18:163,065+3
10 Aug 2026, 07:303,062-2
7 Aug 2026, 17:503,064-1
7 Aug 2026, 12:013,065no change
7 Aug 2026, 11:553,065first reading

Engagement

20 posts held, back to 2 January 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 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 22 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

90 reactions across 18 posts, in 6 distinct kinds. The most used accounts for 47.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4347.8%
👍2224.4%
1921.1%
🆒33.33%
🤣22.22%
🥰11.11%

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 18 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 90 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 January 2026 to 22 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

22 Jul 2026, 12:41 UTC515 views5 reactionsread 8 August 2026

Offensive AI Agents Landscape: Projects, Models, Skills, MCP Servers, Papers, Benchmarks & Commercial Solutions https://github.com/Yeti-791/Awesome-Offensive-AI-Agentic-Landscape

🔥32

20 Jul 2026, 19:55 UTC707 views2 reactionsread 8 August 2026

A labeled reverse-engineering dataset over 4,598 crackmes from crackmes.one, built for benchmarking automated RE (AI agents + decompilers) https://github.com/crackmesone/crackmes-re-dataset

1👍1

18 Jul 2026, 14:21 UTC758 views1 reactionsread 8 August 2026

How to use Claude Code for Bug Bounty: find fast, validate manually https://www.yeswehack.com/learn-bug-bounty/llm-series-claude

🥰1

8 Jul 2026, 05:06 UTC≈1,210 views6 reactionsread 8 August 2026

T3MP3ST A multi-agent offensive-security framework, built to turn the AI coding agent you already run into a zero-day hunter. Point it at an authorized target and the kill chain runs itself: recon → exploit → report, from a browser War Room or the CLI, driven by the agent you're already signed into — Claude Code, Codex, Hermes — or a model you run fully offline (Ollama, LM Studio, vLLM). No new API keys, no cloud ten

🔥6

12 May 2026, 05:01 UTC≈1,740 views2 reactionsread 8 August 2026
Photo

Dirty Frag: Universal Linux LPE Obtain root privileges on major Linux distributions by chaining the xfrm-ESP Page-Cache Write vulnerability and the RxRPC Page-Cache Writevulnerability. Dirty Frag is a case that extends the bug class to which Dirty Pipe and Copy Fail belong. Because it is a deterministic logic bug that does not depend on a timing window, no race condition is required, the kernel does not panic when t

🔥2

4 May 2026, 12:36 UTC≈1,620 viewsread 8 August 2026

Release v3.8.0 · projectdiscovery/nuclei https://github.com/projectdiscovery/nuclei/releases/tag/v3.8.0

23 Mar 2026, 20:11 UTC≈2,240 views7 reactionsread 8 August 2026

CVE-2026-24291: Windows LPE (RegPwn) Exploit: https://github.com/mdsecactivebreach/RegPwn Blog: https://www.mdsec.co.uk/2026/03/rip-regpwn/ BOF: https://github.com/Flangvik/RegPwnBOF Tested versions: Windows 11 25h2 Windows 11 24h2 Windows 10 21h2 Windows Servers 2016/2019/2022 Patched: Mar 10, 2026

👍3🔥31

23 Mar 2026, 20:09 UTC≈1,740 views4 reactionsread 8 August 2026
Photo

CVE-2025-71257 and CVE-2025-71260 BMC FootPrints Pre-Authenticated Remote Code Execution Chain • Bypass authentication with CVE-2025-71257. • If it is successful, it tries to verify the CVE-2025-71260 RCE by writing a ranomized .jsp file to the tomcat servers webroot. This .jsp file just enumerates system information. Blog: https://labs.watchtowr.com/thanks-itsms-threat-actors-have-never-been-so-organized-bmc

🔥3👍1

17 Mar 2026, 08:56 UTC≈1,610 views8 reactionsread 8 August 2026
Photo

VMkatz Without VMkatz, the traditional workflow looks like this: exfiltrate the entire VM disk or memory snapshot, mount it locally, install a full Windows analysis stack, load the snapshot into a debugger or use mimikatz on a booted copy, and manually piece together credentials from each VM - one at a time. Multiply that by a dozen VMs on the cluster and you are looking at days of bandwidth, tooling, and post-proce

🔥42👍2

23 Feb 2026, 07:57 UTC≈1,750 views7 reactionsread 8 August 2026
Photo

Gaining Initial Access and Outsmarting SmartScreen .zip email attachment that includes a VHDX (Hard Disk Image File) + Mark of the Web and SmartScreen bypass using Trusted Executable Reputation and DLL Sideloading. Tools: https://github.com/g3tsyst3m/CodefromBlog/tree/main/2026-2-21-Initial%20Access%20and%20Outsmarting%20SmartScreen

👍3🔥21🤣1

21 Feb 2026, 11:51 UTC≈1,590 views7 reactionsread 8 August 2026
Photo

The Mimikatz Missing Manual My goal was to create the "Missing Manual" — the documentation that explains not just the commands, but the why and the how of the Windows protocols being manipulated. Parts: • Foundations: Setting up your environment and the basic syntax. • System Internals: How Windows handles tokens, processes, and services. • LSASS & Credentials: The heart of Mimikatz—extracting secrets from

🔥32👍2

24 Jan 2026, 20:25 UTC≈1,920 views11 reactionsread 8 August 2026
Photo

2026-24061: Telnetd RCE as Root This flaw allows an attacker to establish a Telnet session without providing valid credentials, granting unauthorized access to the target system. The vulnerability exists all the way up to version 2.7-2 of the GNU telnetd service. Exploit: https://github.com/SafeBreach-Labs/CVE-2026-24061 Query: ZoomEye: app="GNU Inetutils telnetd" Shodan: product:"telnetd" @news4hack

🔥43🆒3🤣1

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

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.

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

“Pentester” (@news4hack), 3,106 subscribers as measured 5 September 2026. Telegram Register, tgregister.com/channel/news4hack.

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.