Malicious Code Injection in nokire-lokcek20: A Threat to npm Packages
Summary
MAL-2025-162773: Malicious code in nokire-lokcek20 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The nokire-lokcek20 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. The malicious nature of this package lies in its ability to modify its own metadata and republish itself under various names, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in nokire-lokcek20 originates from its involvement in a token reward campaign that utilizes autopublish scripts to generate and publish numerous derivative packages. These scripts alter the package.json file by removing private flags, changing version numbers, and creating random package names, which leads to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as they may introduce malicious code into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-lokcek20If 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 monitor your package dependencies using tools like Vulert. By utilizing Vulert, you can check your package-lock.json file for any open-source vulnerabilities without requiring access to the code or installation. You can visit the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability.
Conclusion
The nokire-lokcek20 package poses a significant threat to the npm ecosystem due to its malicious code and ability to republish itself under various names. It is crucial for developers to be vigilant and remove any affected packages while utilizing tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for nokire-lokcek20 →
FAQ
Nokire-lokcek20 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, compromising its security and integrity.
You should uninstall the nokire-lokcek20 package immediately using the command 'npm uninstall nokire-lokcek20'.
Regularly update your dependencies, use trusted packages, and monitor your projects for vulnerabilities using tools like Vulert.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can use it without signing up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
