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

nokire-nakala63 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163018: Malicious code in nokire-nakala63 (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-nakala63' 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. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in 'nokire-nakala63' originates from its design to automatically generate and publish derivative packages with randomized names. This malicious behavior includes modifying the package.json file to remove private flags, changing version numbers, and continuously republishing variants to pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as well as the degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall nokire-nakala63

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, avoid using the 'nokire-nakala63' package and monitor your project for any dependencies that may indirectly include it. You can also use tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.

Conclusion

The 'nokire-nakala63' package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is essential for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for nokire-nakala63 →

Share this vulnerability

FAQ

The 'nokire-nakala63' package is an npm package associated with a malicious campaign that aims to inflate developer reputation scores through automated publishing of derivative packages.

This vulnerability can lead to the inclusion of malicious code in your project, potentially compromising security and stability.

You should uninstall the package immediately using 'npm uninstall nokire-nakala63' and check your project for any other affected dependencies.

Regularly audit your dependencies, use trusted packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.

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

How To Fix

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

npm uninstall nokire-nakala63

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