Malicious Code Injection in nokire-zabuza65: A Threat to npm Ecosystem
Summary
MAL-2025-163557: Malicious code in nokire-zabuza65 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'nokire-zabuza65' is part of a larger campaign targeting the npm ecosystem, specifically associated with the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores in exchange for token rewards, which poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the 'nokire-zabuza65' package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, leading to pollution of the npm registry. This not only affects the reputation of legitimate developers but also creates potential security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zabuza65If 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 this malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that you do not include 'nokire-zabuza65' in your package.json file. You can also use Vulert to monitor for vulnerabilities in your project without requiring code access. Visit https://vulert.com/scanner to check if your application is affected.
Conclusion
The 'nokire-zabuza65' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is crucial for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for nokire-zabuza65 →
FAQ
'nokire-zabuza65' is an npm package involved in a malicious campaign aimed at inflating developer reputation scores through the publication of numerous derivative packages.
This vulnerability can lead to the pollution of the npm registry, potentially introducing insecure packages into your application and affecting its overall security.
You should immediately remove the package from your project and monitor for any updates or patches that may be released.
Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without needing code access.
Detailed information can be found in the vulnerability report on the official npm registry or by visiting Vulert's website.
