Malicious Code Injection in sabu-nali-lbiya Package: A Threat to npm Users
Summary
MAL-2025-165288: Malicious code in sabu-nali-lbiya (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 sabu-nali-lbiya package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea.xyz token reward campaign. The package modifies critical files, making it a significant threat to users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in the sabu-nali-lbiya package originates from its malicious intent to alter package.json files by removing private flags and changing version numbers. This allows the package to create and republish variants with randomized names, effectively polluting the npm registry. The ramifications include potential security risks for applications relying on these packages, as they may inadvertently incorporate malicious code into their dependencies, leading to data breaches or system compromises.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sabu-nali-lbiyaIf 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, users can avoid using the sabu-nali-lbiya package and any of its derivatives. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.
Conclusion
The sabu-nali-lbiya package poses a significant threat to npm users due to its malicious code injection capabilities. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications. Regularly updating packages and utilizing monitoring tools like Vulert can help mitigate risks associated with open-source vulnerabilities.
See every vulnerability recorded for sabu-nali-lbiya →
FAQ
The sabu-nali-lbiya package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising security and data integrity.
If you have installed the sabu-nali-lbiya package, you should remove it immediately and check for any other affected dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
