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

nokire-nana88 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163246: Malicious code in nokire-nana88 (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-nana88' 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 creating numerous derivative packages with random names, which can inflate developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'nokire-nana88' originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also compromises the security and reliability of applications that depend on these packages.

How To Fix

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

npm uninstall nokire-nana88

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 the 'nokire-nana88' package and replace it with a legitimate alternative. Always verify the source of any npm package before installation.

Conclusion

The 'nokire-nana88' package represents a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can safeguard their applications and maintain the integrity of their software.

See every vulnerability recorded for nokire-nana88 →

Share this vulnerability

FAQ

The 'nokire-nana88' package is a malicious npm package that is part of a campaign to inflate developer reputation scores through the creation of numerous derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the security and reliability of applications that depend on affected packages.

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

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Yes, always look for well-reviewed and actively maintained packages on npm that serve the same purpose as 'nokire-nana88' but do not have a history of malicious behavior.

How To Fix

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

npm uninstall nokire-nana88

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