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

nokire-nana11 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163162: Malicious code in nokire-nana11 (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-nana11' 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. The primary functionality of such packages is to inflate developer reputation scores through automated publishing of derivative packages, often leading to a polluted registry and potential security risks.

Vulnerability Detail

The vulnerability in 'nokire-nana11' originates from its involvement in a malicious campaign designed to manipulate the npm registry. The package contains scripts that modify the 'package.json' file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious packages, leading to potential data breaches or system compromises.

How To Fix

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

npm uninstall nokire-nana11

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, avoid using the 'nokire-nana11' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your 'package-lock.json' file for real-time alerts on open-source vulnerabilities.

Conclusion

The 'nokire-nana11' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating the registry. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to safeguard their projects from potential vulnerabilities.

See every vulnerability recorded for nokire-nana11 →

Share this vulnerability

FAQ

'nokire-nana11' is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity.

You should uninstall 'nokire-nana11' immediately and check for any other potentially affected packages in your project.

Regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in real-time.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing your 'package-lock.json'. You can check for vulnerabilities without signing up by using the Vulert playground.

How To Fix

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

npm uninstall nokire-nana11

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