Leaked secret guides

Found an API key, token or password in a public repository? Every provider has its own way to kill it, and the first hour decides how much damage follows. These guides give you the order of operations for each type of secret: where to revoke it at the provider, how to tell whether someone used it, what to harden afterwards, and how to clean up the repository last. Each guide is written for one provider, so you are not guessing which menu to open. LeakWatch detects these same secret types in public commits on GitHub, GitLab and Codeberg, and for many of them it checks whether the key is still active before reporting it. Every guide says plainly whether that live check exists for its type. Pick the one that matches what leaked; if you are not sure what is exposed, run a free scan of your account first.