Trivy Compromise - Credential Theft from GitHub Action
Basically, hackers used a trick to steal passwords from many software projects.
A major supply chain attack has compromised Trivy's GitHub Action, risking credential theft across thousands of CI/CD pipelines. Organizations must act fast to secure their environments and rotate exposed secrets. Don't let your data fall into the wrong hands!
What Happened
In a concerning development for software security, a sophisticated supply chain attack has compromised the official Trivy GitHub Action, impacting continuous integration and deployment (CI/CD) pipelines worldwide. Disclosed in late March 2026, this incident marks the second compromise of the Trivy ecosystem within just a month. The attackers managed to force-push 75 out of 76 existing version tags, effectively distributing a malicious infostealer to over 10,000 GitHub workflow files that rely on this action.
The attack was executed by leveraging residual write access from a previous credential breach, allowing the threat actors to alter existing version tags without raising alarms. This method minimized the chances of detection, as it avoided creating new releases or pushing code to branches, which typically trigger security alerts.
Who's Affected
The impact of this attack is extensive, affecting numerous organizations that utilize the Trivy GitHub Action in their CI/CD pipelines. With over 10,000 workflows potentially compromised, the blast radius for credential theft is massive. This includes both GitHub-hosted and self-hosted runners, making it a critical issue for many developers and companies relying on this tool for security scanning.
Organizations that have executed any of the poisoned version tags are at risk. The attackers specifically targeted sensitive data, including SSH keys, database credentials, and CI/CD configuration files, which could lead to further exploitation if not addressed promptly.
What Data Was Exposed
The malicious script injected into the Trivy GitHub Action is designed to collect sensitive data systematically. During its operation, the infostealer targets:
- SSH keys and Git credentials
- Cloud provider credentials (AWS, Azure)
- CI/CD and Docker configurations
- Environment files containing sensitive variables
- Cryptocurrency wallet data
The malware operates in stages, including targeted collection, encryption, and stealthy exfiltration of the stolen data. It uses advanced techniques like AES-256 encryption and attempts to exfiltrate data via HTTPS requests, even creating public repositories to hide its tracks if initial attempts fail.
What You Should Do
Organizations using the Trivy GitHub Action must take immediate action. Here are the recommended steps:
- Stop referencing any version tags of the Trivy Action, except for the untouched version @0.35.0.
- Pin the action to a specific safe commit SHA (57a97c7e7821a5776cebc9bb87c984fa69cba8f1) to prevent further exploitation.
- Rotate all exposed secrets, including cloud credentials and API tokens, to mitigate potential breaches.
- Audit GitHub organizations for any unauthorized repositories named tpcp-docs, which may contain stolen data.
Taking these steps is crucial to safeguard your organization against the fallout from this alarming attack. The threat landscape is evolving, and vigilance is key.
Cyber Security News