Malicious Code Vulnerability in nokire-nakala76 Package

nokire-nakala76 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-163032: Malicious code in nokire-nakala76 (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 nokire-nakala76 package is part of the npm ecosystem and has been identified as part of a larger campaign that aims to exploit the npm registry. This package is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages with the intent of inflating developer reputation scores. The malicious nature of this package compromises its integrity and poses risks to developers and users alike.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the nokire-nakala76 package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The primary goal of this malicious activity is to continuously republish variants of the package, thereby polluting the npm registry and potentially leading to reputational damage for developers and security risks for users. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with such harmful packages.

How To Fix

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

npm uninstall nokire-nakala76

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 prevent the installation of the nokire-nakala76 package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include this package in its dependencies. You can also use the following command to audit your project for vulnerabilities: 'npm audit'.

Conclusion

The nokire-nakala76 package poses a significant security risk due to its malicious code designed to manipulate package metadata and republish variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for nokire-nakala76 →

Share this vulnerability

FAQ

The nokire-nakala76 package is an npm package that has been identified as malicious, part of a campaign to exploit the npm registry.

The vulnerability can lead to the modification of your project's package.json file, potentially compromising its integrity and security.

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

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

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

How To Fix

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

npm uninstall nokire-nakala76

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