Threat group profile

TeamPCP

Also known as PCPCat, DeadCatx3, ShellForce

The US FBI (July 2026) describes TeamPCP as a cyber criminal group behind large-scale software supply chain compromises of widely used developer and security tools.

In short

The US FBI (July 2026) describes TeamPCP as a cyber criminal group behind large-scale software supply chain compromises of widely used developer and security tools. Australian and US authorities announced arrests and an indictment linked to the group in August 2026, and MITRE ATT&CK describes it as active since at least September 2025.

Profile MapThreat Group
  1. Names6names in public reportsTeamPCP · PCPCat · ShellForce
  2. Sectors9named as targetsBuild pipelines · LiteLLM · AWS, GCP, Azure
  3. Techniques14in the attack chainResource Development · Initial Access · Execution
  4. Tools5tools and malware listedTeamPCP Cloud Stealer · CanisterWorm · Mini Shai-Hulud

In one minute

Who they are
The FBI (FLASH of 2 July 2026) calls TeamPCP a cyber criminal group. MITRE ATT&CK describes it as financially motivated and cloud-native, active since at least September 2025. CERT-EU, the German BSI and the US Department of Justice (August 2026) name it too; CERT-EU says "reportedly" and BSI says the group is said to be behind the attacks.
Who they target
Software developers and the build pipelines (CI/CD) they use. The FBI says the group modified Trivy, KICS, LiteLLM and the Telnyx Python SDK. CERT-EU says the Trivy compromise gave access to a European Commission cloud account, with data of at least 29 other EU entities possibly affected.
How they usually get in
The sources describe poisoned software in trusted places: GitHub Actions tags, package registries such as npm and PyPI, Docker Hub and IDE extensions, plus stolen tokens and cloud credentials. Malware then steals secrets and, in some cases, spreads by itself.
What stands out
It attacks the tools that defenders and developers trust, so one stolen secret feeds the next compromise. The FBI also says the group extorts victims and works with other criminal groups. The Australian Federal Police charged two men on 26 August 2026 and the US indicted one; the investigation is ongoing.
What to do first
Pin GitHub Actions to full commit hashes, rotate every secret a pipeline could reach if it ran a named bad version, and search your GitHub organization for repositories called tpcp-docs or docs-tpcp, as the FBI and BSI advise.

Names

Public reports use several names for this activity.

Names used for TeamPCP
NameWhere it appears
TeamPCP MITRE ATT&CK G1056 (group name); FBI FLASH of 2 July 2026; BSI warning of 26 March 2026; CERT-EU; US Department of Justice press release[1, 5, 6, 8, 12]
PCPCat MITRE ATT&CK G1056 Associated Groups[1]
ShellForce MITRE ATT&CK G1056 Associated Groups[1]
DeadCatx3 MITRE ATT&CK G1056 Associated Groups[1]
SHADOW-WATER-058 MITRE ATT&CK G1056 Associated Groups[1]
UNC6780 MITRE ATT&CK G1056 Associated Groups[1]

Who says so

Attribution is a judgment by the body named. It is shown here as attributed, not as proven fact.

  • BSI (Germany) 26 March 2026

    In its warning on the Trivy attack, said the group TeamPCP is said to stand behind the supply chain attacks, which it described as touching GitHub Actions, Docker Hub, npm (CanisterWorm), OpenVSX and PyPI.[12]

  • CERT-EU 1 April 2026

    Cyber Brief 26-04 calls TeamPCP a cybercrime actor that reportedly compromised Trivy, LiteLLM and the Telnyx Python package. The brief says its attributions only reflect public reporting, not CERT-EU's stance.[9]

  • CERT-EU 2 April 2026

    Assessed with high confidence that the European Commission cloud breach started with the Trivy supply-chain compromise, which it describes as publicly attributed to TeamPCP.[8]

  • CERT-EU 2 June 2026

    Cyber Brief 26-06 says TeamPCP's Mini Shai-Hulud worm compromised over 160 npm and PyPI packages, and that copycat actors adopted the malware after its source code was published.[10]

  • FBI 2 July 2026

    FLASH-20260702-01 describes TeamPCP as a cyber criminal group that carried out large-scale software supply chain compromises, and lists its malware and indicators. Coordinated with CISA.[5]

  • MITRE ATT&CK 16 July 2026

    Describes TeamPCP (G1056) as a financially motivated, cloud-native group active since at least September 2025. Group page version 1.0, created 16 July 2026.[1]

  • US Department of Justice 27 August 2026

    Announced an indictment for cyberattacks conducted in spring 2026 "under the moniker TeamPCP". The indictment was filed on 25 August and unsealed on 26 August.[6]

  • Australian Federal Police with FBI 27 August 2026

    Charged two men over an alleged cybercrime syndicate. An FBI official said the men are allegedly members of the cybercriminal group TeamPCP.[7]

  • CERT-EU 3 September 2026

    Cyber Brief 26-09 reports the Australian arrests of two alleged members of TeamPCP.[11]

