Malicious Code Injection in nokire-lokcek29: A Threat to npm Users

nokire-lokcek29 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162782: Malicious code in nokire-lokcek29 (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-lokcek29' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. The primary function of these packages is to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only undermines the integrity of the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in 'nokire-lokcek29' originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a loss of trust in the npm ecosystem, potential data breaches, and exploitation of developers who rely on these packages for their projects.

How To Fix

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

npm uninstall nokire-lokcek29

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 package dependencies using tools like Vulert, which allows you to check for vulnerabilities in your project without requiring access to the code or installation. You can use the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability.

Conclusion

The 'nokire-lokcek29' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant about the packages they use and to take proactive measures to secure their projects against such vulnerabilities. By utilizing tools like Vulert, developers can monitor their dependencies and ensure their applications remain safe.

See every vulnerability recorded for nokire-lokcek29 →

Share this vulnerability

FAQ

Nokire-lokcek29 is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.

You should immediately uninstall the package using 'npm uninstall nokire-lokcek29' and review your project for any other potentially harmful dependencies.

Regularly update your dependencies, use trusted packages, and employ tools like Vulert to monitor for vulnerabilities in your project.

You can find detailed information about this vulnerability in the Open Source Vulnerability database or by using monitoring tools like Vulert.

How To Fix

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

npm uninstall nokire-lokcek29

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