Malicious Code Injection in nokire-lokcek48: A Threat to npm Packages
Summary
MAL-2025-162803: Malicious code in nokire-lokcek48 (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-lokcek48' is part of a broader campaign targeting npm, specifically linked to the tea.xyz token reward initiative. This package is designed to manipulate npm's ecosystem by generating and publishing derivative packages with randomized names, ultimately aimed at inflating developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability in 'nokire-lokcek48' originates from its inclusion in a malicious campaign that floods the npm registry with fake packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, 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-lokcek48
If 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 prevent the installation of this package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid any unintended installations of this malicious package.
Conclusion
The 'nokire-lokcek48' package presents a significant risk due to its malicious nature, which alters package metadata and floods the npm registry. It is crucial for developers to be vigilant, remove any instances of this package, and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their projects.
See every vulnerability recorded for nokire-lokcek48 →
FAQ
'nokire-lokcek48' is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the installation of malicious code that alters your project's package metadata and potentially exposes it to further risks.
If you have installed 'nokire-lokcek48', you should immediately remove it from your project and check for any other affected packages.
Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.