Threat Intel - Aqua Security Repositories Defaced by TeamPCP
Basically, hackers changed Aqua Security's GitHub pages to show they owned them after stealing access.
Aqua Security's GitHub repositories were defaced after a supply chain attack involving malicious Trivy images. The breach exposed sensitive developer data and internal tools, raising significant security concerns.
The Threat
A recent supply chain attack has led to the defacement of 44 repositories belonging to Aqua Security. On March 22, 2026, researchers discovered that malicious images of Trivy were uploaded to Docker Hub, which contained infostealer malware. Versions 0.69.4 to 0.69.6 were particularly dangerous, as they included code from the TeamPCP group, a known cloud-native threat actor. This breach highlights the vulnerabilities in the software supply chain and the potential risks developers face when using compromised container images.
The attackers used a stolen service account token to gain access, allowing them to rename and deface all repositories in Aqua Security's internal GitHub organization. This incident marks a significant escalation in TeamPCP’s activities, showcasing their ability to execute a fully automated attack in a matter of minutes.
Who's Behind It
The attack was orchestrated by TeamPCP, also known as DeadCatx3, PCPcat, ShellForce, and CanisterWorm. This group has been active in 2025 and 2026, focusing on Docker API and Kubernetes exploitation, along with various forms of cyberattacks including supply chain attacks and ransomware. They have a history of leveraging GitHub Actions to compromise CI systems, making them a formidable threat in the cloud-native ecosystem.
Prior to the attack, TeamPCP tested the stolen token's capabilities by creating and deleting a branch, a tactic designed to avoid detection. This methodical approach allowed them to map out repositories and prepare for the main attack, which involved renaming and defacing the repositories in a matter of minutes.
Tactics & Techniques
The attack followed a clear sequence of events. First, TeamPCP compromised the Trivy GitHub Actions to steal credentials from CI systems, including tokens and keys. They then captured a service account token with admin access across multiple organizations. After confirming their access by mimicking normal behavior, they executed their plan, resulting in the rapid defacement of Aqua Security's repositories.
This incident is particularly concerning because it exposes internal tools and infrastructure, meaning any stored secrets or credentials should now be considered compromised. The automated nature of the attack also indicates a high level of sophistication and planning on the part of TeamPCP.
Defensive Measures
To protect against such threats, organizations should ensure that their CI/CD pipelines are secure. This includes implementing strict access controls and regularly rotating service account tokens. Additionally, monitoring for unusual activity, such as unexpected repository changes or suspicious API calls, can help detect potential breaches early.
Developers using container images should remain vigilant and verify the integrity of the images they pull from repositories like Docker Hub. Utilizing tools that can scan for vulnerabilities and monitor for compromised images is essential in maintaining a secure development environment. By taking these proactive measures, organizations can better defend against supply chain attacks and safeguard their critical assets.
Security Affairs