Use Clunkyard's private vulnerability reporting to send a report to the organization maintainers. Name the affected repository or game feature and include the steps, impact and smallest safe reproduction you can provide.

Keep vulnerabilities, account tokens, API keys and private robot source out of public issues. Ordinary bugs belong in the affected repository’s issue tracker; questions belong in community discussions. See Support for the right route.