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

nokire-lokcek99 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162858: Malicious code in nokire-lokcek99 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'nokire-lokcek99' is part of a series of malicious 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 aimed at inflating developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'nokire-lokcek99' originates from its malicious design, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers who unknowingly use these packages. The malicious payload can compromise the integrity of applications relying on affected packages, making them susceptible to further exploitation.

How To Fix

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

npm uninstall nokire-lokcek99

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 workaround, you can monitor your project's dependencies using tools like Vulert. By utilizing Vulert, you can check if your application is affected by this vulnerability without requiring access to the code or installation. Simply upload your package-lock.json file to receive real-time alerts for open-source vulnerabilities.

Conclusion

The 'nokire-lokcek99' package poses a significant threat to the npm ecosystem due to its malicious design aimed at manipulating the registry. It is crucial for developers to be vigilant, remove affected packages, and utilize monitoring tools like Vulert to ensure the security of their applications.

See every vulnerability recorded for nokire-lokcek99 →

Share this vulnerability

FAQ

'nokire-lokcek99' is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can compromise the integrity of your application by introducing malicious code that may lead to further exploitation or data breaches.

You should uninstall the package immediately using 'npm uninstall nokire-lokcek99' and monitor your dependencies for any further vulnerabilities.

Regularly audit your dependencies, use tools like Vulert for monitoring, and avoid using unverified packages from the npm registry.

Yes, Vulert can monitor your package-lock.json file for vulnerabilities and alert you in real-time, helping you maintain the security of your application.

How To Fix

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

npm uninstall nokire-lokcek99

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