Is this a thing now ? https://redd.it/1vhafa2 @r_bugbounty

Channel
R_bugbounty
@r_bugbounty
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
137subscribers
+5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001465971699 |
|---|---|
| Type | Channel |
| Username | @r_bugbounty |
| Created | Between 1 April 2019 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/r_bugbounty |
Topic
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 26 September 2026 and assigned it the closest of 31 fixed categories, at 58% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 20:38 | 137 | +1 |
| 2 Oct 2026, 08:16 | 136 | +1 |
| 8 Sept 2026, 03:35 | 135 | +2 |
| 30 Aug 2026, 00:35 | 133 | -1 |
| 14 Aug 2026, 20:18 | 134 | +2 |
| 9 Aug 2026, 00:45 | 132 | no change |
| 6 Aug 2026, 16:23 | 132 | first reading |
Engagement
20 posts held, back to 31 July 2026 — 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Weekly Beginner / Newbie Q&A New to bug bounty? Ask about roadmaps, resources, certifications, getting started, or any beginner-level questions here! Recommendations for Posting: Be Specific: Clearly state your question or what you need help with (e.g., learning path advice, resource recommendations, certification insights). Keep It Concise: Ask focused questions to get the most relevant answers (less is more). …
Slopped Finally, it happened: the day before yesterday, I got my first invite to a program that was so obviously vibecoded that I found three potential highs and some smaller stuff within just two evenings. So far, I’m actually enjoying the AI wave quite a bit. https://redd.it/1vgfago @r_bugbounty
Does DHS VDP offer recognition or not? I read in the guidelines (bugcrowd) that DHS offers recognition to those who report valid vulnerabilities. But I managed to report one P1 which was triaged- resolved in a period of 3 days, 10 days have passed and the customer (dhs) did not even answer me about what recognitions they offered, could someone solve the doubt if this program offers recognitions and how should I requ…
How to Payout bounty on bugcrowd Hi Everyone, i'm a reseacher from Uruguay and i recently found my first paid bounty on the bugcrowd plataform. And here is the problem; I Have added the w8-en form and fullfilled it with all my data, but i have been waiting for bugcrowd to accept it to receive my bounty payout. is it common in this plataform? What i should do? I also contacted the Bugcrowd support, and they sa…
Duplicate Dell P2 finding hi recently i found a P2 rated bug in Dell’s application system, but it was marked as a duplicate, ive had a few other findings end up the same way. So my question is has anyone here actually been paid through Bugcrowd for a legitimate finding? im starting to wonder if the system is rigged, or if ive just been unlucky https://redd.it/1vfuslt @r_bugbounty
Critical finding in crypto protocol Ive found a critical finding on a crypto protocole that put $3.5M a high risk. Ive run a poc and everything works. But theproblem is the protocol doesn’t have a bug bounty on any platforms I’ve tried to contact them tru email but no answer. What should I do ? https://redd.it/1vfi6t3 @r_bugbounty
An URL-unencoded GET-based XSS attack can be reflected. Hi. I discovered an XSS vulnerability; accessing the link directly doesn't trigger a popup, but using Burp Suite does. The browser automatically encodes the closing character `>` (preventing the popup), so I have to use tools like Burp or cURL to send the unencoded `>`. I managed to trigger the popup by routing traffic through my own server, but most of the …
Rant: Bug Bounty is dead (AI and corporate bad faith destroyed the ecosystem) Hey everyone. I mostly just need to vent because this whole situation has become unbearable. For context, I’m not a beginner getting mad because a reflected XSS was marked as a duplicate. I’ve worked as a pentester, have been doing bug bounty for over five years, and have earned more than $150,000 from reporting vulnerabilities. I know h…
Weekly Collaboration / Mentorship Post Looking to team up or find a mentor in bug bounty? Recommendations: Share a brief intro about yourself (e.g., your skills, experience in IT, cybersecurity, or bug bounty). Specify what you're seeking (e.g., collaboration, mentorship, specific topics like web app security or network pentesting). Mention your preferred frequency (e.g., weekly chats, one-off project) and skil…
Alternative for Claude Code? In short - claude runs out of tokens super fast, but is the best and hardly ever refuses cybersecurity prompts (verified profile). I tried using codex but that even refuses active recon prompts, antigravity refuses everything. Kimi is still waitlisted so haven't tried. Is there any other alternative model that doesn't refuse cybersecurity prompts and is not run locally? Locally I'm think…
How do you handle HackerOne findings that require Enterprise features to validate? I’m testing an app on HackerOne and found what I’m pretty sure is a valid vulnerability that could lead to a zero-click account takeover through the way the app handles email addresses. To build a proper PoC, I need Okta SSO, which is only available on the Enterprise plan. I couldn’t find any contact information for the security team…
Showing the 12 most recent of 20 posts we hold for @r_bugbounty. 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.
Mentions
Named by 8 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.
Named by
Channels on the register whose posts name this channel's handle.
@IngressPrimeFeedback · 321 postOctober Strike
@OctoberStrike · 71 postr/badcode
@r_badcode · 391 postr/Furrypasta
@r_furrypasta · 301 postr/GharKeKalesh
@r_gharkekalesh · 711 postI'm going to hell for this
@r_imgoingtohellforthis · 1251 post@r_invites
@r_invites · 1861 postRussianIsSoHard
@RussianIsSoHard · 61 post
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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“R_bugbounty” (@r_bugbounty), 137 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/r_bugbounty.
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.