Malicious Code Injection in nokire-lokcek83: A Threat to npm Packages
Summary
MAL-2025-162841: Malicious code in nokire-lokcek83 (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-lokcek83' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability in 'nokire-lokcek83' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of other packages and applications relying on npm.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-lokcek83If 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 using the following command to uninstall it: npm uninstall nokire-lokcek83. Additionally, ensure that your package-lock.json is monitored for any unauthorized changes.
Conclusion
The 'nokire-lokcek83' package poses a significant threat due to its malicious code designed to manipulate npm package metadata. Immediate action is required to remove this package and safeguard your application from potential risks. Utilize tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for nokire-lokcek83 →
FAQ
The main risk is that it modifies package metadata and floods the npm registry with malicious variants, which can lead to compromised applications.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
You should uninstall the package immediately and check for any unauthorized changes in your package-lock.json.
Currently, there are no known patches for the nokire-lokcek83 package. It is recommended to remove it from your project.
The malicious code can lead to the exposure of sensitive information, compromise the integrity of your project, and affect the reputation of your application in the npm ecosystem.
