Malicious Code Injection in nokire-lokcek43: A Threat to npm Ecosystem
Summary
MAL-2025-162798: Malicious code in nokire-lokcek43 (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 'nokire-lokcek43' is part of a broader campaign targeting the npm ecosystem, specifically associated with the tea.xyz token reward initiative. This package is designed to manipulate npm's publishing system by creating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores in exchange for token rewards, which poses a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'nokire-lokcek43' originates from its malicious design, which includes scripts that automatically modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also compromises the security and reliability of the packages within it, potentially affecting developers who rely on these packages for their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-lokcek43If 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 measure, you can avoid using 'nokire-lokcek43' and any packages that may have been derived from it. Regularly audit your package-lock.json file to identify any suspicious packages and remove them promptly.
Conclusion
The 'nokire-lokcek43' 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 remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your applications from potential risks associated with this and similar vulnerabilities.
See every vulnerability recorded for nokire-lokcek43 →
FAQ
'nokire-lokcek43' is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your application and compromising its security.
You should uninstall the package immediately using 'npm uninstall nokire-lokcek43' and review your dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