Where sources differ

Sources differ in how firmly they name the group. CERT-EU writes "reportedly" and says its briefs only reflect public reporting, and it describes the Trivy attribution as made publicly by others. The BSI says the group is said to be behind the attacks. The FBI states it as the subject of its FLASH. The US Department of Justice says the attacks were carried out "under the moniker TeamPCP", and the Australian release names the group only through an FBI quote. An indictment and charges are allegations until proven in court. The CISA catalog entry for the Trivy flaw does not name any actor.

Who they target

Sectors

  • Build pipelinesThe FBI says the group modified widely used developer and security tools that are built into CI/CD pipelines, cloud infrastructure and security workflows.[5]
  • npm, PyPI, Docker Hub, GitHub Actions, OpenVSXThe BSI lists these as the ecosystems hit by the campaign in March 2026. MITRE adds VS Code extensions.[1, 12]
  • LiteLLMCERT-EU says TeamPCP reportedly compromised the LiteLLM Python package on PyPI (versions 1.82.7 and 1.82.8 per the BSI).[9, 12]
  • AWS, GCP, AzureThe FBI says the CanisterWorm malware harvests cloud access tokens and credentials for these three providers.[5]
  • European Commission web hostingCERT-EU says a stolen AWS secret from the Trivy compromise led to theft of data tied to up to 71 clients of the europa.eu hosting service, including at least 29 other EU entities.[8]
  • Cluster secretsThe FBI lists Kubernetes secrets and service account tokens among the data taken. MITRE describes use of the Kubernetes API for lateral movement.[1, 5]
  • Downstream organizationsThe AFP says infected software reached organizations across government, academia and the private sector, potentially over 1000 organizations worldwide.[7]
  • GitHub internal repositoriesCERT-EU says TeamPCP reportedly claimed theft of about 4,000 private repositories, and GitHub confirmed about 3,800 were breached via a malicious VS Code extension.[10]
  • npm maintainer accountsThe FBI says the group takes over npm publishing accounts by targeting stale or expired recovery email domains.[5]

Operations timeline

Each entry is attributed to the group by the sources cited.

  1. September 2025

    Earliest activity per MITRE

    MITRE ATT&CK describes TeamPCP as active since at least September 2025, first focused on ransomware and cryptocurrency theft.[1]

  2. Late February 2026

    Start of the Trivy attack

    The Trivy maintainers say the March incident continued an attack that began in late February 2026. Credential rotation after the 1 March disclosure was not atomic, so access may have remained.[15]

  3. 19 March 2026

    Trivy and GitHub Actions compromise

    The Trivy maintainers report a malicious Trivy v0.69.4 release and force-pushed tags on 76 of 77 trivy-action versions and all 7 setup-trivy versions. CERT-EU says the same day a stolen AWS secret reached a European Commission cloud account.[8, 15]

  4. 22 March 2026

    Docker Hub images

    The Trivy maintainers report malicious Trivy v0.69.5 and v0.69.6 images on Docker Hub.[15]

  5. 24 March 2026

    LiteLLM PyPI compromise

    CERT-EU says TeamPCP reportedly published malicious LiteLLM versions 1.82.7 and 1.82.8 to PyPI. The BSI says the attack on Trivy presumably led to it.[9, 12]

  6. 26 March 2026

    Trivy flaw added to CISA catalog

    CISA lists CVE-2026-33634, an embedded malicious code flaw in Trivy, as exploited. The same day the BSI published its warning.[12, 13]

  7. 27 March 2026

    Telnyx PyPI package

    CERT-EU says TeamPCP reportedly uploaded malicious Telnyx versions 4.87.1 and 4.87.2 to PyPI.[9]

  8. 28 March 2026

    Commission data leaked

    CERT-EU says the extortion group ShinyHunters published the data taken from the Commission account on its leak site.[8]

  9. 11 May 2026

    TanStack npm worm

    CERT-EU says TeamPCP's Mini Shai-Hulud compromised over 160 npm and PyPI packages. TanStack's postmortem reports 84 malicious versions across 42 packages on that day.[10, 18]

  10. 17 May 2026

    Source code published

    CERT-EU says TeamPCP published its own malware code to GitHub and independent actors began copying it.[10]

  11. 19 May 2026

    GitHub internal repositories

    CERT-EU says GitHub began investigating access to internal repositories after an employee installed a malicious VS Code extension; TeamPCP reportedly claimed the theft.[10]

  12. 27 May 2026

    TanStack flaw added to CISA catalog

    CISA lists CVE-2026-45321, which allowed malicious TanStack versions to be published to npm.[14]

  13. 2 July 2026

    FBI FLASH

    The FBI publishes FLASH-20260702-01 with tactics, malware names and indicators.[5]

  14. 26 August 2026

    Arrests in Australia

    The AFP charges two Western Australian men with a combined 14 offenses. The US indictment, filed 25 August, is unsealed.[6, 7]

