Contribute
Help improve Solana ecosystem security
Why Contribute?
The Superteam Security dashboard aims to be a comprehensive resource for the Solana ecosystem. By contributing to this public good, you help improve the security awareness and practices across the ecosystem. Your contributions directly impact the safety of protocols and users.
Enhance Knowledge
Document vulnerabilities and help others learn from past incidents
Improve Security
Contribute to better security practices and standards
Join Community
Connect with security researchers and protocol developers
1. Fork the Repository
Start by forking the Superteam Security Repository to your GitHub account.
2. Add or Update Vulnerability Data
You can contribute by adding new vulnerability entries or updating existing ones using Markdown files in the /data/vulnerabilities directory.
Use the frontmatter to provide metadata (e.g. title, date, severity, auditor), and include the exploit or vulnerability details in the body of the Markdown file. Be sure to follow the format outlined in the repository’s contributing guidelines.
01-vulnerability-2025.md
---
id: vulnerability id
title: Mango Markets Price Manipulation Attack
protocol: Protocol Name
protocolType: Bridge/DEX/Lending/Stablecoin/Yield Farming/etc
exploitDate: YYYY-MM-DD
amountStolen: 1000000 // in USD
exploitType: Signature Spoofing
technique: Detailed description of the exploit technique
auditor: Audit firm name or Unaudited
status: published/draft
collaborators:
- username: Prastut
url: https://x.com/prastutkumar
- username: 0xDeep
url: https://x.com/0xDeep
---
Markdown section to enter vulnerability details.3. Verify Your Contribution
Ensure your data is accurate, properly formatted, and includes relevant references to support your submission. Test your changes locally to make sure everything works as expected.
4. Submit a Pull Request
Once you're ready, submit a pull request to the main repository. Provide a clear description of your changes and why they're valuable. Our team will review your submission and provide feedback if needed.
Contribution Guidelines
- •Ensure all vulnerability information is factually correct and verified
- •Include technical details when possible, including root cause analysis
- •Provide references to official postmortems, analyses, or news articles
- •Format code snippets and technical details properly
- •Respect intellectual property and don't share private or confidential information
Need help with your contribution? Have questions about the project? Join our community channels to connect with other contributors and the project maintainers.