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

nokire-lokcek5 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162805: Malicious code in nokire-lokcek5 (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 Penetration testing for web, API and mobile 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-lokcek5' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata to inflate developer reputation scores, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in 'nokire-lokcek5' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to continuously republish variants of the package, polluting the npm registry and potentially leading to security risks for applications that depend on these packages. The origin of this vulnerability is linked to a campaign aimed at exploiting the npm ecosystem for token rewards, making it a significant concern for developers.

How To Fix

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

npm uninstall nokire-lokcek5

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, avoid using the 'nokire-lokcek5' package and monitor your dependencies for any instances of this package. You can also utilize tools like Vulert to monitor your project for vulnerabilities. To check if your application is affected, you can use the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'nokire-lokcek5' package poses a significant risk due to its malicious code designed to manipulate package metadata. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action is required to mitigate the risks associated with this package.

See every vulnerability recorded for nokire-lokcek5 →

Share this vulnerability

FAQ

'nokire-lokcek5' is a malicious npm package associated with a token reward campaign that floods the npm registry with harmful packages.

The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.

You should uninstall the package immediately using 'npm uninstall nokire-lokcek5' and monitor your project for any other vulnerabilities.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and keep your packages updated to minimize risks.

You can find detailed information in the vulnerability report on the GitHub repository of the malicious packages or through security advisories.

How To Fix

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

npm uninstall nokire-lokcek5

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