Government actions

Indictments, sanctions and advisories that name the group or its alleged members.

Government actions about TeamPCP
DateWhoWhat
26 Mar 2026 CISA Known exploited vulnerabilities alertAdded CVE-2026-33634 (Trivy embedded malicious code) to its catalog. The entry does not name an actor.[13, 14]
26 Mar 2026 BSI Security warning (BITS-V 2026-237970-1032)Warned of the Trivy compromise, named TeamPCP as said to be behind it, and advised returning to clean versions and rotating secrets.[12]
1 Apr 2026 CERT-EU Cyber Brief 26-04Reported TeamPCP's Trivy, LiteLLM and Telnyx compromises, with the caveat that it reflects public reporting.[9]
2 Apr 2026 CERT-EU Blog on the European Commission cloud breachAssessed with high confidence that Trivy was the initial access and listed actions for defenders.[8]
27 May 2026 CISA Known exploited vulnerabilities alertListed CVE-2026-45321 (TanStack) in its catalog. The entry does not name an actor.[14]
2 Jun 2026 CERT-EU Cyber Brief 26-06Reported the Mini Shai-Hulud worm and its copycats.[10]
2 Jul 2026 FBI (coordinated with CISA) FLASH-20260702-01Described TeamPCP's tactics and malware, listed indicators and set out recommendations.[5]
25 Aug 2026 US Department of Justice, Northern District of California IndictmentIndicted one man on conspiracy and computer fraud charges over TeamPCP attacks; filed 25 August, unsealed 26 August, announced 27 August.[6]
26 Aug 2026 Australian Federal Police with Western Australia Police and FBI Arrests and chargesSearched properties in Perth, arrested two men and charged them with 14 offenses in total; further arrests were not ruled out.[7]

How they get in

Techniques reported for this group, by MITRE ATT&CK tactic.

Resource Development

  • Acquire Infrastructure: Domains T1583.001

    Registered look-alike domains of victim sites such as scan.aquasecurtiy[.]org to hide command and control.[1]

Initial Access

  • Supply Chain Compromise: Compromise Software Dependencies and Development Tools T1195.001

    Attacked npm, VS Code, Docker and PyPI to compromise many software packages.[1]

  • Valid Accounts: Cloud Accounts T1078.004

    Used stolen GitHub and package registry credentials, including privileged service accounts, to inject code into pipelines.[1]

  • Exploit Public-Facing Application T1190

    Exploited GitHub Actions misconfigurations and CVE-2026-33634 in Trivy, and CVE-2025-55182 against cloud endpoints.[1]

Execution

  • Poisoned Pipeline Execution T1677

    Injected credential-stealing payloads into trusted CI/CD workflows and packages.[1]

Persistence

  • Create or Modify System Process: Systemd Service T1543.002

    Used a systemd user service to keep malware running.[1]

