Skip to content

TeamPCP

Threat actor group tied to the Shai-Hulud npm supply-chain attacks, stealing credentials and secrets from developer build pipelines.

Known aliases

  • Altered Spider
  • PCPcat
  • @pcpcats
  • PCPsh
  • Persy_PCP
  • ResoluteXBF
  • ShellForce
  • Team PCP
  • tpcp
  • UNC6780

Current stories

securityConfirmed16 publishers

AFP sizes the Shai-Hulud syndicate's take at more than 500,000 credentials

Two men arrested in Australia this week are alleged TeamPCP members. The AFP estimate filed alongside the case puts the worm's take at more than 500,000 credentials and 300GB of data, and that scale makes token lifetime the live question.

Perspective Coverage

16 publishers
Builder
Builder 29%
Operator
Operator 56%
Investor
Investor 15%

Reality

Evidence62
Adoption68
Hype gap+30
Incentives58
Confidence70
securityOne report1 publisher

TeamPCP's package attacks reused the stolen-token techniques of S1ngularity and Shai-Hulud

Two TeamPCP-linked actors are under arrest after package compromises that ReversingLabs says caused a suspected hundreds of millions of dollars in damages. The waves since September 2025 began with a stolen publishing credential and reached victims through updates their own pipelines installed.

Reality

Evidence35
Adoption
Not scored
Hype gap+25
Incentives75
Confidence35
productOne report1 publisher

Google's undercover analyst watched TeamPCP poison packages from inside its core chat

Austin Larsen of Google's threat intelligence group says a Mandiant persona sat in TeamPCP's inner circle from almost the start of the campaign. For the companies the group breached, that infiltration was the warning system.

Reality

Evidence55
Adoption
Not scored
Hype gap+20
Incentives60
Confidence55
buildOne report1 publisher

GitHub lost 3,800 internal repos to code running with its editor's permissions

A dev.to writeup traces roughly 3,800 exfiltrated GitHub repositories to one trojanised Nx Console install from the official Marketplace, where the sandbox that would have contained it has been an open feature request since 2018.

Publishers:dev.to

Reality

Evidence42
Adoption28
Hype gap+18
Incentives62
Confidence45
productOne report1 publisher

An ex-employee's live OAuth token let strangers copy 170 CrowdSec repositories in nine minutes

TeamPCP's npm compromise of TanStack reached CrowdSec through a departed employee's laptop, and the company learned its private repositories had been copied only when the code surfaced on a dark web forum in September.

Publishers:devops.com

Reality

Evidence58
Adoption55
Hype gap+12
Incentives72
Confidence60
buildOne report1 publisher

An agent now picks the packages the person prompting it will never see

GitHub's volume counters and Chainguard's account of agent-written code both point at dependency review as the step nobody is doing. Mandiant estimates mean time-to-exploit at minus seven days in 2025.

Publishers:thenewstack.io

Reality

Evidence43
Adoption55
Hype gap+27
Incentives76
Confidence42
securityOne report1 publisher

Google put an undercover analyst inside TeamPCP's inner circle during its 1,000-company campaign

TeamPCP hijacked developer accounts, poisoned hundreds of programs and released a worm to automate the spread. Google says the inside access let it warn victims, revoke stolen credentials and help patch an AI-developed zero-day.

Publishers:scworld.com

Reality

Evidence32
Adoption38
Hype gap+22
Incentives68
Confidence30
securityOne report1 publisher

Google clocks TeamPCP standing up a mass credential-harvesting campaign in under six hours

GTIG's 2026 accounting traces one crew from package-registry compromises on PyPI, npm and Docker Hub to agent instructions that planned and ran the campaign, then out to public malware releases anyone can reuse.

Publishers:securityweek.com

Reality

Evidence48
Adoption45
Hype gap+22
Incentives72
Confidence45
securityOne report1 publisher

AFP, FBI and Western Australia Police arrest two men over the TeamPCP npm attacks

Aikido says the pair, both in their early 20s, ran TeamPCP's npm supply chain campaigns with a worm they cloned from Shai-Hulud. Whoever wrote the original is still unidentified, and the code is still published.

Publishers:aikido.dev

Reality

Evidence41
Adoption44
Hype gap−6
Incentives63
Confidence45
securityConfirmed3 publishers

