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

nokire-lokcek56 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162812: Malicious code in nokire-lokcek56 (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-lokcek56' 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 numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'nokire-lokcek56' originates from its malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This can result in developers unknowingly installing compromised packages, which may lead to further exploitation or data breaches.

How To Fix

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

npm uninstall nokire-lokcek56

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-lokcek56' package and monitor your dependencies for any similar malicious packages. You can also use tools like Vulert to check your package-lock.json for vulnerabilities without needing to install any software.

Conclusion

The 'nokire-lokcek56' package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers are advised to remove this package and monitor their dependencies closely to avoid potential exploitation. Utilizing tools like Vulert can enhance security by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for nokire-lokcek56 →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.

You can use Vulert's playground to analyze your package-lock.json file for vulnerabilities related to the nokire-lokcek56 package.

You should uninstall the package immediately using 'npm uninstall nokire-lokcek56' and check for any other affected packages.

Yes, Vulert can monitor your open-source dependencies in real-time and alert you to any vulnerabilities.

Using compromised packages can lead to data breaches, unauthorized access, and other security risks for your application.

How To Fix

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

npm uninstall nokire-lokcek56

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