Malicious Code Injection in sabua-muyafig-budfaifa: A Threat to npm Users
Summary
MAL-2025-165432: Malicious code in sabua-muyafig-budfaifa (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 'sabua-muyafig-budfaifa' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The malicious nature of this package poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability originates from the package's design, which includes autopublish scripts that modify the package.json file to remove private flags and change version numbers. This allows the package to generate random names and continuously republish variants, leading to pollution of the npm registry. The ramifications include potential security risks for users who may unknowingly install these malicious packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sabua-muyafig-budfaifaIf 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 'sabua-muyafig-budfaifa' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like 'npm audit' to identify and address vulnerabilities.
Conclusion
The 'sabua-muyafig-budfaifa' package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for sabua-muyafig-budfaifa →
FAQ
The main threat is the injection of malicious code that modifies package.json files, allowing for the creation of numerous derivative packages that can pollute the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed the package, you should uninstall it immediately using 'npm uninstall sabua-muyafig-budfaifa' and check for any other affected packages.
Yes, tools like 'npm audit' can help identify vulnerabilities in your npm packages, and services like Vulert can provide real-time monitoring.
Look for alternative packages that offer similar functionality without the associated risks. Always review the security of packages before integrating them into your project.
