Malicious Code Injection in uinsnu-lotimi-killnear: A Threat to npm Ecosystem
Summary
MAL-2025-169757: Malicious code in uinsnu-lotimi-killnear (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 package 'uinsnu-lotimi-killnear' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others in the npm registry, is intended to facilitate the development and sharing of code. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This behavior not only compromises the integrity of the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in 'uinsnu-lotimi-killnear' originates from its association with a malicious token reward campaign. The package contains scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This leads to the continuous republishing of these variants, which pollutes the npm registry and can potentially introduce harmful code into projects that depend on these packages. The ramifications include compromised security for applications using these packages and a degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uinsnu-lotimi-killnearIf 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 workaround, you can monitor your project's dependencies using tools like Vulert. Vulert allows you to check for vulnerabilities in your package-lock.json file without requiring code access or installation. You can use the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability.
Conclusion
The 'uinsnu-lotimi-killnear' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to be vigilant about the packages they use, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking these steps, you can help maintain the integrity and security of your projects.
See every vulnerability recorded for uinsnu-lotimi-killnear →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can introduce malicious code into your project, compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall uinsnu-lotimi-killnear' and review your project's dependencies for any other vulnerabilities.
Regularly update your dependencies, use trusted packages, and utilize tools like Vulert to monitor your project's dependencies for vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities using your package-lock.json file.
