Bug Bounties
Help us improve Numerai and earn NMR!
We need and want your help to improve Numerai so we will aim to be generous and fair with our bounties where possible. If you feel like you deserve more/less bounty for your contribution just let us know!
The examples listed below are not exhaustive and the bounty amounts listed above are only rough guidelines. The exact amounts depends on the actual bug, feedback or suggestion. Actual bounty payout amounts, if any, will be determined by Numerai at its sole discretion. Please allow 3-5 business days for a response to reports.
Bugs
If you see anything that is broken, report it! If it turns out to be a real issue and your report helped us fix it then we will give you a bounty!
Note: You must have a Numerai Tournament account to receive bounty payment. US persons receiving a bounty valued > $600 USD will be required to submit W9 taxpayer information.
Regardless of your tax jurisdiction, you are solely responsible for any tax implications related to any bounty payouts you may receive.
Out-of-Scope
We consider the follow to be of negligible security impact unless the researcher provides concrete explanation and valid proof-of-concept to support claims:
Missing security headers
Reports that state that software is out of date/vulnerable without a proof-of-concept
Highly speculative reports about theoretical damage
Vulnerabilities as reported by automated tools without additional analysis as to how they're an issue
Reports from automated web vulnerability scanners (Acunetix, Vega, etc.) that have not been validated
SSL/TLS scan reports (this means output from sites such as SSL Labs)
Open ports without an accompanying proof-of-concept demonstrating vulnerability
Subdomain takeovers - please demonstrate that you are able to take over the page by leaving a non-offensive message, such as your username
CSV injection
Unchained open redirects
Best practices concerns
Protocol mismatch
Rate limiting
Exposed login panels
Dangling IPs
Vulnerabilities that cannot be used to exploit other users or Numerai-- e.g. self-xss or having a user paste JavaScript into the browser console
Content injection issues
Missing cookie flags on non-authentication cookies
Cross-site Request Forgery (CSRF) with minimal security implications (Logout CSRF, etc.)
Reports that affect only outdated user agents or app versions -- we only consider exploits in the latest browser versions for Safari, FireFox, Chrome, Edge, IE and the versions of our application that are currently in the app stores
Issues that require physical access to a victim’s computer/device
Stack traces
Path disclosure
Directory listings
Exclusions
While researching, we'd like to ask you to refrain from:
Denial of service
Spamming
Rate limiting attacks (unless it constitutes a significant risk)
Attacking or compromising user accounts
How to submit a vulnerability report
Send email to security@numer.ai explaining the vulnerability, it's impact, and proof-of-concept to support claims. The proof-of-concept must provide steps to execute an attack or exploit the vulnerability. Reports submitted after an actual attack takes place will be ineligible for a bounty.
Feedback & Suggestions
If you have any good ideas about how to improve the Numerai propose it to us! If it is a good idea and we end up using it then we will give you a bounty!
How to give feedback and suggestions
Message us on the Discord.
If you are going for a large bounty, it would be helpful if you wrote up your idea in a document (pdf or google docs) or a notebook (google colab, github).
Last updated