Channel
@bughuntertips
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
3,059subscribers
-2 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001814209494 |
|---|---|
| Type | Channel |
| Username | @bughuntertips |
| Created | Between 1 October 2022 and 30 September 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/bughuntertips |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 02:13 | 3,059 | -1 |
| 7 Aug 2026, 20:45 | 3,060 | -1 |
| 7 Aug 2026, 13:31 | 3,061 | no change |
| 7 Aug 2026, 13:06 | 3,061 | first reading |
18 posts held, back to 30 November 2024 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 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 18 posts for this entry, the most recent from 7 January 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 5 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
167 reactions across 18 posts, in 8 distinct kinds. The most used accounts for 44.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 74 | 44.3% | |
| 👍 | 44 | 26.3% | |
| 🔥 | 34 | 20.4% | |
| ❤🔥 | 6 | 3.59% | |
| 👎 | 3 | 1.80% | |
| 🗿 | 3 | 1.80% | |
| 😱 | 2 | 1.20% | |
| 👌 | 1 | 0.599% |
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 18 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 167reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 18 most recent posts we hold, published 30 November 2024 to 7 January 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.
🔍 SwaggerSpy: Automated OSINT for API Intelligence Looking for exposed secrets in API documentation? Meet SwaggerSpy - an OSINT tool that crawls SwaggerHub for publicly exposed API specs and uses regex patterns to extract: ● Hardcoded API keys and tokens ● Database credentials ● Internal endpoints and architecture details ● Authentication secrets ● AWS keys, JWT tokens, and more Quick Start: python3 swaggerspy.py …
❤8🔥2👍1
🔍 Quick Win: Git Exposure → Secret Hunting 🔥 Step 1: Mass Git Config Hunt nuclei -l alive_http_services.txt -id git-config Step 2: Dump the repository git-dumper https://target.com/ output/ Step 3: Hunt for secrets in dumped code nuclei -u output/ -file Jackpot: - SaaS Keys in config files - DB credentials in .env - Internal API docs with admin endpoints Lesson: Never stop at initial finding - always dig deeper…
❤9
Want to report a scanner finding, but feel like writing it up is too tedious? 😅 Install the ReportLM extension and get Burp AI to do it for you! Prompt example: Generate a bug bounty report, outlining the finding summary, impact, provide full HTTP requests and CVSS scoring #bugbountytips
🔥3❤2
If you need to generate a target-specific wordlist, make sure to check out GAP extension. It will scan for sus parameters and generate you a complete wordlist with one click of a button. #bugbountytips
❤3
Cloudflare has recently started blocking proxy tools such as Burp Suite by detecting their unique TLS and request fingerprints. If you encounter this issue, install the "Bypass Bot Detection" extension from the BApp Store. It spoofs Burp’s TLS fingerprint to resemble normal browser traffic and bypass the block. https://github.com/PortSwigger/bypass-bot-detection #bugbountytips
🔥10👎3👍1
If you found a package.json file in the wild, you might find some internal packages vulnerable to a dependency confusion attack 👀 Check for it quicker using this cool new tool by JSMon: https://app.jsmon.sh/tools/npm-validator/ #bugbountytips
👍19❤3😱2🔥1
Found an XSS but got blocked by the CSP? https://cspbypass.com has a compiled list of ways to bypass the Content-Security Policy. Check out the video. #bugbountytips
❤19👍2
🎯 CSP Takeover Hunting Content-Security-Policy (CSP) whitelists trusted hosts for scripts/resources — but if a whitelisted domain is vulnerable to subdomain takeover (expired DNS, dangling CNAME, abandoned cloud service), an attacker can host malicious assets and bypass CSP. How to find them: Use cspgrabber - to extract domains/subdomains from CSP headers across your targets, then feed results to Nuclei’s subdomai…
🔥3🗿3❤2
Not many know this: nuclei's param fuzzing skips a parameter after the first 10 payloads that return nothing. So if the initial 10 tries don't trigger anything, that parameter gets ignored and you might miss interesting cases. How to fix it: use -fuzz-param-frequency. It controls how many "uninteresting" payloads are allowed before nuclei skips a parameter (default is 10). nuclei -h | grep frequency ... -fuzz-para…
❤4👍1
12 useful firefox extensions for bugbounty 💵 1. Trufflehog - Detecting hidden API keys, tokens and secrets on websites. 2. Wappalyzer - Identify technologies on websites. 3. DotGit - An extension to check if .git is exposed in visited websites. 4. FindSomething - Find interesting things in the webpage's source code or JavaScript. 5. Fake Filler - A form filler that fills all form inputs (textboxes, textareas, ra…
🔥3❤1👍1
TLS-Based Recon for Attack Surface Here's a fast and effective recon flow to find and scan hidden assets using TLS certificate metadata and Shodan dorking via Nuclei’s built-in Uncover engine. Step 1: Find subdomains with subfinder and use tlsx to extract TLS certificate metadata: subfinder -d tesla.com | tlsx -nc -silent -so | awk '{for(i=2; i<=NF; i++) printf "%s ", $i; print ""}'| tr -d '[],' | sort -uf 📌 This g…
❤3👍1🔥1
Nuclei AI Prompts enables security researchers to quickly generate Nuclei templates using AI. Instead of manually writing YAML templates for vulnerabilities, you simply provide a description, and a fully structured template ready for use with Nuclei is generated automatically. To get started with Nuclei AI Prompts, first obtain an API token from ProjectDiscovery. Then, run Nuclei with the -auth flag and add your tok…
❤🔥6
Showing the 12 most recent of 18 posts we hold for @bughuntertips. 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 — 1,122,436 of 1,169,250entries 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.
Named by 1 registered channel — 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.
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.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“#bugbountytips” (@bughuntertips), 3,059 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/bughuntertips.
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.