Malicious Code Injection in nokire-lokcek78: A Threat to npm Ecosystem
Summary
MAL-2025-162835: Malicious code in nokire-lokcek78 (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-lokcek78' 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 creating and publishing numerous derivative packages with randomized names. This behavior not only inflates developer reputation scores but also compromises the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-lokcek78' stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior can pollute the npm registry and potentially expose users to further malicious activities, as it undermines the trustworthiness of the packages available in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-lokcek78If 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-lokcek78' package and monitor your project for any unintended dependencies that may include it. You can also use tools like Vulert to scan your project for vulnerabilities. To check if your application is affected, you can use the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'nokire-lokcek78' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential to remove this package from your projects and regularly monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for nokire-lokcek78 →
FAQ
The primary risk is that it modifies package.json files to remove private flags and generates numerous malicious packages, which can lead to a polluted npm registry and potential security breaches.
You can check your package-lock.json file or run 'npm ls nokire-lokcek78' in your terminal to see if it is included in your project.
You should immediately uninstall the package using 'npm uninstall nokire-lokcek78' and review your other dependencies for similar vulnerabilities.
Regularly update your packages, use tools like Vulert to monitor for vulnerabilities, and be cautious when adding new dependencies from unverified sources.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
