Malicious Code Injection in nokire-lokcek97: A Threat to npm Ecosystem
Summary
MAL-2025-162856: Malicious code in nokire-lokcek97 (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-lokcek97' is part of a series of malicious packages that emerged during 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, thereby inflating developer reputation scores for token rewards. 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-lokcek97' originates from its malicious intent to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of projects that depend on these packages. The malicious payload can potentially introduce security risks and instability in applications using affected packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-lokcek97If 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 remove the 'nokire-lokcek97' package from your project by executing the command: 'npm uninstall nokire-lokcek97'. This will prevent any malicious code from executing in your application until a secure version is available.
Conclusion
The 'nokire-lokcek97' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive measures can help safeguard your projects from such threats.
See every vulnerability recorded for nokire-lokcek97 →
FAQ
The primary risk is the potential for malicious code to alter your project's package.json file, leading to security vulnerabilities and instability.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for vulnerabilities.
If you find the 'nokire-lokcek97' package in your project, you should uninstall it immediately and check for any updates or patches for your other dependencies.
To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and ensure that you only install packages from trusted sources.
If you suspect your project has been compromised, conduct a thorough security audit, remove any suspicious packages, and consider restoring from a backup if necessary.
