By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.
18px_cookie
e-remove
Blog
Glossary
Customer Story
Video
eBook / Report
Solution Brief

A Practitioner’s Guide to Responding to the TeamPCP Supply Chain Attacks

Investigating, remediating, and hardening your environment in the wake of the TeamPCP campaign — from an organization that went through the process itself.

Investigating, remediating, and hardening your environment in the wake of the TeamPCP campaign — from an organization that went through the process itself.

Investigating, remediating, and hardening your environment in the wake of the TeamPCP campaign — from an organization that went through the process itself.

Written by
No items found.
Published on
March 27, 2026
Updated on
March 27, 2026
Topics

Investigating, remediating, and hardening your environment in the wake of the TeamPCP campaign — from an organization that went through the process itself.

Investigating, remediating, and hardening your environment in the wake of the TeamPCP campaign — from an organization that went through the process itself.

The TeamPCP attacks have triggered widespread incident response efforts across the industry, evolving in just six days from a compromised GitHub Action in the Trivy repository into a multi-vector supply chain campaign impacting npm packages, Python libraries, container images, IDE extensions, and CI/CD pipelines across thousands of organizations, all from a single stolen token. The blast radius continues to grow, with impacts spanning LiteLLM (3.6M daily downloads), over 60 npm packages via the CanisterWorm, Checkmarx’s KICS GitHub Actions, and dozens of defaced repositories, alongside the discovery of a targeted wiper component.

This isn’t an isolated event but part of a broader evolution in supply chain attacks, from SolarWinds to Codecov to today, each becoming faster, more automated, and harder to contain. As a vendor operating in this ecosystem, Endor Labs is actively assessing exposure and reinforcing its own defenses, and this guide shares a practical, real-world framework for responding to such incidents across investigation, remediation, and prevention.

Free Assessment

What's running in your GitHub Actions?

Find out More

The Challenge

The Solution

The Impact

Welcome to the resistance
Oops! Something went wrong while submitting the form.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.