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

nokire-akaza24 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-162235: Malicious code in nokire-akaza24 (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 Your last release was probably never penetration tested 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-akaza24 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 the npm registry and inflate developer reputation scores through deceptive practices.

Vulnerability Detail

The vulnerability in nokire-akaza24 originates from its association with a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This manipulation modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, thereby polluting the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may introduce malicious code into their applications.

How To Fix

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

npm uninstall nokire-akaza24

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-akaza24 package and consider replacing it with a trusted alternative. Additionally, you can utilize tools like Vulert to monitor your project for vulnerabilities. For example, you can check your application against this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The nokire-akaza24 package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant, update their packages, and utilize monitoring tools like Vulert to safeguard their applications from such vulnerabilities.

See every vulnerability recorded for nokire-akaza24 →

Share this vulnerability

FAQ

Nokire-akaza24 is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can introduce malicious code into your application, potentially compromising its security and functionality.

If you have installed nokire-akaza24, it is recommended to remove it and update your project to eliminate any potential security risks.

You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner.

To prevent future vulnerabilities, regularly update your dependencies, use trusted packages, and employ tools like Vulert for monitoring.

How To Fix

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

npm uninstall nokire-akaza24

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