Threat Overview

On 2026-08-27, Australian Federal Police (AFP) announced the arrest of two men from Western Australia, aged 21 and 23, who are suspected of leading the notorious cybercrime group TeamPCP. The group has orchestrated the longest-running supply‑chain attack campaign, embedding malicious code in hundreds of open‑source software packages and extracting credentials from cloud environments worldwide.

TeamPCP’s primary vehicle, the self‑propagating worm Shai‑Hulud, infiltrates development pipelines by compromising the accounts of developers on platforms such as GitHub and NPM. Once inside a build system, the worm injects malware into open‑source libraries, which are then redistributed to other developers. The cycle repeats, enabling TeamPCP to maintain a growing network of compromised credentials and to publish weaponized versions of popular tools.

Key TTPs

• Credential Phishing and Theft: Targeted phishing campaigns aimed at developers’ personal and organizational accounts.
• Malicious Package Injection: Substituting legitimate open‑source libraries with malicious binaries that carry back‑door payloads.
• Supply‑Chain Contest: Publicly offering monetary rewards for the largest successful supply‑chain operation, effectively recruiting talent and expanding the attack surface.
• Data Exfiltration: Harvesting API keys, cloud service credentials, and other secrets from thousands of businesses, including major AI and automotive firms.

In March 2026, TeamPCP leveraged the LiteLLM open‑source AI gateway to exfiltrate credentials from over 2,500 organizations. In May 2026, the group claimed responsibility for compromising nearly 3,800 GitHub repositories after a malicious extension was installed by a GitHub developer.

Attacker Profile

TeamPCP is not a single, monolithic crew but a loosely connected community of threat actors. The central node appears to be George Prepakis, operating under the handle @kernelstub. He facilitated a Matrix chat server called Cybercats that congregates members from various cybercrime groups.

The two arrested individuals—identified as Ruben Thomson (21) and Michael Gaebler (23)—were active in this community. Thomson, whose real name is Ruben Thomson, had a history of opsec failures, including using the same personal email across multiple platforms, registering companies with names tied to his criminal aliases, and posting a HackerOne profile under the pseudonym Deadcatx3.

Operational Footprint

Several IP addresses linked to the group were identified. A key server operated by Thomson used the IP 211[.]27[.]196[.]111 to host private file storage. Another server at 110[.]141[.]230[.]15 was used to host domains such as rubenthomson.com, which served as a front for selling stolen iPhones and distributing illicit software.

All URLs in this report have been sanitized. For example, the official threat report is available at hxxps://krebsonsecurity[.]com/2026/08/two-alleged-teampcp-hackers-arrested-in-australia/. Additional context can be found on AlienVault OTX at hxxps://otx.alienvault[.]com/pulse/6a9025d25142baef9c2634cd/.

Impact Assessment

TeamPCP’s attacks caused significant disruption to the global software development ecosystem. The compromise of code repositories exposed confidential credentials, leading to data breaches in sectors ranging from automotive to healthcare. The group’s activities forced major platforms—GitHub, Python Package Index, npm—to implement cooldown mechanisms and stricter code‑review policies.

Recommendations for Defense

1. Implement Supply‑Chain Risk Management (SCRM): Adopt policy frameworks that require continuous monitoring of dependencies, enforce signed packages, and verify source code integrity using reproducible builds.
2. Enforce Multi‑Factor Authentication (MFA) for all developer accounts: MFA reduces the effectiveness of credential phishing and limits lateral movement within development pipelines.
3. Deploy Code‑Scanning and Static Analysis Tools: Integrate automated scanning into the CI/CD pipeline to detect malicious code before it reaches end users.
4. Monitor for Anomalous Build Behavior: Use telemetry to detect unusual commits, unauthorized package uploads, or sudden increases in package download counts.
5. Secure Developer Workstations: Harden local environments, restrict external media, and enforce least‑privilege principles.
6. Educate Developers on Social Engineering: Provide training that covers phishing, credential reuse, and safe handling of third‑party libraries.

These measures, combined with threat‑intelligence sharing across industry consortia, can mitigate the risk posed by sophisticated actors like TeamPCP. Continuous vigilance, coupled with proactive defense, remains essential to safeguard the integrity of open‑source ecosystems.

Conclusion

The arrest of the two TeamPCP suspects marks a significant victory for Australian law enforcement and the global cybersecurity community. However, the group’s legacy underscores the evolving nature of supply‑chain threats and the necessity for robust, coordinated defenses. By adopting the recommendations above, organizations can reduce their exposure to similar attacks and protect the foundations of modern software development.