Affected: PyPI: durabletask

**1.4.1**, **1.4.2**, and **1.4.3** of `durabletask` were compromised via a **PyPI maintainer account takeover**. All three malicious versions were published on 2026-05-19 within a 35-minute window (16:19–16:54 UTC). Pin to `<=1.4.0`.

**Attack chain**

- *Stage 1 — Import-time dropper:* on import, the package fetches a second-stage payload `rope.pyz` from `check.git-service.com` (`160.119.64.3`). The TLS certificate for this C2 was issued on 2026-05-16, indicating ~3 days of pre-attack staging. - *Stage 2 — Credential-theft framework:* - AWS / Azure / GCP IMDS interrogation and Secrets Manager dumps - Kubernetes lateral movement via in-cluster service-account tokens - HashiCorp Vault token extraction - Harvesting from 85 known filesystem credential paths - Brute-forcing of local password manager vaults - *Exfiltration:* stolen data is encrypted and shipped to the primary C2, with a **dead-drop fallback** that pushes encrypted blobs as GitHub commits (FIRESCALE-style egress). - *Persistence:* systemd unit `pgsql-monitor.service`. - *Destructive payload:* a **geotargeted wiper** activates on hosts identified as being located in **Israel** or **Iran**.

**Indicators of compromise**

- C2 (primary): `check.git-service.com` — `160.119.64.3` - C2 (secondary): `t.m-kosche.com` — `185.95.159.32` - Dropped payload: `rope.pyz` - Persistence unit: `pgsql-monitor.service`

**Recommended actions**

- Pin `durabletask` to `<=1.4.0`. - Block both C2 domains at network egress. -…