Malicious Code Injection in nokire-lokcek59: A Threat to npm Ecosystem

nokire-lokcek59 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162815: Malicious code in nokire-lokcek59 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package nokire-lokcek59 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 generating and publishing derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses significant risks to users who may unknowingly install these compromised packages.

Vulnerability Detail

The vulnerability in nokire-lokcek59 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify package.json files. This manipulation removes private flags, alters version numbers, and creates random package names, leading to the pollution of the npm registry. The ramifications include potential security risks for developers and users who rely on the integrity of the npm ecosystem, as well as the degradation of trust in package management.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nokire-lokcek59

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 measure, you can avoid using the nokire-lokcek59 package and any other packages that may be part of the tea.xyz campaign. Regularly check your package-lock.json file for any unauthorized changes or additions.

Conclusion

The nokire-lokcek59 package poses a significant threat to the npm ecosystem due to its malicious behavior. Users are advised to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for nokire-lokcek59 →

Share this vulnerability

FAQ

Nokire-lokcek59 is an npm package identified as part of a malicious campaign that aims to manipulate the npm registry.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your project.

You should immediately uninstall the package using npm uninstall nokire-lokcek59 and audit your project for any other 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 against known vulnerabilities using the Vulert playground.

There is no patch available for nokire-lokcek59 as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nokire-lokcek59

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback