Malicious Code Injection in sabua-muyaig-bfuga Package
Summary
MAL-2025-165458: Malicious code in sabua-muyaig-bfuga (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-bfuga package is part of the npm ecosystem, often associated with token reward campaigns. It is designed to facilitate the automatic generation and publication of derivative packages. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with variants, potentially harming developers' reputations and the integrity of the registry.
Vulnerability Detail
The vulnerability originates from the sabua-muyaig-bfuga package, which includes malicious scripts that alter the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant issues, including the compromise of developer reputations and 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-muyaig-bfugaIf 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, you can prevent the package from being executed by removing it from your package.json file and ensuring that it is not included in your project dependencies. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The sabua-muyaig-bfuga package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor for any related vulnerabilities using tools like Vulert.
See every vulnerability recorded for sabua-muyaig-bfuga →
FAQ
It is an npm package associated with token reward campaigns that has been identified as malicious.
The vulnerability can lead to the pollution of the npm registry and compromise your project's integrity and reputation.
You should uninstall the package immediately and check for any dependencies that may be affected.
Currently, there is no patched version available. The best course of action is to remove the package.
You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
