Malicious Script Injection in Trivy Compromise Enables Credential Theft
## Cybersecurity: Trivy GitHub Action Compromise
Cybersecurity: Trivy GitHub Action Compromise
A sophisticated supply chain attack has targeted the aquasecurity/trivy-action on GitHub, affecting continuous integration and continuous deployment (CI/CD) pipelines globally.
Disclosed in late March 2026, this incident represents the second compromise in the Trivy ecosystem within a month.
Attackers successfully force-pushed 75 out of 76 existing version tags, distributing a malicious infostealer. Over 10,000 GitHub workflow files depend on this action, significantly increasing potential credential theft risks.
The attacker utilized residual write access from a previous breach to alter existing version tags without creating a new release or branch. This allowed them to distribute malware through trusted version references.
The threat actor targeted widely used versions such as @0.33.0 and @0.18.0 , pointing them to newly forged commits.
Disclosed in late March 2026, this incident represents the second compromise in the Trivy ecosystem within a month.
The attacker spoofed Git commit metadata by replicating original author names, dates, and messages, making malicious commits appear legitimate. The legitimate entrypoint.sh file was replaced with an infected version.
Version @0.35.0 remains unaffected and is the only safe tag.
The injected entrypoint.sh script executes malicious operations before the legitimate Trivy scan, remaining hidden.
Collection: Targets both GitHub-hosted and self-hosted runners, extracting secrets directly from memory or the filesystem. Encryption: Uses AES-256-CBC for compression and encryption, with the key wrapped by an RSA-4096 public key. Exfiltration: Attempts data exfiltration via HTTPS POST to a typosquatted domain. If unsuccessful, it uses the victim's GitHub Personal Access Token to create a public repository for data upload.
Organizations should immediately cease referencing trivy-action by version tags, except @0.35.0 . Pin actions to commit SHA 57a97c7e7821a5776cebc9bb87c984fa69cba8f1 for security.
Any environment executing a compromised tag should be deemed compromised. Security teams must rotate all exposed secrets, including cloud credentials and API tokens, and audit for unauthorized repositories.
Based on reporting by Cyber Security News.