26 Feb 2026, 17:48 UTC≈3,270 viewsread 25 August 2026
When Audits Fail Part 2: From Pre-Auth SSRF to RCE in TRUfusion Enterprise https://www.rcesecurity.com/2026/02/when-audits-fail-from-pre-auth-ssrf-to-rce-in-trufusion-enterprise/
Channel
BUG BOUNTY TOOLS & Courses
@Hunting_do_do
On this record: Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
3,181subscribers
+67 since we began measuring on 25 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001102894609 |
|---|---|
| Type | Channel |
| Username | @Hunting_do_do |
| Created | Between 1 February 2017 and 31 October 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 25 August 2026 |
| Last confirmed live | 10 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 10 September 2026 |
| On Telegram | t.me/Hunting_do_do |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Sept 2026, 09:16 | 3,181 | +23 |
| 5 Sept 2026, 01:00 | 3,158 | +11 |
| 1 Sept 2026, 18:04 | 3,147 | +20 |
| 29 Aug 2026, 08:54 | 3,127 | +11 |
| 26 Aug 2026, 09:14 | 3,116 | +2 |
| 25 Aug 2026, 17:45 | 3,114 | no change |
| 25 Aug 2026, 17:30 | 3,114 | first reading |
Engagement
20 posts held, back to 11 March 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 26 February 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
26 Feb 2026, 17:48 UTC≈2,740 viewsread 25 August 2026
RCE in Google's AI code editor Antigravity - $10000 Bounty https://www.hacktron.ai/blog/hacking-google-antigravity
26 Feb 2026, 17:48 UTC≈3,550 viewsread 25 August 2026
GraphQL Pentesting for Bug Bounty Hunters: From Endpoint Discovery to High-Impact Exploits…! https://medium.com/@mpjani294/graphql-pentesting-for-bug-bounty-hunters-from-endpoint-discovery-to-high-impact-exploits-821f64a953b5
22 Sept 2025, 18:17 UTC≈4,700 viewsread 25 August 2026
Electron Research in Desktop apps [Part 1] https://blog.securelayer7.net/electron-app-security-risks/
22 Sept 2025, 18:17 UTC≈3,020 viewsread 25 August 2026
Java 23: Embrace the new era of code comments https://www.sonarsource.com/blog/java-23-embrace-the-new-era-of-code-comments/
22 Sept 2025, 18:17 UTC≈2,730 viewsread 25 August 2026
Intigriti Bug Bytes #228 - September 2025 🚀 https://www.intigriti.com/researchers/blog/bug-bytes/intigriti-bug-bytes-228-september-2025
22 Sept 2025, 18:17 UTC≈2,650 viewsread 25 August 2026
What's the top bug in your language? Find out in The State of Code: Languages report https://www.sonarsource.com/blog/the-state-of-code-languages/
22 Sept 2025, 18:17 UTC≈3,820 viewsread 25 August 2026
Cyber Resilience Act: Navigating speed and security with AI-coding https://www.sonarsource.com/blog/cra-navigating-speed-and-security-with-ai-coding/
23 Apr 2025, 07:03 UTC≈2,250 viewsread 25 August 2026
The No BS Bug Bounty & Web Hacking Roadmap https://www.youtube.com/watch?v=AMQq06WUMVk
23 Apr 2025, 07:03 UTC≈2,600 viewsread 25 August 2026
Jumping the line: How MCP servers can attack you before you ever use them https://blog.trailofbits.com/2025/04/21/jumping-the-line-how-mcp-servers-can-attack-you-before-you-ever-use-them/?hss_channel=lcp-912286
23 Apr 2025, 07:03 UTC≈1,890 viewsread 25 August 2026
Escalating Impact: Full Account Takeover in Microsoft via XSS in Login Flow https://melotover.medium.com/escalating-impact-full-account-takeover-in-microsoft-via-xss-in-login-flow-f160fa79b008
23 Apr 2025, 07:03 UTC≈1,720 viewsread 25 August 2026
Intercepting HTTPS Communication in Flutter: Going Full Hardcore Mode with Frida https://sensepost.com/blog/2025/intercepting-https-communication-in-flutter-going-full-hardcore-mode-with-frida/
Showing the 12 most recent of 20 posts we hold for @Hunting_do_do. 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.
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 Bug Bounty Hunter
@thebugbountyhunter · 50,455
Telegram ranks this channel #34 of 60 here — alongside 59 others — read 25 August 2026
@thebugbountyhunter · 50,455
Telegram ranks this channel #34 of 60 here — alongside 59 others — read 25 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 10 September 2026 — this entry's latest reading, not the date you are reading this.
“BUG BOUNTY TOOLS & Courses” (@Hunting_do_do), 3,181 subscribers as measured 10 September 2026. Telegram Register, tgregister.com/channel/Hunting_do_do.
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.