Telegram RegisterThe public register of Telegram

Channel

r0 Crew (Channel)

@R0_Crew

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry

8,862subscribers

+14 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001123637250
TypeChannel
Username@R0_Crew
DescriptionSecurity Related Links: - Reverse Engineering; - Malware Research; - Exploit Development; - Pentest; - etc; Join to chat: @r0crew_bot 👈 Forum: https://forum.reverse4you.org Twitter: https://twitter.com/R0_Crew
Created17 May 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/R0_Crew

Growth

8,8488,8628,8556 August 2026 — 8,848 subscribers6 August 2026 — 8,848 subscribers6 August 2026 — 8,850 subscribers9 August 2026 — 8,853 subscribers12 August 2026 — 8,862 subscribers6 August 202612 August 2026
5 measurements spanning 6 days, net +14. 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 8,846–8,864 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 02:528,862+9
9 Aug 2026, 10:078,853+3
6 Aug 2026, 06:328,850+2
6 Aug 2026, 03:008,848no change
6 Aug 2026, 02:278,848first reading

Engagement

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

What this channel posts

Photos
35
Videos
1
Links
1,980

Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Reaction mix

378 reactions across 20 posts, in 16 distinct kinds. The most used accounts for 31.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍11731.0%
🔥10327.2%
8522.5%
102.65%
🥰102.65%
🤣92.38%
👎82.12%
😴82.12%
🤔71.85%
😐61.59%
👏41.06%
🤯41.06%
😁20.529%
😍20.529%
🥱20.529%
🤝10.265%

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 378reactions 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 17 March 2024 to 19 January 2025, 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

19 Jan 2025, 08:50 UTC≈11,400 views23 reactionsread 12 August 2026
Forwarded from @malware_research

New blog on using CLR customizations to improve the OPSEC of your .NET execution harness. This includes a novel AMSI bypass that identified by author in 2023. By taking control of CLR assembly loads, we can load assemblies from memory with no AMSI scan. https://securityintelligence.com/x-force/being-a-good-clr-host-modernizing-offensive-net-tradecraft/ Proof-of-concept for the AMSI bypass and an implementation of a

108👍5

1 Jan 2025, 00:01 UTC≈10,800 views51 reactionsread 12 August 2026
Photo

Happy New Year! May every binary reveal its secrets, every challenge find its solution, and the Year of the Snake bring you stability, inspiration, and success!

👍2119🔥11

15 Nov 2024, 13:37 UTC≈12,900 views22 reactionsread 12 August 2026

Complete list of LPE exploits for Windows (starting from 2023) https://github.com/MzHmO/Exploit-Street #windows #expdev #lpe

13👍3🤯3🥱2🤣1

27 Sept 2024, 07:37 UTC≈12,400 views31 reactionsread 12 August 2026

Attacking UNIX Systems via CUPS, Part I CVE-2024-47176, CVE-2024-47076, CVE-2024-47175, and CVE-2024-47177 have been assigned around these CUPS issues. CVSS 9.9 This remote code execution issue can be exploited across the public Internet via a UDP packet to port 631 without needing any authentication, assuming the CUPS port is open through your router/firewall. LAN attacks are also possible via spoofing zeroconf /

🤣87👍5😐4🔥2🥰2😁2🤯1

26 Sept 2024, 07:37 UTC≈9,490 views15 reactionsread 12 August 2026

0-Click exploit in MediaTek Wi-Fi chipsets affects routers and smartphones / Exploiting (CVE-2024-20017) 4 different ways https://blog.coffinsec.com/0day/2024/08/30/exploiting-CVE-2024-20017-four-different-ways.html #expdev #poc

10👍4🔥1

3 Sept 2024, 10:58 UTC≈12,700 views18 reactionsread 12 August 2026

Native function and Assembly Code Invocation https://research.checkpoint.com/2022/native-function-and-assembly-code-invocation/ #reverse #idapro

🔥11👍4🥰2🤝1

27 Aug 2024, 20:33 UTC≈8,280 views14 reactionsread 12 August 2026

Exploiting the Windows Kernel via Malicious IPv6 Packets (CVE-2024-38063) https://malwaretech.com/2024/08/exploiting-CVE-2024-38063.html #expdev #poc

👍12😍2

26 Aug 2024, 15:13 UTC≈8,590 views14 reactionsread 12 August 2026

POC for trigerring CVE-2024-38063 (RCE in tcpip.sys) https://github.com/ynwarcs/CVE-2024-38063 #expdev #poc

10👍4

23 Aug 2024, 13:59 UTC≈6,910 views5 reactionsread 12 August 2026

C++ Unwind Exception Metadata: a Hidden Reverse Engineering Bonanza https://www.msreverseengineering.com/blog/2024/8/20/c-unwind-metadata-1 #reverse #cpp #type #reconstruction #hints

🔥5

23 Aug 2024, 13:31 UTC≈5,800 views6 reactionsread 12 August 2026

V8 Sandbox escape/bypass/violation and VR collection https://github.com/xv0nfers/V8-sbx-bypass-collection #v8 #sandbox #escape

🔥6

23 Aug 2024, 13:01 UTC≈5,130 views9 reactionsread 12 August 2026

How to Bypass Golang SSL Verification https://www.cyberark.com/resources/threat-research-blog/how-to-bypass-golang-ssl-verification #golang #ssl #bypass #reverse #web #pentest

🤔5👏21🔥1

22 Aug 2024, 10:55 UTC≈5,230 views7 reactionsread 12 August 2026

SGN is a polymorphic binary encoder for offensive security purposes such as generating statically undetecable binary payloads. It uses a additive feedback loop to encode given binary instructions similar to LSFR. This project is the reimplementation of the original Shikata ga nai in golang with many improvements. https://github.com/EgeBalci/sgn #redteam #golang

🔥3👍2🤔2

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

Citation-graph rank

Citation-graph rank — 177,475 of 1,478,351entries 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.

Republishes

Channels on the register whose posts this channel has forwarded.

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 3 registered channels — 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.

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.

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,130
Telegram ranks this channel #49 of 58 here — alongside 57 others — read 13 August 2026

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.

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

“r0 Crew (Channel)” (@R0_Crew), 8,862 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/R0_Crew.

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.