TeamPCP Defaces 44 Repositories in Aqua Security’s Internal GitHub Organization
Summary
OpenSourceMalware reports that TeamPCP defaced 44 repositories in Aqua Security’s internal GitHub organization, allegedly using a stolen service-account token. The repositories were renamed and made public; the token may also access another Aqua organization.
Key points
- The article reports that 44 repositories in Aqua Security’s internal aquasec-com GitHub organization were renamed and given TeamPCP’s defacement message in a roughly two-minute burst on March 22, 2026.
- The affected repositories reportedly included source code, CI/CD configurations, infrastructure, security tooling, and internal knowledge bases; the article says they were exposed publicly.
- OpenSourceMalware attributes the activity with high confidence to a compromised Argon-DevOps-Mgt service-account token, but says the account and attacker IP should be confirmed through audit logs.
- The researchers cite a branch created and deleted on aquasecurity/trivy-plugin-aqua about seven hours earlier as possible testing of the token; they assess the same token may have access to Aqua’s public organization.
- The article links the suspected token theft to TeamPCP’s earlier Trivy GitHub Actions compromise, in which a credential harvester allegedly collected tokens and other secrets from CI runners.
- Recommended actions include revoking service-account tokens, auditing both GitHub organizations, rotating secrets in exposed repositories, checking CI runners, and pinning GitHub Actions to full commit SHAs.
Article Details
- Victim Organization
- Aqua Security
- Incident Type
- Compromise of the aquasec-com GitHub organization followed by scripted defacement and public exposure of 44 internal repositories.
- Incident Date
- 2026-03-22
- Disclosure Date
- 2026-03-22
- Data Types Exposed
- Proprietary source code
- CI/CD pipeline configurations
- Kubernetes operator and infrastructure configurations
- Internal knowledge-base content
- Potential secrets, API keys, or credentials in repositories and CI/CD configurations
- Affected Records
- 44 repositories
- Operational Impact
- All 44 repositories were renamed with a tpcp-docs- prefix and given a defacement description. The article reports that the internal repositories were exposed publicly; it does not specify service disruption.
- Ransom Or Extortion
- None reported
- Claim Status
- confirmed
Indicators of compromise
| Type | Indicator | Context |
|---|---|---|
| DOMAIN | aquasecurtiy[.]org | Listed in the article's IOC section as a domain associated with the threat activity. |
| DOMAIN | tdtqy-oyaaa-aaaae-af2dq-cai[.]raw[.]icp0[.]io | Identified as C2 infrastructure associated with TeamPCP. |
| HOSTNAME | championships-peoples-point-cassette[.]trycloudflare[.]com | Listed as C2 infrastructure associated with TeamPCP. |
| HOSTNAME | investigation-launches-hearings-copying[.]trycloudflare[.]com | Listed as C2 infrastructure associated with TeamPCP. |
| HOSTNAME | scan[.]aquasecurtiy[.]org | Listed in the article's IOC section as threat-related infrastructure. |
| HOSTNAME | souls-entire-defined-routes[.]trycloudflare[.]com | Listed as C2 infrastructure associated with TeamPCP. |
| SHA256 | 18a24f83e807479438dcab7a1804c51a00dafc1d526698a66e0640d1e5dd671a | Hash listed in the article's VirusTotal section as an indicator associated with the threat activity. |
CVE
Threat Actors
CanisterWormIdentified in the article as an alias of TeamPCP.DeadCatx3Identified in the article as an alias of TeamPCP.PCPcatIdentified in the article as an alias of TeamPCP.ShellForceIdentified in the article as an alias of TeamPCP.TeamPCPThreat actor attributed by the article with high confidence to the aquasec-com organization compromise and repository defacement.
Malware
Vendors
Products
GitHub ActionsEvents API points to a compromised service account token — likely stolen during TeamPCP's prior Trivy GitHub Actions compromise — as the attack vector.TraceeImpact: 44 internal repos defaced, renamed, and exposed publicly — including source code for Tracee, internal Trivy forks, CI/CD pipelines, Kubernetes operators, and team knowledge basesTrivyGitHub Events API points to a compromised service account token — likely stolen during TeamPCP's prior Trivy GitHub Actions compromise — as the attack vector.