Malicious Code Injection in nokire-zabuza5: A Threat to npm Users
Summary
MAL-2025-163540: Malicious code in nokire-zabuza5 (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-zabuza5' is part of the npm ecosystem and has been identified as a component of a malicious campaign targeting developers. It is designed to manipulate package metadata and inflate developer reputation scores through automated scripts. This package, like others in its category, poses significant risks to the integrity of the npm registry and the security of applications relying on it.
Vulnerability Detail
The vulnerability in 'nokire-zabuza5' originates from its involvement in the tea.xyz token reward campaign, which floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. This can result in compromised applications and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zabuza5If 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 measure, you can prevent the installation of this malicious package by using the following command to audit your npm packages: 'npm audit'. This will help identify and mitigate risks associated with vulnerable packages.
Conclusion
The 'nokire-zabuza5' package poses a significant security risk due to its malicious code designed to manipulate npm package metadata. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action is required to mitigate the risks associated with this package.
See every vulnerability recorded for nokire-zabuza5 →
FAQ
The primary threat is the injection of malicious code that modifies package metadata, leading to potential security breaches and compromised applications.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you have installed nokire-zabuza5, you should remove it immediately and check for any other affected packages in your project.
Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time about open-source vulnerabilities.
Using compromised packages can lead to data breaches, loss of user trust, and significant security risks for your applications.
