Malicious Code Injection in uinsu-loti-babinakam: npm Package Vulnerability
Summary
MAL-2025-170001: Malicious code in uinsu-loti-babinakam (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 uinsu-loti-babinakam 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 the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded in the uinsu-loti-babinakam 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 continuous republishing of these variants can lead to a compromised npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-loti-babinakamIf 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 uinsu-loti-babinakam package and any other packages that may be part of the malicious campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to track vulnerabilities in your dependencies.
Conclusion
The uinsu-loti-babinakam package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for uinsu-loti-babinakam →
FAQ
The uinsu-loti-babinakam package is an npm package that has been identified as part of a malicious campaign aimed at flooding the npm registry with derivative packages.
This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and functionality.
You should uninstall the uinsu-loti-babinakam package immediately and monitor your project for any unauthorized changes.
Yes, regularly update your dependencies, use tools like Vulert to monitor for vulnerabilities, and review your package-lock.json file for any unauthorized changes.
Vulert is a tool that monitors and alerts you in real-time for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by vulnerabilities without needing to install any software.
