If you have received an e-mail from email@example.com saying your server registration key has been leaked on GitHub, it means anyone can see and use your leaked server registration key(s). Server registration keys are meant to be private, only for the server owner to see.
To fix this, you only have to do the following steps:
Login with your account on Keymaster.
Find the leaked server registration key(s). Leaked keys are highlighted in red and have an exclamation octagon symbol before their ID.
Click on your key ID to open the key page.
In the Details tab, click on Regenerate to change your key.
Once regenerated, your server registration key is no longer at risk 🙂.
- You will also need to replace the key on your server’s config file.
- Additionally, make sure to not commit it again in a public repository.