Worm rubs out competitor's malware, then takes control
#Vulnerabilities

Worm rubs out competitor's malware, then takes control

Privacy Reporter
6 min read

A newly discovered self-propagating cloud worm is eliminating infections from rival cybercrime group TeamPCP to seize control of compromised systems, harvest credentials across cloud environments, and spread to new vulnerable targets without human intervention, creating significant risks for user privacy and regulatory compliance under GDPR and CCPA.

Featured image

Security researchers at SentinelOne’s SentinelLabs have identified a self-propagating cloud worm, dubbed PCPJack, that actively eliminates infections from rival cybercrime group TeamPCP to seize control of compromised systems, harvest sensitive credentials, and spread to new vulnerable targets without human intervention. First detected in late April 2026 within a Kubernetes-focused hunting rule on VirusTotal, PCPJack stands out from common cloud attack tools for its primary initial action: erasing all processes and artifacts associated with TeamPCP, a group that gained notoriety in late 2025 for compromising the Trivy vulnerability scanner in one of the most impactful supply chain attacks of the year.

TeamPCP’s compromise of Trivy, a widely used open-source tool for scanning container images and filesystems for vulnerabilities, allowed the group to distribute credential-harvesting malware to any developer or organization that downloaded the infected version. This enabled attackers to pivot from compromised development environments to more valuable production targets, making the attack one of the most notable supply chain incidents in recent memory. Unlike TeamPCP’s campaign, which relied on human actors to manually distribute compromised software and pivot to new targets, PCPJack spreads automatically with no human intervention required after the initial infection.

Infections begin when already compromised systems scan for exposed, unsecured services including Docker instances, Kubernetes clusters, Redis databases, MongoDB deployments, RayML frameworks, and public-facing web applications. Once a vulnerable environment is identified, the worm executes a shell script on the target that sets up a payload download environment, then immediately terminates any active TeamPCP processes and deletes associated files. SentinelLabs initially considered that the toolset might belong to a researcher cleaning up TeamPCP infections, but analysis of later-stage payloads confirmed it is a malicious framework designed for long-term credential theft and propagation.

After clearing out the rival group’s malware, PCPJack downloads its full toolset, which includes modules for lateral movement across internal and external networks, credential parsing and encrypted exfiltration, and automated scanning for new vulnerable environments to infect. The credential theft module targets a wide range of sensitive data: environment variables, configuration files, SSH keys, Docker secrets, Kubernetes service tokens, and stored credentials for dozens of finance, enterprise, messaging, and cloud service platforms. A full list of targeted services is available in the SentinelLabs advisory. SentinelLabs noted that PCPJack does not include a cryptominer, a common addition to cloud malware, suggesting its operators intend to use stolen credentials for spam campaigns, financial fraud, or to sell access to other cybercriminals. As researchers noted, the worm’s operators are effectively claiming 'all your compromised credentials are belong to us now instead of the other gang' as they seize control of systems previously held by TeamPCP.

This type of large-scale credential harvesting and unauthorized system access triggers strict obligations under major data protection regulations, including the European Union’s General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA). Under GDPR, any entity that processes the personal data of EU residents must implement appropriate technical and organizational measures to protect that data, including securing cloud environments against unauthorized access. A breach resulting from an unsecured cloud instance compromised by PCPJack would qualify as a reportable data breach if it leads to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to personal data.

GDPR requires organizations to notify their lead supervisory authority of a breach within 72 hours of becoming aware of it, and to notify affected individuals without undue delay if the breach is likely to result in a high risk to their rights and freedoms. Fines for non-compliance or failure to secure personal data can reach up to 4% of a company’s global annual revenue or €20 million, whichever is higher. For example, a company that leaves a Kubernetes cluster exposed without authentication, leading to a PCPJack infection that steals customer credentials, could face massive fines if regulators determine they did not implement reasonable security measures.

Under CCPA/CPRA, businesses that collect personal information of California residents must disclose data collection practices, and are liable for statutory damages of up to $750 per consumer per incident in the event of a data breach caused by unauthorized access to non-encrypted personal information. Intentional violations of CCPA can result in fines of up to $7,500 per violation, enforced by the California Attorney General. PCPJack’s focus on harvesting credentials for finance and enterprise platforms means stolen data will likely include personal information protected under these regulations, creating direct liability for affected companies.

Impact on Users and Companies

Affected parties span both individual users and organizations of all sizes. For individual users, stolen credentials can lead to identity theft, unauthorized access to bank accounts, email, and social media profiles, and fraudulent charges. Since PCPJack targets credentials for messaging and cloud services, users may also face unauthorized access to work accounts if they reuse credentials across personal and professional platforms.

For organizations, the impacts are far more severe. A PCPJack infection can lead to full compromise of cloud environments, exfiltration of proprietary data, and lateral movement to on-premises systems. Companies that process personal data face regulatory fines as outlined above, in addition to costs associated with incident response, forensic investigations, customer notification, and credit monitoring for affected individuals. Reputational damage can also lead to lost business, particularly for companies in regulated industries like finance and healthcare.

Cloud service providers that host unsecured instances are not immune to impact either. While PCPJack targets user-managed instances rather than provider infrastructure, a large-scale infection affecting multiple customers of a single provider could lead to scrutiny from regulators, who may investigate whether the provider offered adequate security guidance or tools to prevent exposure. SentinelLabs noted that PCPJack’s ability to spread across both internal and external networks means a single compromised instance can quickly infect an entire organization’s cloud footprint, as well as third-party systems connected to the initial target.

What Changes Are Needed

The discovery of PCPJack underscores the need for immediate changes to cloud security and compliance practices. SentinelLabs’ primary mitigation recommendation is straightforward: all cloud services, including Docker and Kubernetes instances, must require authentication even if they are not exposed to the public internet. Many organizations leave development or testing instances unsecured under the assumption that they are not accessible to external actors, but PCPJack’s automated scanning can identify these instances even if they are not listed in public directories.

From a compliance perspective, organizations must update their data protection policies to explicitly address cloud security risks. This includes conducting regular audits of all cloud instances to identify exposed services, implementing least privilege access for all cloud credentials, and deploying endpoint detection tools capable of identifying PCPJack and TeamPCP artifacts. Companies subject to GDPR or CCPA must also review their breach notification procedures to ensure they can meet 72-hour reporting deadlines if a PCPJack infection leads to a data breach.

Regulators may also update enforcement priorities in response to the rise of self-propagating cloud worms like PCPJack. The U.S. Federal Trade Commission has already taken action against companies that fail to secure cloud environments, and EU data protection authorities have increasingly targeted organizations with inadequate cloud security measures. Companies that fail to implement basic authentication for cloud services may find themselves the subject of regulatory investigations, even if no breach has occurred yet, as regulators shift to proactive enforcement of security requirements.

For cybersecurity teams, the rivalry between TeamPCP and PCPJack operators highlights a growing trend of cybercriminal groups targeting each other’s infrastructure to seize market share. This infighting can lead to more aggressive malware as groups compete to control compromised systems, making it even more critical for organizations to secure their environments against all threat actors, not just known groups.

Comments

Loading comments...