EXCLUSIVE: NPM ECOSYSTEM POISONED BY 89,000 MALICIOUS PACKAGES IN "INDONESIANFOODS" SUPPLY CHAIN ATTACK
A massive, two-year-long cyber campaign has been hiding in plain sight, flooding the world's most critical software development pipeline with digital poison. Dubbed "IndonesianFoods," this sophisticated attack saw threat actors deploy nearly 89,000 malicious packages into the Node Package Manager (npm) registry, turning a cornerstone of modern coding into a minefield of potential vulnerabilities and data breaches.
Security researcher Paul McCarty exposed the operation in November 2025, revealing packages named after dishes like "bakso" and "rendang" that contained no legitimate code. Their sole purpose was to inject junk dependencies into software projects. This was not a simple spam attack; it was a patient, strategic assault on software supply chain integrity, designed to exploit developer trust and automated build processes.
The genius—and horror—of the campaign was its camouflage. Experts at Endor Labs confirm the packages had pristine documentation and valid configurations, allowing them to evade detection since 2023. The attackers weren't pushing their code; they were polluting the digital well, waiting for developers to drink by mistake through a typo or misclick. At least 11 projects unknowingly ingested the toxic code.
The real cybersecurity nightmare was a self-replicating malware module. Once installed, certain packages would autonomously publish new malicious modules to npm every seven seconds, using the victim's own credentials. This created an exponentially growing infection, a ransomware-style worm within the development ecosystem. While not a direct crypto theft mechanism, the campaign highlights critical gaps in blockchain security for managing software dependencies and underscores how a single zero-day exploit in a common tool can be weaponized.
This is a wake-up call for every company that uses open-source software. Your next data breach could originate from a misspelled package name. A developer's innocent search could trigger a phishing-style "typosquatting" exploit, compromising your entire build pipeline. The software world has relied on communal trust; that trust has now been weaponized.
We predict a wave of copycat attacks targeting PyPI, RubyGems, and other repositories within six months. The playbook is now public: hide, pollute, and wait for the inevitable human error.
The open-source software supply chain is bleeding, and the attackers are just getting started.
