3 min read
[AI Minor News]

Trivy Strikes Again! 75 GitHub Actions Tags Compromised, Cloud Credentials Stolen


The popular vulnerability scanner Trivy has suffered a major compromise, with its GitHub Action tags tampered with, leading to the theft of secrets from CI/CD environments.

※この記事はアフィリエイト広告を含みます

[AI Minor News Flash] Trivy Strikes Again! 75 GitHub Actions Tags Compromised, Cloud Credentials Stolen

📰 News Summary

  • In a shocking twist, 75 out of 76 version tags of the official GitHub Action for the popular vulnerability scanner Trivy (aquasecurity/trivy-action) have been forcefully rewritten by attackers.
  • The tampered tags included a malicious infostealer capable of extracting AWS, GCP, and Azure credentials, SSH keys, Kubernetes tokens, and more from execution environments.
  • This attack follows a breach of a VS Code extension earlier in March, attributed to incomplete credential rotation from the previous incident.

💡 Key Points

  • Trust in Tags Shattered: Typically, fixing a version like “@v0.33.0” was seen as safe, but since the tags were rewritten, even fixed versions could execute malicious code. As of now, “@0.35.0” is the only tag confirmed safe.
  • Advanced Deception: Attackers replaced only the entrypoint.sh file with malware, pushing it based on the latest legitimate code, using a technique called “force-updating tags” to delay detection.
  • AI Detection: Socket’s AI scanner detected 182 malicious GitHub Actions related to this attack in real-time, correctly categorizing them as backdoors and infostealers.

🦈 Shark’s Eye (Curator’s Perspective)

This attack isn’t just a bug; it’s a malicious maneuver that strikes at the very foundation of trust! I was stunned to see 75 past tags, which developers believed to be stable, altered all at once. Ironically, the very tool designed to find vulnerabilities has been turned into a “thief” that steals cloud credentials. The fact that Socket’s AI identified these as infostealers in real-time showcases the effectiveness of AI in defense! The clever method of swapping out just entrypoint.sh reveals the attackers’ deep understanding of CI/CD environments – talk about dedication!

🚀 What’s Next?

The practice of specifying versions based on tags in GitHub Actions is likely to be reevaluated, with a shift toward using “commit SHA” for more tamper-resistant fixes. Moreover, similar breaches have been spotted on Docker Hub, ushering in an era where AI monitoring tools are essential to ensure the integrity of the entire supply chain.

💬 A Shark’s Take

It’s terrifying to think that a tool designed to find vulnerabilities could become a data-stealing shark! Everyone, take a moment to review your GitHub settings right now! 🦈🔥

📚 Terminology

  • Infostealer: Malware specifically designed to extract sensitive information such as passwords, authentication tokens, and credit card data from computers.

  • GitHub Actions: A tool that automates workflows for building, testing, and deploying on GitHub, allowing developers to incorporate “Actions” created by others as components.

  • Force-Push: An operation in Git that forcibly overwrites the history of a remote repository. While generally discouraged, it allows users with the right permissions to alter tags or branch contents.

  • Source: Trivy under attack again: Widespread GitHub Actions tag compromise secrets

【免責事項 / Disclaimer / 免责声明】
JP: 本記事はAIによって構成され、運営者が内容の確認・管理を行っています。情報の正確性は保証せず、外部サイトのコンテンツには一切の責任を負いません。
EN: This article was structured by AI and is verified and managed by the operator. Accuracy is not guaranteed, and we assume no responsibility for external content.
ZH: 本文由AI构建,并由运营者进行内容确认与管理。不保证准确性,也不对外部网站的内容承担任何责任。
🦈