rootpwn

Threat Intel

TeamPCP Container Ransomware Attack: Elastic D4C Detects Full Attack Chain

TeamPCP launched a multi‑stage container compromise that leveraged a curl‑pipe‑bash download to gain execution, established persistence, and moved laterally across Kubernetes pods. Elastic’s Defend for Containers (D4C) surfaced each phase through runtime telemetry, allowing defenders to map the chain to MITRE ATT&CK. SecOps teams should enable D4C’s pre‑built detections and monitor for the outlined indicators.

What happened

TeamPCP executed a curl‑pipe‑bash payload inside a container to download a script from 67.217.57.240:666 and run it without writing a file. The script then checked for a Kubernetes environment, established persistence, and began moving laterally across pods and nodes.

Impact

The compromise allowed the actor to prepare for large‑scale monetization, including ransomware and mining. Containers that were not isolated could be infected, leading to data exfiltration or service disruption.

Detection with D4C

Elastic’s Defend for Containers surfaced every phase of the chain through runtime telemetry. D4C’s pre‑built detections flag the curl‑pipe‑bash execution, the discovery of Kubernetes APIs, the persistence mechanisms, and the lateral movement patterns, mapping them to MITRE ATT&CK.

Mitigation steps

Enable all D4C detections and review policy rules. Block outbound traffic to unknown IPs, especially on non‑standard ports. Enforce no shell pipelines that download and execute code. Apply least‑privilege on containers and use runtime security controls to detect and stop unexpected exec calls.

TeamPCP container ransomware D4C Elastic attack chain kubernetes

← All news