Malicious Code Injection in uinsu-lost-din Package - npm Vulnerability
Summary
MAL-2025-169938: Malicious code in uinsu-lost-din (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-lost-din 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 within the uinsu-lost-din package. It modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsu-lost-dinIf 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 installation of this malicious package by using npm's package-lock.json to monitor your dependencies. You can also utilize tools like Vulert to check if your application is affected by this vulnerability. For example, you can run the following command to check your package-lock.json: vulert check package-lock.json.
Conclusion
The uinsu-lost-din package poses a significant risk due to its malicious code designed to exploit the npm registry. Developers are advised to remove this package and monitor their dependencies closely to avoid potential security breaches. Utilizing tools like Vulert can aid in maintaining the integrity of your applications.
See every vulnerability recorded for uinsu-lost-din →
FAQ
The uinsu-lost-din package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
This vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should immediately remove the uinsu-lost-din package from your project and check for any other affected packages.
You can use tools like Vulert, which allows you to monitor and alert 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.
