LiteLLM finds leaked Git key remains public after deletion

The author argues that deleting a file, rewriting git history, or deleting a repository does not protect developers from leaked secrets, because attackers and automated scanners continuously parse git history and retain copies. Using examples such as a LiteLLM infrastructure compromise, the article demonstrates that leaked credentials remain reachable via commit hashes and forked repositories. Consequently, the only effective safeguard is immediate credential rotation followed by an audit of access logs and recent code changes. Open article →