TeamPCP hacking group is actively spreading worm-enabled malware via npm packages, compromised GitHub accounts, and Trivy supply-chain attack.
The hacking group TeamPCP, active since December, has escalated to a full supply-chain attack by compromising Aqua Security's GitHub account and poisoning virtually all versions of the Trivy vulnerability scanner. The worm-enabled malware auto-propagates by scanning infected machines for npm access tokens and publishing malicious versions of available packages. A secondary payload acts as a data wiper specifically targeting Iranian-based machines. Researchers at Flare first observed the group building distributed proxy/scanning infrastructure to enable ransomware, data exfiltration, and crypto mining at scale.
Trivy is embedded in thousands of CI/CD pipelines, and virtually every version is now compromised. Any machine that ran a Trivy scan and held npm credentials may have already published poisoned package versions to the public registry. This is a worm — it doesn't wait for human action, it spreads automatically through legitimate developer toolchains.
Immediately audit your npm access tokens: run `npm token list` and revoke all tokens issued before today, then check your published package version history on npmjs.com for any releases you didn't author.
Suggested exercise · not independently tested. Access requirements and costs may vary.
Open your terminal on any machine that has run Trivy or CI/CD pipelines recently
Run: `npm token list` — look for any tokens you don't recognize or can't attribute to a specific workflow
Run: `npm view your-package-name time` replacing your-package-name with each package you maintain — look for version timestamps you didn't create
If unknown versions exist, run `npm unpublish your-package-name@suspicious-version` immediately and rotate all tokens with `npm token revoke <token-id>`
Tags