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

nokire-nana92 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163251: Malicious code in nokire-nana92 (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-nana92' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to generate and publish numerous derivative packages with randomized names, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol. The malicious nature of this package poses significant risks to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in 'nokire-nana92' originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically 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, dependency confusion, and a compromised development environment.

How To Fix

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

npm uninstall nokire-nana92

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 measure, you can avoid using 'nokire-nana92' and any packages that may have been derived from it. Regularly audit your package-lock.json file to identify and remove any suspicious packages. You can also use tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The 'nokire-nana92' package represents a significant threat to npm users due to its malicious intent to manipulate package metadata and flood the registry. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure their projects are secure.

See every vulnerability recorded for nokire-nana92 →

Share this vulnerability

FAQ

'nokire-nana92' is an npm package identified as part of a malicious campaign that modifies package metadata and floods the npm registry with derivative packages.

The vulnerability can lead to security risks, dependency confusion, and potential exposure to malicious code, compromising the integrity of your project.

You should uninstall 'nokire-nana92' immediately and audit your project for any other potentially malicious packages.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall nokire-nana92

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