Back to all lessons
Awareness Lessons
2 months ago

TeamPCP's Multi-Year OSS Attack Campaign Exposes Supply Chain Blind Spots

The TeamPCP threat actor has been covertly targeting open-source software ecosystems since at least 2020, operating under multiple aliases and evading attribution for years. Their exploitation of vulnerabilities like ShadowRay — combined with AI-assisted payload adaptation — demonstrates how sophisticated adversaries can evolve faster than defenders detect them. The group's suspected self-propagating botnet targeting AI infrastructure signals a dangerous escalation in supply chain threats. Organizations relying on open-source components without rigorous vetting and monitoring are unknowingly inheriting long-standing, active threat vectors. This case underscores that threat actors with deep operational histories can remain invisible without proactive threat intelligence and continuous dependency monitoring.

Tactical Insight

Immediate actions

  • Audit all open-source dependencies in your software supply chain for known vulnerabilities, including ShadowRay and related CVEs exploited by TeamPCP.
  • Subscribe to threat intelligence feeds that track OSS-targeting threat actors and cross-reference aliases such as TA-NATALSTATUS and IronErn.
  • Scan AI/ML infrastructure environments specifically for indicators of compromise associated with botnet activity.

Long-term improvements

  • Implement a Software Bill of Materials (SBOM) process to maintain full visibility into every open-source component used across your organization.
  • Establish a formal OSS vetting and approval workflow before any open-source package is introduced into production pipelines.
  • Invest in threat actor attribution capabilities or partner with threat intelligence providers to detect multi-alias adversaries earlier.

Detection measures

  • Deploy behavioral monitoring on AI infrastructure to identify anomalous lateral movement or self-propagating botnet patterns.
  • Enable comprehensive logging of package installations, dependency updates, and build pipeline activity to detect supply chain tampering.
  • Set automated alerts for packages associated with known malicious maintainers or flagged repositories.