Malicious Code Injection in nokire-lokcek2: A Threat to npm Ecosystem
Summary
MAL-2025-162772: Malicious code in nokire-lokcek2 (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-lokcek2' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores in exchange for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-lokcek2' stems from its malicious payload that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the security of the affected packages but also affects the overall trustworthiness of the npm ecosystem, potentially leading to further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-lokcek2If 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 'nokire-lokcek2' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies to ensure no malicious packages are present. You can also use tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The 'nokire-lokcek2' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive measures can help safeguard your projects from potential exploitation.
See every vulnerability recorded for nokire-lokcek2 →
FAQ
'nokire-lokcek2' is an npm package identified as part of a malicious campaign that aims to manipulate the npm registry.
You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using malicious packages can lead to security breaches, data loss, and compromise the integrity of your software project.
It is advisable to audit your npm packages regularly, especially before deploying updates or new features.
Immediately remove the malicious package from your project and replace it with a secure alternative. Report the package to the npm registry.
