Trust
Security
Vulnerability disclosure policy
How to report a security issue in Rehive, what is in scope, and the rules that keep your research authorised.
Updated 16 Nov 2026
Contact: [email protected]
On this page
How to report
We welcome reports from security researchers. Email [email protected]. Please send one issue per report, in English.
What a report needs
We review reports that show a real, exploitable security issue. Please include:
- The affected asset: the exact URL, API endpoint, app, library or component.
- Steps to reproduce: clear enough for one of our engineers to follow without guessing, with the requests and responses (curl commands or an HTTP log work well) and the test account you used.
- A working proof of concept, using only accounts you own. An error response, a validation message, or something our docs do not mention is not a proof of concept on its own.
- The impact: what an attacker could actually do, for example read or change another user's data, move funds, take over an account or bypass authentication.
We may close reports that do not include these without replying.
In scope
- The Rehive platform API and Rehive extensions
- Rehive web apps, including the dashboard and wallet apps
- Rehive open source software and libraries
- Rehive websites
Out of scope
Unless you can show a concrete exploit with real security impact, we will not act on:
- output from automated scanners that has not been verified by hand
- missing security headers, cookie flags or other best-practice findings
- email and DNS configuration (SPF, DKIM, DMARC, CAA, DNSSEC) or TLS configuration
- clickjacking on pages with no sensitive actions, self-XSS, or login and logout CSRF
- missing rate limits, unless you can show harm such as account takeover or financial loss
- user enumeration, version disclosure, or outdated software without a working exploit
- issues in third-party services we use (please report these to the vendor)
- social engineering, phishing, physical attacks, and denial of service or load testing of any kind
Rules for testing
If you follow these rules, we will treat your research as authorised and done in good faith, and we will not take legal action against you for it:
- Test only with accounts and data you own. Create your own test accounts.
- Do not access, change, download or keep anyone else's data. If you come across it by accident, stop, tell us, and delete it.
- Do not move real funds or try to profit from an issue.
- Do not disrupt or degrade our services for other users.
- Do only what you need to confirm the issue, then stop.
- Keep the details private until we have fixed the issue, and give us reasonable time to do so.
- Comply with all applicable laws.