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

nokire-nana3 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163182: Malicious code in nokire-nana3 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'nokire-nana3' is part of the npm ecosystem, which is widely used for JavaScript package management. It is typically utilized by developers to share and manage code libraries. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores through token rewards.

Vulnerability Detail

The vulnerability in 'nokire-nana3' stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The malicious payload is designed to automate the generation of these packages, making it difficult for developers to identify and mitigate the threat.

How To Fix

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

npm uninstall nokire-nana3

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 'nokire-nana3' by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid any unintended installations of this malicious package.

Conclusion

The 'nokire-nana3' 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 and take immediate action to remove this package and monitor their dependencies for vulnerabilities.

See every vulnerability recorded for nokire-nana3 →

Share this vulnerability

FAQ

'nokire-nana3' is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies.

You should remove the package from your project immediately and check for any other affected packages.

You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

npm uninstall nokire-nana3

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