Malicious Code Injection in sabu-nali-lbisya Package - npm Vulnerability
Summary
MAL-2025-165287: Malicious code in sabu-nali-lbisya (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-lbisya 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 aimed at inflating developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the sabu-nali-lbisya package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, which can lead to a significant increase in the number of untrusted packages in the npm registry, potentially compromising the integrity of applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sabu-nali-lbisyaIf 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 avoid using the sabu-nali-lbisya package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The sabu-nali-lbisya package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential for developers to remove this package from their projects and to stay vigilant about the packages they use. Regular monitoring and updates can help mitigate such vulnerabilities.
See every vulnerability recorded for sabu-nali-lbisya →
FAQ
sabu-nali-lbisya is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
The malicious code can lead to the pollution of the npm registry with untrusted packages, potentially compromising the security and integrity of applications that depend on these packages.
If you have installed the sabu-nali-lbisya package, you should uninstall it immediately using the command: npm uninstall sabu-nali-lbisya.
You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
