Malicious Code Injection in nokire-lokcek31: A Threat to npm Packages
Summary
MAL-2025-162785: Malicious code in nokire-lokcek31 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'nokire-lokcek31' is part of a series of npm packages associated with 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. This behavior is intended to inflate developer reputation scores for rewards in the tea protocol. The package's functionality is compromised due to its malicious intent, making it a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in 'nokire-lokcek31' originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses risks such as unauthorized access to sensitive information and potential exploitation of affected systems. The malicious payload can significantly disrupt the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-lokcek31If 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 avoid using 'nokire-lokcek31' and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages and remove any that are suspicious or unverified.
Conclusion
The 'nokire-lokcek31' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive steps, you can protect your projects from potential risks associated with this and similar vulnerabilities.
See every vulnerability recorded for nokire-lokcek31 →
FAQ
'nokire-lokcek31' is an npm package linked to a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your project to security risks and instability.
You should uninstall 'nokire-lokcek31' immediately and audit your project for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Yes, tools like Vulert can help you monitor and alert for vulnerabilities in your open-source dependencies automatically.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
