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

nokire-nanali28 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163280: Malicious code in nokire-nanali28 (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-nanali28' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only compromises the integrity of the npm registry but also poses significant risks to developers who may unknowingly use these packages in their projects.

Vulnerability Detail

The vulnerability in 'nokire-nanali28' originates from its malicious intent to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of variants that pollute the npm registry, making it difficult for developers to identify legitimate packages. The ramifications include potential security breaches, loss of trust in the npm ecosystem, and the risk of integrating compromised code into applications.

How To Fix

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

npm uninstall nokire-nanali28

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-nanali28' package and check your package-lock.json for any dependencies that may have been inadvertently included. You can also use the following command to audit your npm packages for vulnerabilities: 'npm audit'.

Conclusion

The 'nokire-nanali28' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to be vigilant, remove any instances of this package, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for nokire-nanali28 →

Share this vulnerability

FAQ

'nokire-nanali28' is a malicious npm package that is part of a campaign to manipulate developer reputation scores through the automatic generation of derivative packages.

Using 'nokire-nanali28' can lead to the inclusion of malicious code in your project, potentially compromising security and integrity.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If you have used 'nokire-nanali28', uninstall it immediately and review your code for any potential security issues introduced by this package.

Regularly audit your dependencies using 'npm audit', keep your packages updated, and use trusted sources for package installations.

How To Fix

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

npm uninstall nokire-nanali28

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