Malicious Code Injection in nokire-zabuza63: A Threat to npm Ecosystem
Summary
MAL-2025-163555: Malicious code in nokire-zabuza63 (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-zabuza63' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered names and versions. The primary functionality of these packages is to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'nokire-zabuza63' originates from its design to execute autopublish scripts that modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of unsuspecting developers who may inadvertently use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zabuza63If 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-zabuza63' package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The 'nokire-zabuza63' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and republishes harmful variants. It is essential to remove this package and monitor your dependencies to maintain the integrity of your projects.
See every vulnerability recorded for nokire-zabuza63 →
FAQ
The primary risk is that it modifies package.json files and republishes malicious variants, which can compromise the integrity of your project and the npm registry.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the package immediately using 'npm uninstall nokire-zabuza63' and review your project for any other potentially compromised packages.
Currently, there are no patches available for the nokire-zabuza63 package, so the best course of action is to remove it from your project.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
