Malicious Code Injection in nacho-bunian-juni: A Threat to npm Ecosystem
Summary
MAL-2025-161724: Malicious code in nacho-bunian-juni (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The package 'nacho-bunian-juni' is part of a broader campaign that exploits the npm ecosystem. It is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores by flooding the npm registry with numerous derivative packages. This package, like others in the campaign, is designed to automatically generate and publish variants with altered metadata, potentially compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the 'nacho-bunian-juni' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The primary risk includes the pollution of the npm registry, which can mislead developers and compromise the security of applications relying on these packages. The malicious payload is part of a larger scheme to exploit the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nacho-bunian-juniIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary measure, you can avoid using the 'nacho-bunian-juni' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'nacho-bunian-juni' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and flood the registry. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for nacho-bunian-juni →
FAQ
The vulnerability involves malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Using this package can lead to the pollution of the npm registry, potentially compromising the security and integrity of your application.
Yes, regularly audit your dependencies, remove any suspicious packages, and utilize tools like Vulert for ongoing vulnerability monitoring.
Immediately remove the package from your project and check for any alternative packages that do not pose similar risks.
