From exposed secrets to managed credentials: Reducing credential risk across the application lifecycle
A recent software supply chain attack affecting tens of thousands of GitHub repositories highlights a security problem that is easy to underestimate: a credential does not stop being exposed simply because it has been deleted from the latest version of the code. Researchers uncovered a campaign in which attackers inserted a malicious GitHub Actions workflow into repositories they had permission to modify. Designed to look like a routine security audit, the workflow instead searched for and exfiltrated credentials. It targeted secrets available to GitHub Actions, but also searched repository files and complete Git history for credentials associated with cloud providers and AI services. That meant credentials developers had previously committed and later removed could still be discovered. The incident is another reminder that responding to exposed credentials requires more than cleaning up source code. Organizations need to understand where credentials have been exposed, remediate those credentials and ultimately improve how they are managed. HCP Vault Radar and HashiCorp Vault can help teams address different parts of that lifecycle, moving from discovering exposed secrets to bringing credentials under centralized management. A deleted secret can still be an exposed secret Accidentally committing a credential is not an unusual scenario in software development. An API key gets added to a configuration file while testing an integration, a cloud credential helps get a prototype running, or a token is placed into a workflow to solve an immediate problem. A developer may eventually identify the mistake and remove the credential, leaving the current version of the application looking clean. But removing the plaintext value does not necessarily remediate the underlying credential. The secret can remain in Git history, the original credential may still be active, and copies may exist in other places across the development lifecycle. In this attack, that distinction was parti