Responsible disclosure & bounty
We take security seriously. If you find a vulnerability, please tell us first — we'll fix it fast and credit you publicly (with your permission). We pay bounties for vulnerabilities that move money, found by researchers who use the terminal for real and follow the rules below.
Program openThe bounty is running. This page is always current: any change to the program is published here first. No need to email us to ask whether it's still open — send your report instead. We don't reply to questions about the program's status.
How to report
Email hello@vectorialdata.com with the subject starting with [Security], and include:
- A clear description of the issue and impact.
- Reproduction steps (or a proof-of-concept).
- The affected URL, endpoint, or contract.
- The test accounts you used and the dates and times (UTC) of your testing.
- Your preferred name/handle for public credit (optional).
Please don't send executables or archives with scripts; plain text or Markdown in the email body is best.
We acknowledge reports within 48 hours and aim to ship a fix or mitigation within 14 days for critical findings.
Scope
In scope:
terminal.vectorialdata.comand its API endpoints- Authentication, signing, and balance flows on the terminal
- Smart-contract integrations we wrote (builder code config, treasury setters)
Out of scope:
- Vulnerabilities in third-party protocols we integrate (Hyperliquid, Polymarket, Circle CCTP, Privy) — please report to them directly
- Denial-of-service, volumetric attacks, or rate-limit testing without prior written consent
- Social engineering, phishing, or physical attacks against our team
- Reports based on automated scanners with no demonstrated impact
- Best-practice issues without exploit (missing security headers on static pages, etc.)
Rules of engagement
Research that breaks any of these rules is not eligible for a reward or for safe harbor:
- Identify your traffic: send the header
X-Security-Research: <your handle>on every request, so we can tell research from an attack. - Use at most two test accounts that you created, and list them in your report.
- Keep automated traffic under 2 requests per second and 2,000 requests per day. No high-volume fuzzing of sign-in, signing, or withdrawal flows.
- Don't work around our defenses: if we rate-limit or block you, stop and email us. Switching IP addresses, VPNs, or accounts to keep going ends eligibility and safe harbor.
- Never try to read, change, or move another user's data or funds — not even to check. Stop at the first sign that you could, and report it.
- Only test withdrawals, withdrawal addresses, and passkey recovery on your own accounts, with the minimum needed to show the issue.
- Stop testing once you've confirmed an issue, and report it within 24 hours.
- Don't disclose publicly until we confirm a fix (or 90 days after your report, whichever comes first).
Rewards
We pay only for vulnerabilities that move money: a working path to
- take or move funds that belong to other users or to us;
- sign, withdraw, or change a withdrawal address without the owner — getting around passkeys, co-signing, or our withdrawal controls;
- freeze or lock funds so their owner can't get them out;
- make the system create or lose money — balances, fees, Earn, copy trading, or settlement that come out wrong.
Everything else — data exposure with no path to funds, missing headers, rate limits, interface bugs — is still welcome: we'll fix it and credit you (with your permission), but it isn't paid.
To take part, use the terminal first. Before you report, your test accounts must have reached $1,000 in combined volume on the terminal — perps, spot, predictions, Earn deposits, or copy trading — so the money flows you test are the real ones. We check it on our side. One exception: a report that shows how to take or move other users' funds is always eligible, whatever your volume.
Rewards go up to $50,000 in USDC. We set each one by severity — how much money was at risk and how hard it is to exploit — and by the quality of the report, and rewards are at our sole discretion. To be eligible, a report must be the first to reach us, must not already be known to us (we keep a dated internal record of findings from our own reviews), must not be publicly disclosed, and must come from testing that followed the rules above. One reward per root cause.
Rewards are paid in USDC to a wallet you control, after identity and sanctions screening. We can't pay anyone subject to sanctions or resident in a sanctioned jurisdiction.
Safe harbor
Research conducted in good faith and consistent with this policy, including the rules of engagement, will not result in legal action. Don't access or modify data that isn't yours, don't degrade service, and don't test on real user accounts — use your own. Activity outside these rules is treated like any other unauthorized access, including reports to the network providers involved.
Machine-readable
Our security.txt follows RFC 9116.