Loading story…
Palo Alto Networks Unit 42 reported a self-replicating peer-to-peer worm dubbed P2PInfect that compromises exposed Redis servers by exploiting CVE-2022-0543, a critical Lua sandbox escape affecting Debian-packaged Redis deployments. The malware is written in Rust, targets both Linux and Windows, and was observed attacking Redis honeypots in Unit 42’s HoneyCloud environment. Researchers estimated that 934 internet-exposed Redis systems could be vulnerable out of more than 307,000 observed Redis instances.
The worm uses a P2P architecture to spread, exchange node lists, and deliver updated binaries, giving operators a built-in mechanism to expand the botnet and push future payloads. Unit 42 also observed scanning for additional exposed Redis hosts and port 22 for SSH, although no confirmed SSH exploitation was seen. On Windows, the malware showed persistence and defense-evasion behavior including firewall rule changes, obfuscated PowerShell, a monitor process, self-updating binaries, and deletion of the initial dropper. Binaries named miner and winminer were recovered, but researchers said they found no definitive evidence that cryptomining had been activated.
Pull IOCs and campaign context straight into your stack.
2 events from the most recent confirmed update back to the earliest known activity.
Unit 42 discovered the first known instance of the P2PInfect peer-to-peer worm in its HoneyCloud honeypot environment. The worm targeted exposed Redis instances and exploited CVE-2022-0543 for initial access.
Unit 42 publicly reported the newly discovered Rust-based P2PInfect worm and detailed its cross-platform Linux and Windows capabilities, peer-to-peer architecture, and targeting of exposed Redis systems. The report also assessed that the botnet's auto-updating design could support future payload delivery and noted no definitive evidence of cryptomining.
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 9 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
Pull the IOCs, campaigns, and victimology behind this family, ready to push into your SIEM and EDR.
1 reference 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.
Researchers reported that the **P2PInfect** worm, a Rust-based cross-platform malware family, expanded beyond earlier `x86-64` infections to target **ARM** and **MIPS** systems, increasing the threat to IoT and embedded Linux environments. The worm spreads through multiple paths, including exploitation of **Redis** weaknesses and **SSH** brute-force activity, and uses a **peer-to-peer** architecture rather than a centralized command-and-control server, making disruption more difficult. Analysis of newer samples showed the malware also incorporates self-protection and evasion features, including anti-debugging checks, disabled core dumps, runtime modification of a dropped auxiliary binary, and wrapper ELF files used to conceal the main payload. Telemetry tied the campaign to growing infection activity from late 2023 into early 2024, with observed malicious connections frequently originating from **China, Hong Kong, and Singapore**, while published research also included detection content such as **YARA rules**, infrastructure indicators, and malware hashes to support defender response.
Aug 15, 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
An exposed directory on `188.245.99.156` revealed a cryptomining operation that compromised **3,562 internet-facing Redis servers** from a target list of 12,966 hosts. The operator abused Redis instances with no authentication through rogue replication, using crafted RDB payloads to install cron-based persistence and download XMRig miners configured for the MoneroOcean pool. Two principal campaign runs achieved 26.1% and 22.1% compromise rates, while a prequalified unauthenticated target list yielded 72.6%, indicating that stale target data—not the underlying technique—limited the campaign. The same server hosted rogue replication listeners, payload staging, and HTTP heartbeat collection, and reuse of a Monero wallet tied the infrastructure directly to monetization and to a separate February 2026 Meterpreter/XMRig toolkit. Attempts to inject SSH `authorized_keys` and probe MongoDB did not produce confirmed compromises; researchers also recovered, but could not quantify, a WordPress credential-spraying and webshell-staging chain. Organizations should require Redis authentication, restrict network exposure, and disable or tightly control replication commands where not required; upgrading Redis alone does not remediate unauthenticated deployments.
Sep 9, 2026