Telegram RegisterThe public register of Telegram
Telegram profile photo for Crowdfense

Channel

Crowdfense

@crowdfense

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

273subscribers

+3 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-1002025161745
TypeChannel
Username@crowdfense
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live27 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/crowdfense

Growth

270273271.57 August 2026 — 270 subscribers8 August 2026 — 270 subscribers27 August 2026 — 273 subscribers7 August 202627 August 2026
3 measurements spanning 20 days, net +3. 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 270–273 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 13:37273+3
8 Aug 2026, 08:49270no change
7 Aug 2026, 13:34270first reading

Engagement

20 posts held, back to 4 June 2024the 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.

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 21 May 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

93 reactions across 19 posts, in 6 distinct kinds. The most used accounts for 49.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4649.5%
👍2324.7%
1819.4%
👏33.23%
🥱22.15%
🥰11.08%

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 19 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 93reactions 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 4 June 2024 to 21 May 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

21 May 2026, 15:56 UTC267 views7 reactionsread 8 August 2026

Technical analysis and exploitation strategy for CVE-2026-40369: a 12-byte kernel increment exploitable both as LPE and SBX. Originally prepared for Pwn2Own Berlin, the bug became public shortly before the contest after CVE assignment. https://voidsec.com/cve-2026-40369-browser-sandbox-escape/

🔥7

12 May 2026, 13:56 UTC365 views3 reactionsread 8 August 2026

Some takeaways from our team on the usage of AI for vulnerability research: https://voidsec.com/ai-vulnerability-research-fuzzer-era/

3

11 Dec 2025, 16:04 UTC605 views7 reactionsread 8 August 2026

No, we don’t only post about vulnerability research… This time, we took a short break from breaking things and decided to build something instead: our local LLM rig. Not because it's “AI hype season,” but because we genuinely enjoy tinkering and thought others might, too. If you're curious about running powerful LLMs locally without selling your kidney for a GPU, here you go: https://www.crowdfense.com/home-made-llm-

👍5🥱2

11 Sept 2025, 16:00 UTC771 views2 reactionsread 8 August 2026

Bidding farewell to one of the last Windows Kernel address leaks, CVE-2025-53136 (KASLR bypass). Sometimes, even patches can open new doors for exploitation. https://www.crowdfense.com/nt-os-kernel-information-disclosure-vulnerability-cve-2025-53136/

2

4 Sept 2025, 18:23 UTC667 views7 reactionsread 8 August 2026

Technical deep-dive into CVE-2025-53149, a heap-based buffer overflow in the Windows Kernel Streaming WOW Thunk Service driver (ksthunk.sys). https://www.crowdfense.com/cve-2025-53149-windows-ksthunk-heap-overflow/

🔥61

10 May 2025, 07:31 UTC794 views3 reactionsread 8 August 2026

🔥 New Windows bounty just dropped on VRH! Looking for a Word or Excel RCE. Join the hunt - vrh.crowdfense.com

👍3

17 Apr 2025, 15:57 UTC855 views5 reactionsread 8 August 2026

🔥 New iOS bounty just dropped on VRH! Looking for an iOS Kernel Privilege Escalation. Join the hunt - vrh.crowdfense.com

👍5

7 Apr 2025, 16:12 UTC886 views1 reactionsread 8 August 2026

🚨 New bounties just dropped! 🚨 We’ve added fresh CVE bounties on the VRH platform. Check them out and start earning rewards for your discoveries: vrh.crowdfense.com

🔥1

30 Jan 2025, 07:29 UTC≈1,060 viewsread 8 August 2026

New Bounty: CCTV & Camera Exploits – Hikvision Focus We are currently expanding our bounty program to include CCTV and camera vulnerabilities, with a special focus on Hikvision devices. We are interested in both: - 0-day vulnerabilities - N-day vulnerabilities (up to six months old) If you have high-impact findings in this space, submit them through our platform for evaluation: https://vrh.crowdfense.com

1 Jan 2025, 12:34 UTC853 views2 reactionsread 8 August 2026

Happy new year researchers, may your 2025 exploits be successful! 🎉🥂🍾 2024 was a productive year, we will continue to improve our VRH platform and reach our goals

👏2

2 Dec 2024, 18:05 UTC866 views1 reactionsread 8 August 2026

We are currently looking for weaponized Android n-days (LPE/RCE), which are not publicly available and affect Android 13/14. Submit your findings today and get the BIG payouts you deserve 💰 https://www.vrh.crowdfense.com/

👍1

Showing the 12 most recent of 20 posts we hold for @crowdfense. 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 27 August 2026 — this entry's latest reading, not the date you are reading this.

“Crowdfense” (@crowdfense), 273 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/crowdfense.

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.