PyPI

The durabletask PyPI Supply Chain Attack

Updated 5 Oct 2026 · Incident date 19 May 2026

durabletask 1.4.1, 1.4.2 and 1.4.3 on PyPI downloaded and ran a hidden secret-stealing program on import, within 35 minutes on 19 May 2026.

Security vendors link the campaign to the TeamPCP group. Only Linux systems run the dropper, according to Phoenix Security.

What happened

An attacker used stolen GitHub credentials to take a PyPI token from the repository secrets and publish three poisoned releases.

  • The dropper runs at import time. It downloads rope.pyz and starts it as a detached background process.
  • The second stage collects AWS, Azure and GCP credentials, Kubernetes secrets, password manager data and AI developer tool configuration.
  • StepSecurity counts more than 90 developer tool configurations. It says the code skips systems with a Russian locale.
  • Phoenix reports that the worm spreads through AWS SSM SendCommand and kubectl exec.

Phoenix Security gives the window as 16:19 to 16:54 UTC on 19 May 2026. PyPI yanked the three versions.

Affected versions

  • durabletask 1.4.1
  • durabletask 1.4.2
  • durabletask 1.4.3
  • Version 1.4.0 is the last clean release named by Phoenix Security.

Indicators of compromise

  • Payload file /tmp/managed.pyz.
  • Infection markers ~/.cache/.sys-update-check and ~/.cache/.sys-update-check-k8s.
  • Persistence file pgmonitor.py in /usr/bin/ or ~/.local/bin/.
  • Domains check.git-service[.]com and t.m-kosche[.]com.
  • Subnet 83.142.209.0/24.
  • Download path /rope.pyz.

How to check

Check which durabletask version a Python environment holds without running the package.

pip show durabletask

Look for the payload and marker files.

ls -la /tmp/managed.pyz ~/.cache/.sys-update-check ~/.cache/.sys-update-check-k8s 2>/dev/null

What to do now

  1. Pin to durabletask==1.4.0. Remove 1.4.1, 1.4.2 and 1.4.3 from every environment and image.
  2. If a bad version was imported, treat the host as compromised. Look for the files above.
  3. Rotate cloud credentials, GitHub tokens, SSH keys and Kubernetes secrets that the host had access to.
  4. Block the two C2 domains at egress. Audit AWS SSM and Kubernetes activity for commands you did not run.

What Vigilance would show

These examples show an install hold and the corresponding owner report.

Example install message

Vigilance blocked `durabletask` 1.4.1. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

durabletask 1.4.1

A Microsoft workflow library gained code that, on import, downloaded and ran a hidden secret-stealing program.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

How popular is durabletask?

Phoenix reports about 417,000 monthly downloads.

Why does this page list no file hashes?

The sources list different file hashes for the three versions. Use the hashes in the vendor reports.

Sources

  1. phoenix.security/teampcp-github-breach-durabletask-pypi-supply-chain-wave-four-2026/
  2. stepsecurity.io/blog/5-supply-chain-attacks-in-48-hours-why-securing-one-layer-is-not-enough
  3. wiz.io/blog/durabletask-teampcp-supply-chain-attack

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library