Skip to content
Listed on Cybermalveillance.gouv.fr since November 4Has your email shown up in a data breach? Check it for freeWhat our security audit report looks like, section by section: are you affected?CERT-FR alertFlaws in F5 NGINX: are you affected?
bughunter.pro

Private bug bounty: you only pay for the flaws we find

A private bug bounty is cybersecurity testing paid by results. Our ethical hackers attack your website, application or API with the same method as a penetration test, on a scope we define together. Every proven flaw earns a bounty set upfront by severity, up to a cap. No flaw, no fee.

At a glance

  • The ideaA bounty per proven flaw, set by severity before we start.
  • What's paidEvery proven flaw, at the scale we agree on.
  • Your budgetA cap we agree on together. Your invoice never goes over it.
  • What you getEach flaw with its proof and fix, a final report and a retest.

Vulnerabilities found across these sectors

  • Public services (.gouv.fr)
  • CAC 40 groups
  • Luxury leaders
  • National media
  • Local authorities

No flaw, no fee

You don't pay for our time. You pay for what we find, at a price set before we start.

In a classic penetration test, you buy days of research on a scope. The price is the same whether we find ten flaws or none: that's the right deal when you need to prove everything was checked.

A private bug bounty flips that. Before we start, we agree on the scope, the bounty for each severity level and a cap. After that, only proven flaws get billed.

It's how large companies run bug bounty programs with cybersecurity researchers, scaled to your project: a team you know instead of a crowd of strangers, and no platform fee.

Sample campaign

  • Another customer's orders readableCriticalbounty
  • Script injected into customer reviewsHighbounty
  • Customer accounts guessable at loginMediumbounty

Billed3 bounties, under the cap

Three flaws, three bounties. The invoice adds up the bounties agreed at scoping, under the cap. Had the campaign found nothing, it would be €0.

How a campaign runs

Six steps, from scoping to retest. Only the billing differs from a penetration test.

Read the full methodology
  1. 01

    Scoping

    A call to set the scope, the campaign's length, the bounty for each severity level and the cap. Bounties depend on what a flaw is worth on your scope, and they're written into the scoping before we start. NDA as soon as we get into technical detail, penetration testing authorization agreement signed before any access.

  2. 02

    Research

    Same method as a penetration test: full mapping, then manual research where our in-house tools stop. We look for what an attacker would look for, not just what's quick to find.

  3. 03

    Proof

    Every flaw is shown with a reproducible proof of concept, going no further than needed. A critical flaw is flagged to you the same day, without waiting for the end of the campaign.

  4. 04

    Validation

    Each flaw is rated against the agreed scale, and you sign off on it with us. The same root cause found in several places counts once.

  5. 05

    Invoice

    You pay the sum of the bounties for validated flaws, never more than the cap. If we found nothing, there's nothing to pay.

  6. 06

    Report and retest

    A final report covers each flaw with its proof and fix, and describes what was tested. Once your fixes are in, we recheck every flaw you paid for. The retest is included.

What counts as a flaw

The rules are written down before the campaign starts, so there's nothing to argue about at the end

  • Proven, not assumed

    A flaw counts once we've shown it on your scope, with proof your team can replay. An unverified tool alert doesn't count.

  • Paid once

    The same root cause found on several pages or endpoints counts once. You pay for a flaw, not its copies.

  • Per the signed scale

    Its severity follows the scale agreed at scoping, based on what the flaw actually allows on your systems.

Pentest or bug bounty: which one?

Both rely on the same team and the same method. What changes is what you buy: full coverage, or results.

Penetration test on a fixed quote and private bug bounty, compared
Penetration testFixed quote, set upfrontPrivate bug bountyPay for results, bounty by severity
What you pay forDays of research, at a price set upfront.The flaws we find, at a bounty set upfront by severity.
If nothing is foundThe agreed price, with a report showing everything was checked.Nothing.
Your budgetKnown to the euro before we start.Capped. The invoice depends on what we find, never above the cap.
CoverageEvery part of the scope is checked and documented.We hunt for flaws, with no commitment to cover everything.
The reportA full report that also documents everything checked: useful for a customer, insurer or auditor.A final report with each flaw, its proof and its fix.
RetestIncluded.Included, for the flaws you paid for.

Swipe the table to see both columns.

Penetration testFixed quote, if…

  • a customer, insurer or auditor asks you for a penetration test report
  • you need to show the whole scope was checked
  • it's a first test: on an application that's never been audited, flaws are often many and a fixed quote works out cheaper
  • your budget has to be known to the euro
Web penetration testing

Private bug bountyPay for results, if…

  • you want to test a targeted scope: a feature, an API, a new release
  • your application has been tested before and you want to know what's left
  • you'd rather pay for results than for time
  • you want to start without a fixed budget, staying in control with the cap
Talk about a bug bounty

The two work well together: a penetration test before launch, then a private bug bounty on new features.

A bug bounty, without the platform

We hunt on YesWeHack and Intigriti ourselves. We keep their rules, not the middleman.

  • A team, not a crowd

    The same people from scoping to retest, under NDA. Not hundreds of anonymous researchers on your application.

  • No platform fee

    A platform bills for its service on top of the bounties. Here, you only pay the bounties you agreed to.

  • A written framework

    A penetration testing authorization agreement signed before any access, with the scope, length and rules of the campaign.

Your questions, answered

Another question?

Write to us in a few lines. We reply within 24 business hours.

Contact us
Can a penetration test be free?

Yes, in one specific case: in a private bug bounty, if we find no flaw, you pay nothing. It's not a cut-price test: the method is a penetration test's. A penetration test on a fixed quote, on the other hand, is paid whatever the outcome, because it guarantees the whole scope was checked.

What if you find nothing?

You pay nothing. You still get a final report on what was tested.

How are the bounties set?

At scoping, for each severity level. They depend on your scope and what a flaw would allow there. The scale is written into the scoping before the campaign starts.

What happens when the cap is reached?

The campaign stops and nothing more is billed. As we get close to the cap, we let you know so you can raise it or stop there.

Who does the testing?

Our team, the same one that runs our penetration tests. No anonymous researchers: the same people from scoping to retest, under NDA.

Is it legally covered?

Yes, just like a penetration test: a penetration testing authorization agreement is signed before any access, with the scope, the length and the rules.

Why not a platform like YesWeHack or Intigriti?

Platforms suit large programs open to hundreds of researchers. For a targeted scope, they add fees and a crowd of researchers you don't know. We hunt on those platforms ourselves: we keep their rules, without the middleman.

Only pay for what we find

Your application is a target

Tell us about the scope and what worries you. We'll propose a bounty scale, a cap and a length. The first conversation comes with no commitment.