Defense Evasion

  • Masquerading: Match Legitimate Resource Name or Location T1036.005

    Cloned commit metadata for impostor commits and used legitimate file names for payloads.[1]

  • Obfuscated Files or Information: Steganography T1027.003

    Hid payloads in the frame data of WAV audio files.[1]

Credential Access

  • Steal Application Access Token T1528

    Stole access tokens from cloud and developer environments.[1]

  • Credentials from Password Stores: Cloud Secrets Management Stores T1555.006

    Took cloud secrets from AWS, GCP and Azure.[1]

  • Unsecured Credentials: Private Keys T1552.004

    Extracted SSH and GPG keys from victim environments.[1]

Lateral Movement

  • Use Alternate Authentication Material: Application Access Token T1550.001

    Used stolen tokens to inject code into pipelines and take data from cloud and container environments.[1]

Impact

  • Data Encrypted for Impact T1486

    Deployed ransomware and announced partnerships with ransomware groups.[1]

  • Financial Theft T1657

    Mined and stole cryptocurrency, partnered with extortion groups and sold leaked code.[1]

Tools and malware

  • TeamPCP Cloud Stealer Credential stealer

    MITRE describes it as a filesystem stealer that harvests, encrypts and sends out credentials from over 50 sensitive paths, used in March 2026. The FBI lists the same tool as SANDCLOCK.[2, 5]

  • CanisterWorm Self-propagating worm

    Uses npm credentials to infect packages. MITRE notes a wiper component and command and control through an Internet Computer blockchain canister.[3, 5, 12]

  • Mini Shai-Hulud Supply chain worm

    MITRE describes a credential stealer and self-replicating worm derived from Shai-Hulud that uses stolen npm and GitHub OIDC tokens. The FBI calls it cross-ecosystem (npm and PyPI).[4, 5, 10]

  • Miasma Worm (variant)

    The FBI describes it as a variant of Mini Shai-Hulud that spreads across registries such as npm and PyPI and poisons configuration files.[5]

  • TruffleHog Secret-scanning tool

    CERT-EU says the actor launched this legitimate scanner against the Commission account to look for more secrets.[8]

Detection and defense

  1. Pin GitHub Actions to commit hashes

    Use full commit SHA hashes instead of mutable version tags, as the FBI, BSI and CERT-EU advise.

    Counters T1195.001 T1677

  2. Rotate pipeline secrets

    Treat secrets reachable by a bad build as stolen. Rotate CI/CD secrets, publishing tokens and cloud keys, and review new AWS access keys, as CERT-EU and the FBI advise.

    Counters T1528 T1555.006 T1078.004

  3. Hunt for the exfiltration marker

    Search your GitHub organization for repositories named tpcp-docs or docs-tpcp, which the FBI and BSI link to the worm.

    Counters T1550.001 T1195.001

  4. Limit token power

    Give CI/CD accounts and registry tokens the least access they need so a stolen token cannot spread across repositories.

    Counters T1550.001 T1078.004

  5. Require phishing-resistant MFA

    Apply it to all accounts that can publish to code repositories or package registries, and audit maintainer recovery email domains.

    Counters T1078.004 T1190

  6. Watch runner network traffic

    Use runtime monitoring on CI/CD to spot unexpected outbound connections, such as look-alike domains or Cloudflare tunnels.

    Counters T1583.001 T1677

  7. Delay new package versions

    Set a minimum package age, for example 7 days, so freshly published bad versions are not installed at once.

    Counters T1195.001

  8. Keep an inventory and log pipelines

    List third-party tools and packages in use, log CI/CD activity centrally, and verify artifact signatures and hashes before release.

    Counters T1195.001 T1553.002

What Brandefense can do

  • Cyber Threat Intelligence

    Follow new government advisories on TeamPCP, the names and tools the sources attribute to it, and any targeting of your sector or software supply chain.

  • Dark Web Monitoring

    Watch for leak-site posts and forum offers that mention your organization, as the FBI says the group publishes victim names and threatens to release stolen data.

  • External Attack Surface Management

    See which of your public code, package and cloud assets are exposed, including look-alike domains that mimic your tools.

  • Phishing Monitoring & Domain Abuse

    Spot look-alike domains of your projects, the kind MITRE describes the group registering to hide command and control.

