The Bug Bounty Landscape
Bug Bounty Fundamentals · Bug Bounty track
4 min read
In this module
From Netscape to a Global Industry
Bug bounties aren't new. Back in 1995, Netscape launched the first known programme, offering cash to anyone who could break Navigator 2.0. The idea was simple, almost heretical for the time: stop relying on internal testers alone, and pay outsiders to find your flaws. It took more than a decade to catch on. Mozilla formalised its programme in 2004, Google followed in 2010, and by 2012 dedicated platforms like HackerOne and Bugcrowd had appeared to connect researchers with organisations at scale.
Today the ecosystem is a multi-hundred-million-dollar industry. According to its own 2025 Hacker-Powered Security Report, HackerOne alone paid out $81 million in bounties between July 2024 and June 2025, across roughly 1,950 programmes. Figures like these change every year, so treat them as a snapshot. Tens of thousands of researchers participate worldwide, though the money is concentrated: a relatively small group of top hunters earns most of it, and many participants earn little or nothing. Programmes run by tech companies, banks, and even government departments are now routine.
How Bug Bounty Platforms Work
A bug bounty platform acts as an intermediary between three parties: the researcher who finds vulnerabilities, the organisation that owns the software, and the platform that manages the process.
The platform handles the unglamorous bits: a submission portal, a triage team performing initial validation, a reputation system, safe harbour frameworks, and payment processing. Organisations get to outsource the operational headache of fielding hundreds or thousands of reports.
The major platforms each carve out their own territory:
- HackerOne is the largest with over 1,950 active programmes. Its reputation system tracks signal (report quality) and impact (severity of findings), and it hosts both public and private programmes.
- Bugcrowd is the runner-up. It leans on managed triage and CrowdMatch, which pairs researchers to programmes by skill, and uses its own P1-through-P5 taxonomy rather than CVSS.
- Intigriti is Belgium-based, strong across EMEA, with smooth onboarding and generally lower competition. A good fit for newer researchers.
- YesWeHack is France-based and Europe's leading platform, with deep roots in French enterprises and EU government contracts.
VDPs vs Paid Bounty Programmes
Not every programme pays cash. A Vulnerability Disclosure Programme (VDP) provides a channel for researchers to report security issues, but typically offers no monetary reward. The organisation may acknowledge the researcher in a hall of fame or provide non-monetary recognition such as branded merchandise.
A paid bounty programme offers cash rewards based on the severity of the vulnerability. Typical payout ranges are:
| Severity | CVSS Range | Typical Payout |
|---|---|---|
| Critical | 9.0 - 10.0 | $5,000 - $100,000+ |
| High | 7.0 - 8.9 | $1,000 - $10,000+ |
| Medium | 4.0 - 6.9 | $250 - $2,500 |
| Low | 0.1 - 3.9 | $50 - $500 |
The CVSS bands are the standard qualitative ratings, and the payouts are illustrative; each programme publishes its own table. Bugcrowd programmes rate findings P1 (most severe) to P5 with its Vulnerability Rating Taxonomy instead, which assigns priority by vulnerability type rather than by CVSS score, so a P2 there doesn't map neatly onto a CVSS range.
VDPs are valuable for beginners precisely because they're less competitive. Experienced researchers chase paid programmes, leaving VDPs with attack surface that everyone else has skipped over. They're also a safe place to build a track record before pitching for private invitations.
Public vs Private Programmes
Programmes come in two visibility levels. Public programmes are open to every researcher on the platform; anyone can view the scope, read the policy, and submit reports. The trade-off is competition. Thousands of researchers test the same targets, and easy findings vanish fast.
Private programmes are invitation-only. The platform picks researchers based on reputation, skill set, and past performance. Less competition, higher payouts, more responsive triage. For many full-time researchers, private invitations are the bulk of their income.
Bug bounty hunting is a professional relationship, not an adversarial one. Organisations are paying you to help them improve their security. Approach every interaction with professionalism: report clearly, communicate respectfully, and follow the programme's rules. Researchers who build a reputation for high-quality, professional work receive private invitations and develop long-term relationships with security teams.
Most researchers walk the same path: start with public VDPs to learn the rhythm of submission, move to public paid programmes once you can write a clean report, and pick up private invitations as your reputation accumulates. Each stage feeds the next.