The program is designed to reward the community for their efforts in contributing high-quality templates for critical and trending vulnerabilities.
Bounties range from $50 to $250, depending on the complexity of the template and the effort required.
Only issues listed by us on our GitHub repository with the 💎 Bounty label are eligible for rewards. You can find these bounty issues here
Templates must meet the following criteria:
- Complete POC: A full Proof of Concept (POC) must be provided and not rely solely on version detection.
- Debug Data: Include debug data to assist with template validation.
- Validation Required: The template will be reviewed and validated before rewards are given.
- Accurate Matchers: Use strong matchers to avoid false positives.
Note: Triagers will make the final decision on whether a template qualifies for a reward based on validation and the acceptance criteria outlined.
- Find an Issue: Look for issues tagged with 💎 Bounty.
- Declare Work: Comment with
/attempt #<issue_number>
to claim the issue. - Submit Work: Submit your pull request with
/claim #<issue_number>
in the PR description when ready.
We add new bounty issues on a weekly basis, so make sure to check back regularly for fresh opportunities. In the future, you can expect many more bounty issues as the program expands, allowing more opportunities for contributors to participate and earn rewards.
Yes, you can collaborate with other contributors and split rewards by commenting:
/claim #<issue_number>
/split @contributor1
/split @contributor2
You can work on up to 3 issues simultaneously.
Issues must be completed within 2 months, or they will be closed.
Rewards are distributed once the template is fully validated. If the issue remains unresolved for few weeks, the bounty may increase.
Include the following:
Avoid adding code templates for CVEs that can be achieved using HTTP, TCP, or JavaScript. Such templates are blocked by default and won’t produce results, so we prioritize creating templates with other protocols unless exceptions are made.
- Complete POC: A working Proof of Concept.
- Matchers: Multiple matchers to prevent false positives.
- Debug Data: Data to assist the triage team in validation.
- Metadata: Include required fields like
id
,name
,author
,severity
,description
, andreference
.
Templates may be rejected if they:
- Rely solely on version detection.
- Lack a complete POC.
- Contain weak matchers or redundant changes to existing templates.
- Avoid sharing real-world targets publicly.
- Don’t submit templates with weak matchers.
- Avoid unnecessary changes to existing templates.
Yes! We now have a leaderboard that showcases top contributors. You can check it out here: Leaderboard.
The rewards program is currently a test run, but we may make changes based on community feedback.
Beyond bounties, we also reward contributors with:
- Swag such as t-shirts and stickers.
- Invites to security conferences for standout contributors.
- Stickers as a token of appreciation for all first-time contributors, regardless of the bounty.
Contributors who feel their pull request or issue was overlooked for first-time contributor stickers can ping us on our Discord for assistance: ProjectDiscovery Discord.