Questions

Who is TeamPCP?

The FBI (2 July 2026) describes TeamPCP as a cyber criminal group behind large-scale software supply chain compromises. MITRE ATT&CK describes it as financially motivated and active since at least September 2025. CERT-EU says "reportedly" in its briefs.

Which software did TeamPCP compromise?

The FBI says it modified Trivy, KICS, LiteLLM and the Telnyx Python SDK. CERT-EU and MITRE also report the Mini Shai-Hulud worm, which hit TanStack and other npm and PyPI packages in May 2026.

Has anyone been charged?

The Australian Federal Police charged two men on 26 August 2026 and the US Department of Justice announced an indictment of one man on 27 August 2026. These are allegations, and the AFP said the investigation continues.

Did TeamPCP breach a European institution?

CERT-EU assessed with high confidence that a European Commission cloud account was reached through the Trivy supply-chain compromise, which it describes as publicly attributed to TeamPCP. CERT-EU said data tied to at least 29 other EU entities may be affected.

What should a team do first?

Pin GitHub Actions to full commit hashes, rotate secrets that pipelines could reach, and search for repositories named tpcp-docs or docs-tpcp, as the FBI and BSI advise.

In our research

  1. TanStack worm: CI questions every team should ask October 2026
  2. How a Trivy Compromise Reached LiteLLM Releases October 2026

Sources

  1. TeamPCP, Group G1056 MITRE ATT&CK Supports: Group description, associated names, techniques, software, active since at least September 2025
  2. TeamPCP Cloud Stealer, Software S9041 MITRE ATT&CK Supports: Credential stealer description and the associated name SANDCLOCK
  3. CanisterWorm, Software S9042 MITRE ATT&CK Supports: Worm description, wiper component, canister command and control
  4. Mini Shai-Hulud, Software S9043 MITRE ATT&CK Supports: Worm description derived from Shai-Hulud
  5. Cyber Criminal Group TeamPCP (FLASH-20260702-01) FBI, coordinated with DHS/CISA Supports: Group described as cyber criminal, modified tools, malware list, recommendations
  6. Australian Man Indicted For "TeamPCP" Cyberattacks On Software Supply Chain US Department of Justice, Northern District of California Supports: Indictment filed 25 August 2026, unsealed, cascade and extortion allegations
  7. Two WA men charged following AFP-FBI-WAPF disruption of alleged global cybercrime syndicate Australian Federal Police Supports: Arrests, charges, scale estimates, FBI quote naming TeamPCP
  8. European Commission cloud breach: a supply-chain compromise CERT-EU Supports: Commission cloud account breach via Trivy, TruffleHog use, recommendations
  9. Cyber Brief 26-04, March 2026 CERT-EU Supports: Trivy, LiteLLM and Telnyx compromises described as reported
  10. Cyber Brief 26-06, May 2026 CERT-EU Supports: Mini Shai-Hulud, copycats, GitHub repositories
  11. Cyber Brief 26-09, August 2026 CERT-EU Supports: Report of arrests of two alleged members
  12. Trivy: Supply-Chain Angriff fuehrt zu Kompromittierungen in Deutschland (BITS-V 2026-237970-1032) BSI Supports: TeamPCP named, CanisterWorm, LiteLLM versions, measures
  13. CISA Adds One Known Exploited Vulnerability to Catalog (26 March 2026) CISA Supports: CVE-2026-33634 added to the catalogue
  14. Known Exploited Vulnerabilities Catalog (data feed) CISA Supports: Entries for CVE-2026-33634 and CVE-2026-45321
  15. Trivy ecosystem supply chain temporarily compromised (GHSA-69fq-xp46-6x23) Trivy project security advisory Supports: Compromised releases, tags, images and dates
  16. Security Update: Suspected Supply Chain Incident LiteLLM project Supports: Compromised litellm 1.82.7 and 1.82.8, link to the Trivy compromise
  17. Incident Report: LiteLLM/Telnyx supply-chain attacks, with guidance Python Package Index (PyPI) Supports: PyPI account of the LiteLLM and Telnyx releases
  18. Postmortem: TanStack npm supply-chain compromise TanStack project Supports: 84 malicious versions across 42 packages on 11 May 2026