Malicious Code Injection in nacho-bunia-vibni: A Threat to npm Ecosystem
Summary
MAL-2025-161717: Malicious code in nacho-bunia-vibni (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-bunia-vibni' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can harm developers' reputations and the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in 'nacho-bunia-vibni' stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The malicious payload continuously republishes variants of the package, polluting the npm registry and potentially leading to security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nacho-bunia-vibniIf 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 workaround, avoid using the 'nacho-bunia-vibni' package and consider replacing it with a similar, trusted package. Always verify the integrity of packages before installation.
Conclusion
The 'nacho-bunia-vibni' package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry. It is crucial for developers to remove this package and adopt best practices for package management to safeguard their applications.
See every vulnerability recorded for nacho-bunia-vibni →
FAQ
The main issue is that it contains malicious code designed to manipulate package metadata and flood the npm registry with unwanted variants.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.
If you have installed the package, immediately uninstall it using 'npm uninstall nacho-bunia-vibni' and replace it with a trusted alternative.
While specific exploits have not been detailed, the manipulation of package metadata can lead to security risks and compromised developer reputations.
To prevent similar vulnerabilities, always verify package sources, keep your dependencies updated, and utilize tools like Vulert for real-time monitoring.
