PYSEC-2026-207

PYSEC-2026-207 · durabletask 1.4.1, 1.4.2, and 1.4.3 contain malicious code distributed via a compromised maintainer account

Cette page présente des faits issus de sources publiques. Consultez l’avis original avant toute mise à jour.

`durabletask` versions 1.4.1, 1.4.2, and 1.4.3 were published on 2026-05-19 within a 35-minute window through a compromised PyPI maintainer account and contained malicious code. On import, the package fetched a remote payload (`rope.pyz`) from an attacker-controlled host and executed it. The payload was a credential-theft framework that interrogated cloud instance metadata (AWS/Azure/GCP) and secret stores, harvested Kubernetes service-account tokens, HashiCorp Vault tokens, and credentials from known filesystem paths, attempted to brute-force password manager vaults. Anything obtained was exfiltrated to command-and-control infrastructure with a GitHub dead-drop fallback. It established persistence via a systemd unit (`pgsql-monitor.service`) and included a geo-targeted destructive wiper. Indicators of compromise: - Dropped payload: rope.pyz (sha256 069ac1dc7f7649b76bc72a11ac700f373804bfd81dab7e561157b703999f44ce) - Primary C2: check.git-service[.]com (160.119.64.3) - Secondary C2: t.m-kosche[.]com (185.95.159.32) - Persistence unit: pgsql-monitor.service The affected releases have been removed from PyPI. The known-good versions remain available. `durabletask` version 1.5.0 has been released by the maintainers. This campaign is likely attributable to the threat actor tracked as TeamPCP, based on shared infrastructure and payload overlap with prior supply chain compromises (including the @antv and guardrails-ai waves).

Publication

2026-06-09T19:34:23Z

Mise à jour

2026-06-28T22:30:06.341345236Z

Pile logicielle: python

Vérifiez votre serveur →