Malicious Code Injection in nokire-nakala15 Package - npm Vulnerability

nokire-nakala15 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162966: Malicious code in nokire-nakala15 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The nokire-nakala15 package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol.

Vulnerability Detail

The vulnerability in the nokire-nakala15 package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but can also mislead developers and users regarding the authenticity of packages.

How To Fix

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

npm uninstall nokire-nakala15

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 avoid using the nokire-nakala15 package and monitor your dependencies for any malicious packages. You can also use tools like Vulert to scan your package-lock.json file for vulnerabilities. Here’s a command to remove the package: npm uninstall nokire-nakala15.

Conclusion

The nokire-nakala15 package poses a significant risk due to its malicious behavior of modifying package metadata and flooding the npm registry. It is crucial for developers to be vigilant about the packages they use and to employ tools like Vulert for real-time monitoring of vulnerabilities.

See every vulnerability recorded for nokire-nakala15 →

Share this vulnerability

FAQ

The nokire-nakala15 package is part of a malicious campaign that floods the npm registry with derivative packages to inflate developer reputation scores.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and misleading developers regarding package authenticity.

You should uninstall the nokire-nakala15 package immediately and monitor your project for any other potentially malicious packages.

You can use tools like Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time using your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall nokire-nakala15

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