Listen to this Post
A Major Cybercrime Investigation Reaches Australia
Australian authorities have taken a significant step against an alleged cybercrime operation accused of turning the software developers trust every day into an attack surface. Two men from Western Australia have been charged over their alleged involvement with TeamPCP, a cybercriminal group linked to the destructive Shai-Hulud software supply-chain campaign.
The case highlights a growing reality of modern cybersecurity: attackers do not always need to break directly into a company’s network. Sometimes, compromising the software used by thousands of developers can provide a much larger and more efficient path into businesses around the world.
According to the Australian Federal Police (AFP), the investigation was conducted alongside the FBI and Western Australia Police. Authorities announced on August 26 that a 21-year-old man from Cottesloe and a 23-year-old man from Mandurah had been charged with multiple offenses, including alleged data intrusion and unauthorized modification of data.
Both men appeared before a court in Perth on Thursday as investigators continued to examine their alleged roles in what authorities described as a sophisticated cybercrime syndicate.
Two Western Australian Men Face Serious Charges
The AFP says the two suspects were principal members of the alleged operation and were involved in creating malicious open-source software intended to steal sensitive information and extort organizations.
Authorities estimate that the campaign compromised more than 1,000 organizations worldwide. The alleged attackers are also accused of obtaining more than 500,000 credentials and at least 300GB of stolen data.
Those numbers illustrate why software supply-chain attacks are so dangerous. A single compromised package can potentially reach developers, companies, cloud environments, automated build systems and applications across multiple countries.
The Alleged TeamPCP Connection
Police have not formally identified either suspect by name. However, cybersecurity journalist Brian Krebs has reported that the 21-year-old is allegedly Ruben Thomson, who reportedly operated under the online handle “Ellis” and allegedly led TeamPCP until March 2026.
The distinction between an official identification and a media report is important. Until the allegations are tested in court, the identities and alleged activities should be treated as part of an ongoing criminal investigation rather than established criminal facts.
TeamPCP Built Its Reputation Through Open-Source Software
TeamPCP reportedly emerged in late 2025 and became associated with a particularly dangerous form of cyberattack: poisoning legitimate open-source software.
Instead of concentrating exclusively on breaking into individual corporate networks, attackers could compromise software components that developers already trusted. Those components could then act as a bridge into many downstream environments.
This approach fundamentally changes the economics of cybercrime.
An attacker who compromises one company may obtain access to one environment. An attacker who compromises a widely used software package may potentially reach hundreds or thousands of organizations through a single malicious modification.
Shai-Hulud Turned Trust Into an Attack Weapon
At the center of the allegations is Shai-Hulud, described as a self-propagating worm capable of abusing developer credentials associated with platforms such as GitHub and NPM.
The malware could reportedly help attackers compromise developer accounts and publish malicious versions of otherwise legitimate software packages.
That creates a dangerous chain reaction.
A developer may install what appears to be a normal package. The package executes inside a development environment. Credentials or secrets become exposed. Those credentials can then potentially provide access to additional repositories or infrastructure, allowing the attack to spread further.
The Supply-Chain Domino Effect
The most concerning feature of the campaign is its ability to turn one compromised developer into a potential stepping stone toward additional victims.
Imagine a developer using a popular package without any reason to suspect it has been tampered with. If that package contains malicious code, the developer may unintentionally provide attackers with access to environment variables, API credentials, tokens or other secrets.
If those credentials belong to an organization that maintains additional software packages, the compromise can continue downstream.
This is why software supply-chain security has become one of the defining cybersecurity challenges of the modern cloud era.
Trivy Became One of the High-Profile Targets
Among the incidents associated with TeamPCP was the compromise of Trivy, a widely used vulnerability-scanning tool.
The incident became particularly significant because the consequences reportedly extended beyond the original target. Attackers could potentially use compromised developer infrastructure and credentials as a launching point for additional attacks.
The alleged activity was subsequently linked to compromises involving other organizations, including AI infrastructure company LiteLLM and AI recruitment company Mercor.
LiteLLM Faced a Direct Supply-Chain Threat
LiteLLM also became a notable part of the story. According to the original report, CloudSEK found that an attack involving LiteLLM resulted in secrets being harvested from more than 2,500 organizations.
That figure demonstrates the extraordinary value of credentials to modern attackers.
Passwords are no longer the only prize. API keys, cloud credentials, repository tokens, authentication secrets and machine-to-machine credentials can be equally valuable because they may provide direct access to infrastructure without requiring attackers to defeat traditional login protections.
The AI Industry Is Particularly Exposed
The alleged TeamPCP activity also demonstrates why artificial intelligence companies have become attractive targets for supply-chain attackers.
Modern AI companies depend heavily on open-source libraries, package repositories, APIs, cloud platforms, model-serving frameworks and automated development pipelines.
An attacker who compromises a component used by AI developers may not need to attack the AI company itself. The software dependency can provide a route toward sensitive development environments and cloud infrastructure.
As AI ecosystems continue expanding, this dependency problem is likely to become even more important.
OpenAI Data Was Also Reportedly Stolen
The
Such an incident is particularly notable because it demonstrates how supply-chain compromises can cross organizational boundaries.
A company can invest heavily in firewalls, endpoint protection and identity security while still inheriting risk from the thousands of external packages and tools used by its developers.
The European Commission Was Also Reportedly Targeted
Another significant incident associated with the campaign involved the European Commission’s cloud infrastructure.
The alleged compromise demonstrates that the threat was not limited to small technology companies or individual developers.
Government organizations increasingly rely on cloud platforms and open-source software, creating the same dependency risks found throughout the private sector.
The broader lesson is clear: software provenance and credential security are becoming strategic security concerns, not merely technical details for development teams.
A Disturbing Competition Around Leaked Shai-Hulud Code
The TeamPCP story took an even more unusual turn earlier this year when a competition was reportedly announced on Telegram offering a prize to whoever could create the largest attack using leaked Shai-Hulud code.
If accurately reported, the development illustrates another worrying trend in cybercrime: once dangerous malware or attack tooling escapes its original operators, it can become a reusable weapon for unrelated criminals.
Cybercriminal ecosystems increasingly operate like decentralized markets. Code can be copied, modified, repackaged and redistributed, making attribution and containment substantially harder.
Why Open-Source Software Has Become a Prime Cybersecurity Target
Trust Is the Core Vulnerability
Open-source software is not inherently unsafe. In fact, it is one of the foundations of modern technology.
The problem is that developers often have limited visibility into every dependency their applications consume.
A package may be maintained by a small team or even a single developer. It may have thousands or millions of downloads while receiving limited security scrutiny.
Popularity therefore does not automatically equal safety.
One Package Can Reach Thousands of Developers
The enormous scale of modern software distribution makes supply-chain attacks uniquely powerful.
When malicious code is inserted into a popular dependency, every organization that automatically downloads that dependency can potentially become part of the attack’s reach.
The attacker therefore benefits from the trust accumulated by someone else.
Instead of convincing every victim to install malware, the attacker attempts to compromise something victims already chose to install.
Automatic Updates Increase the Risk
Modern development environments frequently rely on automated package updates.
That convenience can become a security weakness when organizations fail to control exactly which versions of dependencies are permitted.
A compromised package can move rapidly through automated build pipelines before security teams even realize something unusual has happened.
This is one reason dependency pinning, software bills of materials and cryptographic verification are increasingly important.
Developer Credentials Are Extremely Valuable
The Shai-Hulud campaign also underscores the importance of developer credentials.
Developers routinely have access to source-code repositories, package registries, cloud systems, CI/CD environments and deployment platforms.
A stolen developer token can therefore become considerably more valuable than a traditional username and password.
Attackers may use one compromised credential to reach another system, steal additional secrets and then compromise yet another package.
CI/CD Pipelines Can Become Attack Highways
Continuous integration and continuous deployment systems are another critical concern.
These systems frequently have permissions to build, test and deploy software automatically. If attackers gain access to them, they may be able to manipulate legitimate software-production processes.
The result can be especially difficult to detect because malicious activity may occur inside systems that are normally expected to perform automated operations.
The Number of Victims Is Only Part of the Story
More than 1,000 allegedly compromised organizations is already significant, but the number of downstream systems affected by stolen credentials could be even more important.
One organization may have connections to dozens of vendors, developers and cloud services.
A single compromised identity can therefore create consequences far beyond the original victim.
What Undercode Say:
A New Era of Supply-Chain Warfare
TeamPCP represents the direction cybercrime is moving: away from isolated attacks and toward interconnected ecosystems.
Trust Is Becoming the Attack Surface
The attackers allegedly did not need every victim to make a mistake individually. They could exploit trust placed in software that victims already considered legitimate.
Open Source Remains Essential
The answer is not to abandon open-source software. Doing so would be unrealistic and would eliminate many of the technologies powering the modern internet.
Security Must Move Down the Dependency Chain
Organizations need to understand not only their own code but also the software libraries, packages and services embedded inside their applications.
Credentials Are the New Cybercrime Currency
The alleged theft of hundreds of thousands of credentials demonstrates why access tokens and secrets deserve the same attention as passwords.
API Keys Can Open Critical Doors
A leaked API key may provide access to cloud infrastructure, databases, AI services or internal systems without triggering the same alarms as conventional malware.
Package Registries Need Stronger Defenses
Repositories such as NPM have become fundamental infrastructure for software development. Their security is therefore increasingly connected to national and corporate security.
Developers Need Security Visibility
Security teams cannot protect what they cannot see. Organizations need accurate inventories of their dependencies and the permissions those dependencies can access.
Automated Builds Need Strict Controls
CI/CD systems should operate with minimal privileges. A build process should not automatically receive unrestricted access to every production secret.
Secrets Should Never Be Hard-Coded
The safest approach is to keep sensitive credentials outside source code and tightly control when and where applications can access them.
Supply-Chain Attacks Can Multiply Damage
A conventional breach may remain confined to one organization. A supply-chain compromise can potentially multiply the damage across many downstream users.
Shai-Hulud Demonstrates the Domino Effect
The alleged worm-like propagation model shows how quickly a software compromise can transform into a broader ecosystem problem.
AI Makes the Problem More Urgent
AI development depends heavily on open-source components, third-party APIs and rapidly changing frameworks.
AI Infrastructure Contains Valuable Secrets
Cloud credentials, model APIs, proprietary code and internal datasets can make AI environments particularly attractive to attackers.
Governments Are Not Immune
The reported European Commission incident reinforces the fact that government systems can face the same dependency risks as private companies.
Popularity Does Not Equal Security
A package downloaded millions of times can still contain vulnerabilities or be compromised.
Small Maintainers Can Carry Huge Risk
A tiny project can become a critical dependency for thousands of companies without having the resources of a major technology vendor.
Cybercrime Is Becoming More Collaborative
The reported Telegram competition is particularly concerning because it suggests stolen or leaked attack code can be reused by other actors.
Malware Can Outlive Its Creators
Once malicious source code escapes into criminal communities, taking down the original group does not necessarily eliminate the threat.
Arrests Are Important but Not Sufficient
Charging suspected operators can disrupt an operation, but defenders must still address the weaknesses that allowed the campaign to work.
Attribution Remains Difficult
Cybercriminal groups frequently use aliases, infrastructure from multiple countries and shared tools, making definitive attribution challenging.
Legal Action Can Still Have a Deterrent Effect
International cooperation between Australian authorities and the FBI demonstrates that cybercrime investigations increasingly cross national borders.
The Investigation May Not Be Over
The charges could be only one stage of a broader investigation into TeamPCP’s infrastructure, associates and victims.
More Victims Could Emerge
Organizations sometimes discover supply-chain compromises weeks or months after the initial intrusion.
Stolen Credentials Can Create Long-Term Risk
Even after malware is removed, exposed credentials may remain dangerous if organizations do not rotate and revoke them.
Incident Response Must Include Dependencies
Removing malware from a workstation is not enough if the compromised package or developer account remains trusted.
Software Bills of Materials Matter
An accurate software bill of materials can help organizations identify vulnerable or compromised components much faster.
Dependency Monitoring Should Be Continuous
A dependency that is safe today could be compromised tomorrow.
Version Control Is Critical
Organizations should know precisely which versions of third-party packages are running throughout their environments.
Least Privilege Can Limit Damage
Even if a developer credential is stolen, restrictive permissions can prevent attackers from turning one compromise into a much larger breach.
Multi-Factor Authentication Helps
Strong authentication can make stolen credentials harder to exploit, particularly when attackers attempt to access developer accounts directly.
Token Management Deserves More Attention
Long-lived access tokens create unnecessary exposure. Short-lived credentials and automated rotation can reduce the window available to attackers.
Security Teams Need Developer Context
Security monitoring becomes more effective when defenders understand normal development activity and can identify unusual package publication or credential usage.
Open Source Needs Collective Security
Maintainers, registries, cloud providers, developers and corporations all share responsibility for protecting the software ecosystem.
The Biggest Lesson Is About Trust
The TeamPCP case is ultimately a warning about misplaced trust. A legitimate-looking package can become an unexpected entry point into an organization’s most valuable systems.
The Future Will Demand Software Provenance
Organizations will increasingly need to know where their software comes from, who maintains it, whether it has been modified and what permissions it receives.
Supply-Chain Security Is Now Strategic Security
The era when software dependencies were treated as merely a developer concern is ending.
TeamPCP Shows Why
If the allegations surrounding TeamPCP are proven, the campaign demonstrates how a relatively small group can potentially create enormous consequences by attacking the infrastructure of software trust.
Deep Analysis
The Real Target Is the Ecosystem
The most important feature of this case is not simply the alleged theft of data. It is the targeting of relationships between developers, packages, repositories and organizations.
Scale Changes the Economics
Traditional intrusion campaigns require attackers to repeatedly find and compromise individual victims. Supply-chain attacks can potentially produce much greater returns from one successful compromise.
Trust Creates Leverage
Every developer who installs a trusted dependency effectively extends that package’s reach into another environment.
The Attack Surface Is Invisible
Organizations may have hundreds or thousands of dependencies that security teams do not manually inspect.
Automation Magnifies Mistakes
Automated installation and deployment systems can distribute compromised components much faster than humans can investigate them.
Credentials Create Propagation
Once attackers obtain developer or repository credentials, they may be able to move from one environment into another.
Cloud Makes Identity More Important
Modern infrastructure increasingly revolves around identity rather than physical network boundaries.
Developers Are High-Value Targets
Developer accounts can provide access to source code, packages, secrets and deployment systems simultaneously.
Security Must Follow the Code
Protecting production servers while ignoring the software-development process leaves a major gap.
The Registry Is Part of the Security Boundary
Package repositories should increasingly be treated as critical infrastructure rather than simple download sites.
Reputation Can Be Weaponized
Attackers can exploit the reputation of a popular package or maintainer to persuade organizations that malicious code is trustworthy.
The Dependency Problem Is Structural
Organizations cannot realistically eliminate every third-party dependency. They must instead control and monitor them.
Detection Needs Behavioral Signals
Security teams should watch for unusual package publication, credential use, repository changes and unexpected outbound connections.
Prevention Requires Multiple Layers
No single security control can completely stop a supply-chain attack. Identity protection, package verification, monitoring and least privilege must work together.
Incident Response Must Be Wider
When a dependency is compromised, organizations need to investigate not only the infected machine but also every credential and system the package could access.
Revocation Is Critical
Compromised tokens should be revoked quickly. Simply deleting malicious files may leave attackers with continuing access.
Attribution Does Not Equal Containment
Identifying the alleged perpetrators is valuable for law enforcement, but technical remediation must continue independently.
International Cooperation Matters
Cybercrime infrastructure rarely respects national borders. Cooperation between Australia and the United States is therefore particularly important.
Criminal Groups Can Fragment
Even if TeamPCP members are successfully prosecuted, other criminals may adopt similar techniques.
Leaked Tools Increase Future Risk
The reported circulation of Shai-Hulud-related code could allow attackers who had no involvement in the original campaign to reproduce aspects of the attack.
AI Will Increase Dependency Complexity
The rapid evolution of AI frameworks means organizations are adding new dependencies faster than traditional security processes can always assess them.
Developers Need Better Defaults
Secure package installation, secret management and identity controls should require less manual effort from developers.
Companies Need Dependency Ownership
Every important dependency should have someone responsible for monitoring its security status and responding when problems emerge.
Regulators May Pay More Attention
Large-scale supply-chain incidents could encourage governments to introduce stronger requirements around software provenance and security practices.
Open Source Cannot Carry the Burden Alone
Maintainers often operate with limited funding while supporting software used by major commercial organizations.
Commercial Beneficiaries Have a Responsibility
Companies that build businesses on open-source projects should contribute resources toward their security.
Security Budgets May Shift
More organizations are likely to invest in software composition analysis, dependency monitoring, secret scanning and identity security.
The Human Factor Still Matters
Even sophisticated attacks can exploit simple assumptions, such as believing that a popular package must automatically be safe.
The Best Defense Is Verification
Organizations should verify software versions, publishers, signatures, dependencies and expected behavior wherever practical.
The TeamPCP Case Is a Warning
The charges in Australia show that supply-chain cybercrime is no longer a theoretical threat. It has become a law-enforcement priority with potentially global consequences.
The Next Battle Will Be Over Software Trust
As companies become increasingly dependent on interconnected software ecosystems, the ability to prove that code is authentic and trustworthy will become one of the most important defenses in cybersecurity.
❌ The allegations should not be presented as convictions. The two Western Australian men have been charged, meaning the accusations remain subject to the legal process.
✅ The scale of the alleged campaign is substantial. Authorities reportedly estimate that more than 1,000 organizations were compromised, with more than 500,000 credentials and at least 300GB of data stolen.
✅ Shai-Hulud is associated with software supply-chain attacks. The campaign demonstrates how malicious modifications to trusted software can potentially spread risk across downstream developers and organizations.
Prediction
(+1) International Cybercrime Investigations Will Intensify
The cooperation between Australian authorities, Western Australia Police and the FBI points toward a broader international effort to disrupt cybercriminal groups that operate across borders.
(+1) Software Supply-Chain Security Will Receive More Investment
Organizations are likely to increase spending on dependency monitoring, software bills of materials, secret scanning, repository security and developer identity protection.
(+1) Developer Credentials Will Become a Higher Security Priority
Companies will increasingly treat repository accounts, API keys, tokens and CI/CD credentials as critical infrastructure rather than ordinary user credentials.
(+1) Open-Source Governance Will Face Greater Scrutiny
Large organizations may demand stronger provenance, signing, verification and security controls from the software ecosystems on which they depend.
(-1) Attackers Will Continue Targeting Trusted Dependencies
Even if TeamPCP is disrupted, the underlying technique remains highly attractive because it can potentially provide access to many victims through a single compromised component.
(-1) Leaked Attack Code Could Extend the Threat
If malicious code associated with Shai-Hulud continues circulating, unrelated cybercriminals may attempt to modify or reuse it, making the original operation’s disruption less decisive.
(+1) The Biggest Long-Term Shift Will Be Toward Software Provenance
The cybersecurity industry is likely to move toward a future where organizations increasingly demand proof of where software originated, how it was modified and which identities or systems were involved in producing it.
▶️ Related Video (80% Match):
🕵️📝Let’s dive deep and fact‑check.
🎓 Live Courses & Certifications:
Join Undercode Academy for Verified Certifications
🚀 Request a Custom Project:
Secure, high-velocity infrastructure and disruptive technological engineering. Contact our engineering team for high-tier development and proprietary systems:
[email protected]
💎 Smart Architecture | 🛡️ Secure by Design | ⭐ Trusted by Thousands
References:
Reported By: www.bitdefender.com
Extra Source Hub (Possible Sources for article):
https://www.linkedin.com
Wikipedia
OpenAi & Undercode AI
Image Source:
Unsplash
Undercode AI DI v2
🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]
📢 Follow UndercodeNews & Stay Tuned:
𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin | 🦋BlueSky | 🐘Mastodon | 📺Youtube
