Loading story…
Researchers reported multiple TeamTNT campaigns targeting Docker environments, including a fileless malware operation distributed through malicious Docker Hub images and the Cetus cryptojacking worm aimed at exposed Docker daemons on port 2375. The Docker Hub campaign used four tainted container images to execute payloads directly from memory, helping the malware evade static analysis and some runtime defenses. Analysis found packed binaries, an LD_PRELOAD rootkit, Tsunami malware, a backdoor, and a cryptominer, with malicious processes disguised as kthreadd and communications tied to TeamTNT-controlled IRC infrastructure and a MoneroOcean mining pool.
In a parallel operation, Cetus spread by scanning random subnets with Masscan, abusing the Docker REST API through the Docker CLI, and deploying an obfuscated XMRig miner to mine Monero. The worm attempted to blend into containerized systems by posing as a fake Portainer binary and naming its miner payload docker-cache. Researchers linked both efforts to TeamTNT through shared infrastructure and wallet reuse, underscoring the group's growing focus on stealthy, cloud-native malware that abuses misconfigured Docker services and container registries for persistence, propagation, and illicit cryptocurrency mining.
Map this exposure pattern across your cloud, code, and identities.
5 events from the most recent confirmed update back to the earliest known activity.
During the month of May, Unit 42's Docker daemon honeypot observed multiple attacks against exposed Docker daemons, including the newly identified Cetus cryptojacking worm targeting port 2375. Researchers described Cetus as spreading between Docker daemon instances and deploying an obfuscated XMRig miner.
Unit 42 noted that Cetus used XMRig version 5.5.3, indicating the malware was new because that miner version was released on February 2, 2020.
Aqua's analysis of the malicious images showed packed binaries using memory-only execution, an LD_PRELOAD rootkit to hide processes as "kthreadd," Tsunami malware connecting to TeamTNT IRC infrastructure, a cryptominer communicating with MoneroOcean, and a cron-based backdoor mechanism for persistence.
Aqua's Team Nautilus identified four malicious Docker Hub container images hosted by the accounts portaienr and lifengyi1323 and linked the campaign to TeamTNT. The images were designed to execute malware directly from memory inside containers to evade static scanning and some runtime defenses.
Unit 42 identified Cetus as a Docker cryptojacking worm and linked it to TeamTNT through reuse of a Monero wallet address previously associated with TeamTNT attacks on AWS and Docker daemons.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. View all 17 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See where this exposure pattern shows up across your cloud, code, supply chain, and non-human identities.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
TeamTNT continued to evolve from a Linux-focused cryptojacking group into a broad cloud threat actor targeting exposed Redis, Docker, Kubernetes, Jupyter, Hadoop, PostgreSQL, Tomcat, Nginx, SSH, and other internet-facing services. Researchers tied the group to worm-like campaigns that rapidly scanned for vulnerable hosts, deployed **XMRig** miners, dropped **Tsunami**-based IRC bots including DDoS-capable variants, and used malicious container images on Docker Hub to spread payloads at scale. One TeamTNT-linked Docker Hub account reportedly served images pulled more than **150,000** times, while later campaigns showed the group abusing public registries, compromised accounts, and cloud-native tooling to infect newly exposed systems and report them back to command-and-control infrastructure. Across these operations, TeamTNT consistently paired monetization with aggressive credential theft and stealth. Investigations found the group harvesting **AWS**, Azure, GCP, Kubernetes, Git, NPM, Grafana, database, and storage secrets; stealing SSH keys and host data; and using tools such as Weave Scope, Peirates, BotB, MimiPenguin, Mimipy, `tmate`, and Gsocket to expand access and persistence. Analysts also documented detection evasion through log wiping, process hiding, `LD_PRELOAD` userland rootkits, the **Diamorphine** kernel rootkit, privileged containers with restart policies, and even disabling `runc` to lock out rival attackers, underscoring TeamTNT’s shift from opportunistic mining to sustained compromise of cloud and container environments.
Aug 15, 2026
Threat actors abused exposed Docker servers by creating a malicious Alpine Linux container that launched a multi-stage infection chain, ultimately installing both a cryptocurrency miner and an IRC-based DDoS bot. The attack used a Bash script named `XMI` and a Python script named `d.py` to download payloads, establish persistence, and spread further, with the miner identified as **Coinminer.Linux.MALXMR.UWELD** and the bot as a Kaiten/Tsunami variant detected as **Backdoor.Linux.KAITEN.AMV**. The malware relied on Base64 obfuscation, cron jobs, and a service placed in `/etc/init.d` for persistence, and it attempted lateral movement by harvesting targets from `/.ssh/known_hosts`; researchers also found commented-out SSH brute-force propagation code. Trend Micro said the miner wallet overlapped with earlier campaigns exploiting `CVE-2019-3396` and `CVE-2017-5638`, previously associated in public reporting with the **8220** mining group, while the DDoS component communicated with command-and-control infrastructure including `c4k[.]xpl[.]pwndns[.]pw`, `104[.]244[.]75[.]25`, and `107[.]189[.]11[.]170`.
Aug 14, 2026
Security researchers reported multiple malware operations abusing exposed cloud services and misconfigurations to seize control of Kubernetes and containerized environments. FortiGuard Labs said the **P2PInfect** botnet compromised Google Kubernetes Engine clusters by targeting internet-exposed Redis instances, abusing replication through the `SLAVEOF` command and, in some cases, leveraging `CVE-2022-0543` for remote code execution. The Rust-based malware uses a decentralized peer-to-peer architecture, non-standard ports, and long-lived dormant infections that can persist for months, creating a foothold for later delivery of ransomware, cryptominers, or other payloads. Separate reporting tied the activity to a broader rise in cloud-focused criminal operations that exploit known flaws and weak configurations rather than zero-days. Cyble profiled **TeamPCP** as a large-scale actor targeting Docker APIs, Kubernetes components, Ray dashboards, and Redis to convert victim infrastructure into proxy, command-and-control, ransomware, and Monero mining nodes. Researchers also described a newer framework, **PCPJack**, that appears to piggyback on already compromised cloud environments by wiping TeamPCP artifacts, stealing secrets from AWS, Docker, Kubernetes, GitHub, Slack, Office 365, and other services, and exfiltrating encrypted data to Telegram while spreading worm-like across exposed Docker, Kubernetes, Redis, MongoDB, and RayML services.
Jun 29, 2026