Malicious Code Injection in nokire-lokcek81: A Threat to npm Packages

nokire-lokcek81 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162839: Malicious code in nokire-lokcek81 (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-lokcek81 is part of the npm ecosystem, which is widely used for JavaScript package management. This package 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 designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in nokire-lokcek81 arises from its malicious payload that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to continuously republish variants of the package, polluting the npm registry and potentially leading to reputation damage for legitimate developers. The origin of this issue is linked to automated scripts that exploit the npm ecosystem for token rewards, making it a significant concern for package maintainers and users.

How To Fix

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

npm uninstall nokire-lokcek81

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, you can prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies to known safe versions. You can also monitor your project for vulnerabilities using tools like Vulert, which can alert you to open-source vulnerabilities in real-time without requiring code access.

Conclusion

The nokire-lokcek81 package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor their projects for vulnerabilities. Regular updates and dependency management are crucial in maintaining a secure development environment.

See every vulnerability recorded for nokire-lokcek81 →

Share this vulnerability

FAQ

Nokire-lokcek81 is an npm package that has been identified as malicious, associated with a campaign to inflate developer reputation scores through automated scripts.

The vulnerability can lead to the pollution of the npm registry, potential reputation damage for developers, and the risk of inadvertently using compromised packages.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

You should uninstall the package immediately using 'npm uninstall nokire-lokcek81' and review your project's dependencies for any other vulnerabilities.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json, providing real-time insights into potential risks.

How To Fix

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

npm uninstall nokire-lokcek81

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