Passive OSINT and evidence archive for huntbug.com - observed fraud indicators on a suspected fake bug-bounty platform (not a legal verdict).
Status: evidence archive · Report date: 2026-11-13 (UTC) · Method: passive OSINT + manual browser inspection
Nature of this repository. This repository records observed indicators and inferences drawn from public information. It is not a legal finding, verdict, or proof of fraud, and it does not assert criminal intent. No exploitation, port scanning, credential use, form submission, or contact with the site or its operator was performed. All site screenshots were taken by a user in their own browser on 2026-11-13. Business and compliance claims are reproduced as the site published them.
Companies named below appear because the site itself lists them as customers/programs. Their presence here is not an allegation against those companies; it is part of the claim under investigation.
HuntBug presents itself as a legitimate crowdsourced bug-bounty platform — "Find the bugs. Earn the bounty. Build the secure web." A combination of live site observation and passive public-records OSINT produced several mutually reinforcing fraud indicators:
| # | Indicator | Observation | Source |
|---|---|---|---|
| 1 | Fabricated "live" payout feed | Identical entry repeated (@sahil_r → parabol · Chained SSRF → RCE · $42,000); six entries on the same second; all nine entries inside a 13-second window; "12,419 hunters online" | Screenshot 01 · live DOM |
| 2 | Fabricated founding timeline | /about: founded 2022 in a Brooklyn apartment — WHOIS creation 2025-05-24 | Screenshot 02 · WHOIS |
| 3 | Contradictory certifications | /why-us: "SOC 2 Type II, ISO 27001" — /compliance: "not SOC 2 certified… no third-party security certification" | Screenshots 03 & 04 |
| 4 | Unauthorized program listings | /open-directory lists Linear, Sentry, Clerk, Warp as live programs | Screenshot 05 |
| 5 | Rapid, templated build | DMARC reports route to [email protected] (Lovable AI-builder default); Brevo transactional-email TXT record | Passive DNS/TXT |
| 6 | No community footprint | No payout proofs, reviews, or threads on Reddit / Trustpilot / X despite "2,900+ hunters" / "$3.8M paid" (complainant-reported, not independently verified) | Passive |
Most likely risk: harvesting of real vulnerabilities from researchers under false triage/payout and safe-harbor promises.
In scope
huntbug.com (home, /about, /why-us, /compliance, /open-directory).Not performed
All lookups were passive (registry, DNS, certificate transparency, web archive). The domain's IP-owner attribution is called out as unverified where applicable.
The homepage shows a terminal-style widget labelled ~/huntbug/feed · live with a rotating list of "real-time" submissions and payouts, a headline counter v3.4 · 12,419 hunters online, and streaming · 24 events/min.
Direct inspection of a single capture shows it is not a plausible real-time feed:
@sahil_r → parabol · "Chained SSRF → RCE in /v3/payments/refund" · $42,000 — at 23:29:36 and 23:29:33.23:29:33, and all nine entries fall inside a 13-second window — implausible for a genuine multi-tenant feed advertising 24 events/minute.Feed rows as rendered at capture time:
| Time | Severity | Hunter | Program | Report | Bounty |
|---|---|---|---|---|---|
| 23:29:36 | CRIT | @sahil_r | parabol | Chained SSRF → RCE in /v3/payments/refund | $42,000 |
| 23:29:33 | CRIT | @sahil_r | parabol | Chained SSRF → RCE in /v3/payments/refund (duplicate) | $42,000 |
| 23:29:33 | HIGH | @p4lerider | honest | Auth bypass via stale JWT on /me/sessions | $7,500 |
| 23:29:33 | MED | @nyx_0xff | orbital | IDOR on /invoices/{id} leaks customer PII | $2,400 |
| 23:29:33 | HIGH | @k.tanaka | TL;DV | Stored XSS in shared workspace title field | $5,000 |
| 23:29:33 | LOW | @routesix | hexpath | Open redirect on /go?u=… (CSRF chained) | $600 |
| 23:29:33 | CRIT | @vexline | insight-hlth | PHI exposure in radiology report endpoint | $28,000 |
| 23:29:33 | MED | @m_eaves | stelvio | Rate-limit bypass on password reset | $1,800 |
| 23:29:33 | HIGH | @dr_glitch | langdock | SQLi (blind) in admin search · err.code=42 | $8,200 |
Pattern: a 13-second window, one exact duplicate, and six rows on the same second. A genuine feed at 24 events/min would not reproduce this.
Why it matters: a fabricated "live" payout stream is the primary social-proof mechanism used to convince researchers the platform pays.
/about tells a specific origin story; public registration records contradict it by more than two years.
Site claim (huntbug.com/about):
"In 2022, three of us got tired of submitting reports into platforms that ghosted us for 90 days… We started HuntBug in a Brooklyn apartment with a single rule: the clock is always visible."
Also: "347 programs… paid out $3.8M… 30 humans across 9 timezones… backed by 40+ angel researchers."
Public record (WHOIS):
| Field | Value |
|---|---|
| Created | 2025-05-24 |
| Updated | 2026-08-08 |
| Expires | 2027-05-24 |
| Registrar | GoDaddy.com, LLC |
| Registrant | Domains By Proxy, LLC (privacy) |
Inference: a domain created in May 2025 cannot have been operating as a company since 2022. This is corroborated (complainant-reported) by the platform's LinkedIn (founded 2025, 2–10 employees) and by announcements that researcher batches only began in mid-2026.
The marketing page claims the platform is certified; the platform's own compliance page says it is not. Both are live and public at the same time.
/why-us: "Compliance baked in — 1099/W-8, SOC 2 Type II, ISO 27001, GDPR." The homepage also advertises a "SOC 2 Type II" badge./compliance: "No. HuntBug is not SOC 2 certified and holds no third-party security certification at this time. … Nothing here should be read as an audit result."/compliance page labels SOC 2 Type I / Type II as "Planned", while /why-us presents them as live controls.