TeamPCP Linked to Redis Attacks Dating Back to 2020, Predating Supply Chain Campaign
Threat actor TeamPCP has been linked to Redis-related attacks since 2020, predating their later supply chain compromise campaign, indicating a long-term focus on exploiting internet-facing systems.
A new analysis has uncovered that the threat actor tracked as TeamPCP has been active on the cybercrime scene as far back as 2020, indicating the group has been compromising internet-facing infrastructure for years before training their sights on the software supply chain. Researchers from Oligo Security noted that the connection between these activities is supported by overlapping domains, malware deployment paths, staging techniques, backend infrastructure, and operational tradecraft.
This includes two campaigns observed in the second half of 2025: ShadowRay 2.0 (aka IronErn), which involved hijacking artificial intelligence (AI) infrastructure into a self-propagating botnet, and TA-NATALSTATUS, which targeted exposed Redis servers to deliver cryptocurrency miners. TA-NATALSTATUS is assessed to be an evolution of a prior campaign detailed in April 2020 that involved targeting Redis servers to deploy malware, suggesting the threat actor has been actively targeting internet-accessible infrastructure across Ray, Docker, Redis, and React long before branding itself as TeamPCP.
Details of the attackers first emerged towards the end of last year when they were linked to the exploitation of security flaws in React Server Components (RSC) and Next.js to facilitate the extraction of credentials and sensitive data from compromised environments. This activity was codenamed Operation PCPcat. Earlier this year, Flare detailed a massive campaign undertaken by the threat actor to systematically target cloud-native environments as part of efforts to set up malicious infrastructure for follow-on exploitation, aiming to build distributed proxy and scanning infrastructure at scale, compromise servers for data exfiltration, deploy ransomware, conduct extortion, and mine cryptocurrency.
The group has since branched into high-profile supply chain compromises, weaponizing the interconnected nature of modern software to infect developer systems en masse by poisoning popular open-source libraries through a combination of GitHub Actions and token theft abuse. One of the strongest operational links is the overlap between the IronErn GitHub and GitLab identities observed during ShadowRay 2.0 and TeamPCP's later infrastructure, establishing a direct operational bridge between the ShadowRay 2.0 campaign and the actor later operating publicly as TeamPCP.
The latest findings show that not only are these efforts linked, but also that the threat actor repeatedly abused known security flaws impacting React, Docker, Redis, and Ray to gain access and rely on automated and wormable exploitation techniques for self-propagation. The expansion into cascading software supply chain attacks, therefore, represents a natural evolution of this trend, allowing the threat actors to take advantage of legitimate cloud infrastructure and repurpose tried and tested methods in their efforts.
These shifts have been complemented by continuous updates to its malware arsenal, including a Python script ("kube.py") specifically used after breaching Kubernetes environments. While earlier versions focused on propagation and persistence, new variants observed as recently as March 2026 began to incorporate wiper-like functionality. This destructive code path checked if the victim system was configured for the Iran timezone and, if so, fired a DaemonSet that wiped every node in the cluster via a wiper named Kamikaze. On Kubernetes nodes outside Iran, it deployed the CanisterWorm backdoor. For non-Kubernetes Iranian systems, the malware executed a "poison_pill()" routine to erase the entire file system.
Whether this continuity reflects a direct rebrand, a shared operator set, or close collaboration between historically related actors cannot be determined with 100% certainty. What the evidence does demonstrate is that TeamPCP represents the continuation of an existing operational ecosystem rather than an entirely new threat actor that appeared in late 2025.