Malicious Code Injection in nokire-lokcek16: A Threat to npm Ecosystem
Summary
MAL-2025-162768: Malicious code in nokire-lokcek16 (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-lokcek16' is part of a malicious campaign targeting the npm ecosystem, specifically associated with the tea.xyz token reward scheme. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, thereby inflating developer reputation scores. The malicious behavior of this package poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in 'nokire-lokcek16' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also compromises the integrity of the packages, potentially leading to security risks for applications that depend on them.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-lokcek16If 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 the 'nokire-lokcek16' package and replace it with a trusted alternative. Regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'nokire-lokcek16' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and flooding the registry. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking immediate action to remove affected packages can help safeguard your applications.
See every vulnerability recorded for nokire-lokcek16 →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software by analyzing your package-lock.json file.
You should uninstall the package immediately using 'npm uninstall nokire-lokcek16' and replace it with a trusted alternative.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages.
Using compromised packages can lead to security breaches, data leaks, and the potential for malicious code execution in your applications.
