The IndonesianFoods Worm: How Automation and Incentives Fueled a Massive npm Supply-Chain Attack

The IndonesianFoods Worm: How Automation and Incentives Fueled a Massive npm Supply-Chain Attack

Alex Cipher's Profile Pictire Alex Cipher 5 min read

Imagine opening your favorite recipe app and finding it flooded with thousands of oddly named dishes—except, in this case, the menu is the npm registry, and the dishes are malicious packages. The IndonesianFoods worm didn’t just make a mess; it automated chaos, spawning over 100,000 packages at a rate of one every seven seconds. This relentless attack not only strained npm’s infrastructure but also blurred the line between legitimate and spammy code, making life difficult for developers and maintainers alike (BleepingComputer, 2024).

What set this worm apart wasn’t just its scale, but its clever exploitation of the TEA Protocol—a blockchain-based rewards system for open-source contributions. By gaming this system, attackers turned automation into profit, stuffing their digital wallets with TEA tokens. The IndonesianFoods campaign is a stark reminder that open-source ecosystems, while powerful, are vulnerable to new forms of automated abuse. Its evolution over several years, culminating in a worm-like replication loop in 2025, highlights the growing sophistication of supply-chain threats and the urgent need for smarter defenses (BleepingComputer, 2024).

Exploiting Automation in the IndonesianFoods Worm Attack

Automated Package Generation

The IndonesianFoods worm leveraged automation to flood the npm ecosystem with a staggering number of packages. This worm utilized a self-replicating mechanism that allowed it to spawn new packages approximately every seven seconds. This rapid generation of packages led to the creation of over 100,000 packages, as reported by BleepingComputer. The automation process involved randomizing package names using Indonesian culinary terms, which not only added to the volume but also made it challenging to identify and filter out the spam packages from legitimate ones.

Impact on npm Registry

The overwhelming number of packages published by the IndonesianFoods worm had a significant impact on the npm registry. The sheer volume of packages caused by the automated process stressed the registry’s infrastructure, leading to performance degradation and potential service disruptions. This kind of attack exemplifies how automation can be weaponized to exploit vulnerabilities in open-source ecosystems, creating a chaotic environment that can hinder developers’ ability to find and use legitimate packages.

Financial Incentives through TEA Protocol

A financial motive behind the IndonesianFoods worm attack was identified through the exploitation of the TEA Protocol. The TEA Protocol is a blockchain-based system that rewards open-source software (OSS) contributions with TEA tokens. By publishing thousands of interconnected packages, attackers were able to inflate their impact scores and earn more tokens. This strategy was confirmed by a report from Endor Labs, which noted the presence of tea.yaml files listing TEA accounts and wallet addresses in some of the packages (BleepingComputer). This financial incentive highlights how automation can be used not only for disruption but also for profit.

Historical Context and Evolution

The IndonesianFoods worm attack did not occur in isolation but was part of a broader trend of automation-based supply-chain attacks. According to Endor Labs, the spam campaign began two years prior, with significant developments over time. In 2023, 43,000 packages were added, and by 2024, TEA monetization was implemented. The worm-like replication loop was introduced in 2025, marking a significant escalation in the attack’s scale and impact (BleepingComputer). This timeline illustrates the evolving nature of the attack and the increasing sophistication of automation techniques used by threat actors.

Broader Implications for Open-Source Ecosystems

The IndonesianFoods worm attack is part of a growing trend of automation-based attacks targeting open-source ecosystems. Similar incidents, such as the GlassWorm attack on OpenVSX and the Shai-Hulud worm employing dependency confusion propagation, have highlighted the vulnerabilities inherent in these ecosystems. While individually these attacks may cause limited damage, collectively they underscore a shift towards exploiting automation and scale to overwhelm systems (BleepingComputer). This trend poses significant challenges for maintaining the integrity and security of open-source software, necessitating new strategies and defenses to mitigate such threats.

Mitigation Strategies and Recommendations

In response to the IndonesianFoods worm and similar attacks, software developers and organizations are advised to adopt several mitigation strategies. Locking down dependency versions can prevent unauthorized or malicious updates from being introduced into projects. Monitoring for abnormal publishing patterns can help identify and flag suspicious activity early. Implementing strict digital signature validation policies can ensure that only verified and trusted packages are used (BleepingComputer). These measures, while not foolproof, can significantly reduce the risk of supply-chain compromises and enhance the resilience of open-source ecosystems against automated attacks.

Final Thoughts

The IndonesianFoods worm is more than just a cautionary tale—it’s a wake-up call for the open-source community. As attackers harness automation and financial incentives to scale their operations, defenders must adapt with equal agility. Locking down dependencies, monitoring for unusual publishing patterns, and enforcing digital signature validation are no longer optional—they’re essential for survival in this new threat landscape (BleepingComputer, 2024).

The broader trend of automation-based attacks, from GlassWorm to Shai-Hulud, signals a shift in how adversaries target open-source supply chains. Staying ahead will require not just technical solutions, but a community-wide commitment to vigilance and innovation. The IndonesianFoods incident proves that even the most trusted platforms can be overwhelmed, but with the right strategies, resilience is within reach.

References

Related Articles