Attacker agents ran a mass credential harvest from inside the victim's own cloud in six hours

Mandiant traced the Q2 2026 campaign to an AI coding chatbot, one prompt and a set of agent instructions that ran the scanning pipeline, fixed its own errors and rotated IPs with nobody at the keyboard.

Perspective Coverage

3 publishers
Builder
Builder 30%
Operator
Operator 57%
Investor
Investor 13%

Reality

Evidence58
Adoption62
Hype gap+24
Incentives70
Confidence66
buildOne report1 publisher

A backdoored LiteLLM package cleared 119,000 downloads before PyPI quarantined it

Install hooks and .pth files execute before your first import, which puts the useful controls in resolver precedence and environment scope rather than in a test suite that passes either way.

Publishers:dev.to

Reality

Evidence34
Adoption58
Hype gap+20
Incentives55
Confidence33
securityOne report1 publisher

Malicious litellm PyPI releases tied to Trivy scan dependency bypassed official CI/CD

Two litellm releases that never came out of the project's CI harvested SSH keys and cloud credentials from every host that installed them. litellm traces the entry point to the Trivy scanner in its own pipeline.

Publishers:github.com

Reality

Evidence48
Adoption
Not scored
Hype gap+12
Incentives78
Confidence42
securityOne report1 publisher

AFP charges two men near Perth over the self-spreading worm behind the TeamPCP compromises

Two suspects in Western Australia are in custody over the supply-chain worm that hit Trivy, KICS, LiteLLM and Telnyx. The 500,000 credentials it harvested stay valid until someone rotates them. Only 78,000 have surfaced publicly.

Publishers:news.risky.biz

Reality

Evidence50
Adoption62
Hype gap+14
Incentives45
Confidence52
securityOne report1 publisher

TeamPCP poisoned more than 1,000 packages with tactics anyone can copy

Google places the spree with a single operator in South Africa, which makes one arrest plausible, while Palo Alto Networks counts three core members. Either way, the packages moved because almost nobody checks what they ingest.

Publishers:cyberscoop.com

Reality

Evidence58
Adoption74
Hype gap+10
Incentives68
Confidence55
buildOne report1 publisher

Every one of thirteen named 2025-26 incidents ran on a credential that still worked

Anthropic, Sysdig, Unit 42 and GitGuardian describe the same shape of failure, which puts the interesting number on your side of the fence: how long an issued token keeps working after it leaves your control.

Publishers:dev.to

Reality

Evidence27
Adoption44
Hype gap+37
Incentives71
Confidence57
securityOne report1 publisher

Jackal IV's 58 arrests cover under a third of the suspects INTERPOL identified

A week of takedowns removed people and froze assets across five separate actions, while the kit that manufactures the stolen Microsoft 365 sessions those crews depend on still sells on Telegram for $320 a month.

Publishers:sentinelone.com

Reality

Evidence28
Adoption52
Hype gap+30
Incentives58
Confidence36
scienceOne report1 publisher

TeamPCP hid its infostealer inside the scanners that audit everyone else's code

Unit 42 says the group backdoored Trivy, KICS, LiteLLM and Telnyx's Python SDK, tools that run inside CI with the privileges needed to reach production secrets, which is also why the headline counts deserve a slow read.

Reality

Evidence55
Adoption58
Hype gap+32
Incentives78
Confidence48
scienceOne report1 publisher

A backdoored litellm release turns every CI job that installed it into a credential incident

Datadog's investigation puts genuine PyPI releases of litellm and telnyx inside the same campaign that poisoned Trivy on March 19, which makes the unit of remediation the secrets the build could see rather than the version pin.

Publishers:securitylabs.datadoghq.com

Reality

Evidence71
Adoption62
Hype gap−8
Incentives58
Confidence64
securityOne report1 publisher

Oligo dates the crew behind ShadowRay 2.0's self-propagating botnet back to 2020

The Ray, Docker and Redis endpoints hijacked in ShadowRay 2.0 were worked by operators Oligo now ties to TA-NATALSTATUS activity from 2020, which makes the AI-cluster worm a tooling upgrade on an old farm.

Publishers:oligo.security

Reality

Evidence55
Adoption45
Hype gap+25
Incentives75
Confidence50

Earlier coverage