1,000+
packages compromised in under 4 months
A threat group called TeamPCP didn’t need a clever exploit to hit hundreds of millions of downloads. All it needed was the blind trust every dev team already places in “latest version.”
If your development team pulls open-source packages the moment a new version drops, you’ll want to pay attention to this one. A fast-moving threat actor known as TeamPCP just gave the whole industry a hard lesson in why that habit deserves a second look.
According to reporting from CyberScoop, TeamPCP compromised and injected malicious code into more than 1,000 open-source packages in under four months. It’s one of the most aggressive supply-chain campaigns security researchers have tracked, and the compromised packages combined account for hundreds of millions of weekly downloads.
500M
combined weekly downloads affected
15 min
fastest response time once detected
What makes this campaign notable isn’t a clever new exploit. It’s a reminder that most organizations still don’t verify the code flowing into their systems. They trust it by default. TeamPCP didn’t invent this weakness, they just exploited it faster and more aggressively than anyone before.
Why this keeps happening
Modern software isn’t built from scratch, it’s assembled. A typical application pulls in dozens or hundreds of open-source dependencies, each with dependencies of its own, forming a chain that’s nearly impossible to fully audit by hand. When a CI/CD pipeline automatically grabs the “latest” version of a package, it’s optimizing for convenience and patch speed, not for verifying that the latest version is actually safe.
That tradeoff has quietly become one of the biggest attack surfaces in software development, and it’s getting worse as AI coding assistants increasingly select and install packages with little to no human review.
Based on researcher commentary in CyberScoop’s reporting
You don’t need to be a Fortune 500 company to be exposed. If your build pipeline pulls from public package registries, you’re part of the same trust chain.
Five things worth revisiting this week
Pin your dependencies
Auto-updating to “latest” feels safer for patching vulnerabilities, but it also means you inherit a compromise the moment it’s published. Pin versions and update deliberately, after review.
Scan before you merge, not after you ship
Automated dependency scanning should run on every pull request, not on a periodic schedule.
Treat CI/CD credentials like production secrets
Attackers target build systems because they’re a springboard into everything downstream. Rotate secrets on a real schedule, not just after an incident.
Put a human in the loop on AI-assisted changes
If coding agents are recommending or installing packages, someone still needs to sign off before it reaches a shared branch.
Have a rollback plan ready
The fastest-responding organizations in this campaign contained compromised packages within 15 minutes. That kind of speed only happens with a plan rehearsed in advance.
The bigger picture: Managing these moving parts requires a dedicated, security first mindset. which is exactly how we approach infrastructure at ePathUSA.
Company spotlight
TeamPCP’s experience shows why ePathUSA has built security into every engagement since 2005. For nearly two decades, we’ve helped government and commercial organizations modernize systems, secure infrastructure, and adopt cloud and AI technologies while maintaining strong security fundamentals like dependency management, access controls, and secure CI/CD practices.
From Cloud Computing and Software Development to Software Modernization and Artificial Intelligence, ePathUSA partners with teams who want to move fast without trading away security.
If a story like this one has you wondering how your own dependencies and pipelines stack up, our team is happy to talk it through.
