x402-ai-gateway is a Solana-powered, pay-per-request AI inference gateway. We take security seriously and appreciate responsible disclosure of vulnerabilities.
IMPORTANT: Do NOT report security vulnerabilities through public GitHub issues, discussions, or pull requests.
Email (Preferred):
- Address:
gajeramit180@gmail.com - Subject: Include
[SECURITY]prefix - Response: Within 48 hours
GitHub Security Advisory:
- Use GitHub's private vulnerability reporting
- Link: https://github.com/mitgajera/x402-ai/security/advisories/new
Security.txt:
- Location:
x402_receipts/security.txt
- Vulnerability type and affected component
- Severity assessment (Critical/High/Medium/Low)
- Steps to reproduce
- Potential impact
- Suggested fix (if available)
- Environment details (devnet/mainnet)
| Severity | Response Time |
|---|---|
| Critical | 24-48 hours |
| High | Within 1 week |
| Medium | Within 2 weeks |
| Low | Within 1 month |
You will receive:
- Acknowledgment within 48 hours
- Regular status updates
- Security advisory publication (with credit, if desired)
- Patch release
- Smart contract vulnerabilities (Anchor program)
- Payment flow security issues (replay attacks, amount manipulation)
- API endpoint vulnerabilities (auth bypass, injection)
- Frontend security (XSS, wallet connection issues)
- Private key exposure or environment variable leaks
- Transaction validation bugs
- Data privacy issues
- Denial of Service (DoS/DDoS) attacks
- Social engineering attacks
- Physical security issues
- Third-party dependency vulnerabilities (report to maintainer)
- Issues in services we don't control (Solana network, wallet extensions)
- Self-XSS or issues requiring root/admin access
- Theoretical vulnerabilities without proof-of-concept
If unsure, report it anyway. We'd rather review a false positive than miss a real vulnerability.
- Act in good faith and follow responsible disclosure
- Test only on your own accounts or with permission
- Minimize impact on other users
- Use testnet/devnet for testing
- Report vulnerabilities promptly
- Access or modify data that doesn't belong to you
- Perform attacks that could harm the service or users
- Violate laws or breach agreements
- Publicly disclose before we address the issue
- Test on mainnet with real funds
- Use automated scanning tools that impact availability
Critical: Complete system compromise, fund loss, remote code execution (24-48 hour fix)
High: Significant data breach, unauthorized access, payment bypass (1 week fix)
Medium: Limited data exposure, privilege escalation (2 week fix)
Low: Minor security issues, configuration problems (1 month fix)
For Users:
- Never share private keys or seed phrases
- Verify transaction details before signing
- Use hardware wallets for significant amounts
- Keep wallet software updated
For Developers:
- Follow Anchor security best practices
- Validate all inputs
- Never commit private keys
- Use environment variables for secrets
- Rotate keys regularly
- Use separate keys for devnet/mainnet
While we don't currently offer monetary rewards, we provide:
- Public acknowledgment in security advisories (with permission)
- Security hall of fame recognition
- Early access to security patches
- Special thanks for significant contributions
- Program ID:
12wpFdqZm2bwCUNSiqB8UJTwRJFkevU5vUuE8XxhpHE1 - Network: Devnet (testing), Mainnet-beta (production)
- Repository: https://github.com/mitgajera/x402-ai
- Security Email:
gajeramit180@gmail.com - PGP Key: Available upon request
- Anchor Security Best Practices
- Solana Security Guidelines
- OWASP Top 10
- Common Solana Vulnerabilities
We provide safe harbor for security researchers who:
- Act in good faith
- Follow responsible disclosure practices
- Comply with this security policy
- Don't access/modify data beyond what's necessary to demonstrate the vulnerability
Security researchers acting in accordance with this policy will not face legal action from us.
Contact us at gajeramit180@gmail.com with subject line [SECURITY QUESTION].
Thank you for helping keep x402-ai-gateway and its users safe!
Last Updated: 2024