Trivy supply-chain attack spreads to Docker, GitHub repos
Recorded: March 23, 2026, 7 p.m.
| Original | Summarized |
Trivy supply-chain attack spreads to Docker, GitHub repos News Featured Trivy vulnerability scanner breach pushed infostealer via GitHub Actions Microsoft Azure Monitor alerts abused for callback phishing attacks Musician admits to $10M streaming royalty fraud using AI bots FBI links Signal phishing attacks to Russian intelligence services Trivy supply-chain attack spreads to Docker, GitHub repos Varonis Atlas: Securing AI and the Data That Powers It Microsoft Exchange Online service change causes email access issues Block ads and trackers on 9 devices for only $16 in this deal Tutorials Latest How to access the Dark Web using the Tor Browser How to enable Kernel-mode Hardware-enforced Stack Protection in Windows 11 How to use the Windows Registry Editor How to backup and restore the Windows Registry How to start Windows in Safe Mode How to remove a Trojan, Virus, Worm, or other Malware How to show hidden files in Windows 7 How to see hidden files in Windows Webinars Latest Qualys BrowserCheck STOPDecrypter AuroraDecrypter FilesLockerDecrypter AdwCleaner ComboFix RKill Junkware Removal Tool Deals Categories eLearning IT Certification Courses Gear + Gadgets Security VPNs Popular Best VPNs How to change IP address Access the dark web safely Best VPN for YouTube Forums Virus Removal Guides HomeNewsSecurityTrivy supply-chain attack spreads to Docker, GitHub repos Trivy supply-chain attack spreads to Docker, GitHub repos By Bill Toulas March 23, 2026 The TeamPCP hackers behind the Trivy supply-chain attack continued to target Aqua Security, pushing malicious Docker images and hijacking the company’s GitHub organization to tamper with dozens of repositories. "We rotated secrets and tokens, but the process wasn't atomic and attackers may have been privy to refreshed tokens," Aqua Security This allowed the attacker to inject into Trivy credential-harvesting code (TeamPCP Cloud stealer) and publish malicious versions of the tool. Red Report 2026: Why Ransomware Encryption Dropped 38% Related Articles: Docker Bill Toulas Previous Article Post a Comment Community Rules You need to login in order to post a comment Not a member yet? Register Now You may also like: Popular Stories Microsoft: March Windows updates break Teams, OneDrive sign-ins Microsoft Azure Monitor alerts abused for callback phishing attacks CISA orders feds to patch max-severity Cisco flaw by Sunday Sponsor Posts Are refund fraud methods targeting your brand? You can monitor the underground for these threats. Overdue a password health-check? Audit your Active Directory for free AI is a data-breach time bomb: Read the new report Secure your AI agents without sacrificing speed. Cyber resilience without the complexity. Join Zero Networks to stop lateral movement fast. Follow us: Main Sections News Community Forums Useful Resources Welcome Guide Company About BleepingComputer Terms of Use - Privacy Policy - Ethics Statement - Affiliate Disclosure Copyright @ 2003 - 2026 Bleeping Computer® LLC - All Rights Reserved Login Username Password Remember Me Sign in anonymously Sign in with Twitter Not a member yet? Register Now Help us understand the problem. What is going on with this comment? Spam Abusive or Harmful Inappropriate content Strong language Other Read our posting guidelinese to learn what content is prohibited. Submitting... |
The TeamPCP threat actor orchestrated a sophisticated supply-chain attack targeting Aqua Security’s Trivy vulnerability scanner, initiating a cascade of compromises that extended to Docker Hub and numerous GitHub repositories. This incident, detailed by Socket and OpenSourceMalware, highlights critical vulnerabilities in software artifact management and underscores the escalating risks associated with supply-chain security. Initially, the attackers gained unauthorized access to Aqua Security’s GitHub organization through a compromised service account, Argon-DevOps-Mgt, which possessed elevated privileges within both the public and private GitHub organizations. This account, utilizing a Personal Access Token (PAT) instead of a GitHub App, lacked the security mitigations typically associated with service accounts, including multi-factor authentication (MFA). The attackers exploited this weakness, leveraging the TeamPCP Cloud stealer, which harvests sensitive data like GitHub tokens and credentials, to further their intrusion. They then utilized this access to inject malicious code into Trivy images, pushing compromised versions to Docker Hub. Through automated actions, they appended “tpcp-docs-” to 44 repositories, simultaneously altering descriptions to reflect TeamPCP ownership. Following the initial breach, Aqua Security swiftly responded by publishing updated, safe versions of Trivy and engaging Sygnia for remediation. However, subsequent investigation revealed a renewed cyberattack, with TeamPCP regaining unauthorized access and further tampering with repositories. Despite Aqua Security’s actions, no impact was reported on the commercially deployed version of Trivy due to a deliberate lag in incorporating open-source changes through a controlled integration process. OpenSourceMalware provided a comprehensive set of Indicators of Compromise (IOCs) to assist defenders in identifying and mitigating the impact of this attack. These IOCs centered on the compromised service account, the malicious image tags pushed to Docker Hub, and the specific repository modifications made by the attackers. The attackers’ method of gaining access - leveraging a vulnerable service account lacking MFA – illustrates a common and increasingly problematic security risk within DevOps environments. It’s a critical reminder that even seemingly automated systems can be exploited if basic security practices are not rigorously enforced. The incident served as a stark reminder of the importance of immutable tags in Docker Hub and the need for organizations to verify the integrity of software artifacts. Aqua Security's experience underscores the potential damage from compromised build pipelines and exposes weaknesses in the oversight mechanisms surrounding open-source tools like Trivy. The breach also highlighted the vulnerability of service accounts, particularly those with broad access permissions, and reinforced the imperative of implementing robust MFA and granular access control policies within development and operation environments. The event triggered a wider awareness of supply-chain vulnerabilities within the software development lifecycle, prompting a renewed focus on security best practices and proactive monitoring strategies. The rapid response and subsequent updates by Aqua Security, coupled with the detailed analysis by OpenSourceMalware, offered valuable insights for the broader security community in understanding the attack vector and mitigating similar risks. |