Malicious Code Injection in sabua-muyaig-bufu Package
Summary
MAL-2025-165475: Malicious code in sabua-muyaig-bufu (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 sabua-muyaig-bufu package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the sabua-muyaig-bufu package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting developers relying on legitimate packages. The origin of this issue is linked to the automated scripts (auto.js, autopublish.js, etc.) that are designed to exploit the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sabua-muyaig-bufuIf 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-muyaig-bufu package and monitor your project's dependencies for any signs of malicious activity. Regularly audit your package-lock.json file to identify any unauthorized changes.
Conclusion
The sabua-muyaig-bufu package has been identified as containing malicious code that compromises the npm registry. It is crucial to remove this package from your projects and monitor for any related vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your open-source dependencies.
See every vulnerability recorded for sabua-muyaig-bufu →
FAQ
The sabua-muyaig-bufu package is an npm package associated with a token reward campaign that has been identified as malicious.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should uninstall the sabua-muyaig-bufu package immediately and check for any dependencies that may have been affected.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
