> For the complete documentation index, see [llms.txt](https://spawnmeme.gitbook.io/spawnmeme-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/reference-and-support/49-responsible-disclosure.md). # 49. Report a security problem Tell the SPAWN team privately about a security problem so it can be fixed before anyone is harmed. **Open:** [Responsible disclosure](https://spawnmeme.com/disclosure). It is linked in the footer. ## What to report * Anything that could let someone move funds, sign for another wallet, or change a transaction a user is about to approve. * Ways to read or change another person's project, account or private data. * Ways to fake a launch, a payment, a referral payout or an airdrop. * Ways to take over the SPAWN Telegram bot, or post through it. To flag a scam token, a copied project or stolen artwork, use the **Report** link on that page instead. ## Send a private report 1. Open **Responsible disclosure**. 2. Describe what you found and how to reproduce it, with the page or address involved and any transaction signatures. 3. Add an email or Telegram username so we can reply. 4. Press **Send report**. Only the SPAWN team can read the report. Never include a seed phrase or private key; SPAWN will never ask for one. ## Ground rules * Use your own wallets and test with small amounts. * Do not access, change or delete other people's data, or move funds that are not yours. * Do not run tests that slow the site down or flood it with requests. * Do not use social engineering or phishing against the team or the community. * Give us reasonable time to fix the problem before you share it publicly. ## What to expect * We read every report and reply to the contact you give. * We will tell you whether we can reproduce it and what we plan to do. * SPAWN does not run a paid bug bounty at this time. With your permission, we are glad to credit you once a fix is live. * We will not take action against anyone who reports a problem in good faith and follows this page. **Success:** the form shows "Thank you. Your report was received and we will reply to the contact you gave." *** [Guide home](/spawnmeme-docs/feature-guides.md) · [Get help and protect your wallet](/spawnmeme-docs/feature-guides/reference-and-support/39-support-and-safety.md) · [Report a token or project](/spawnmeme-docs/feature-guides/reference-and-support/46-report.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://spawnmeme.gitbook.io/spawnmeme-docs/feature-guides/reference-and-support/49-responsible-disclosure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.