Malicious Code Injection in nokire-zabuza44: A Threat to npm Packages
Summary
MAL-2025-163534: Malicious code in nokire-zabuza44 (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-zabuza44' 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. The primary function of such packages is to manipulate developer reputation scores through the automatic generation and publication of derivative packages.
Vulnerability Detail
The vulnerability in 'nokire-zabuza44' stems from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is designed to inflate developer reputation scores for token rewards while polluting the npm registry with numerous derivative packages. The malicious payload can lead to security risks for developers who unknowingly use these compromised packages, potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zabuza44If 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 remove the 'nokire-zabuza44' package from your project by executing the command: 'npm uninstall nokire-zabuza44'. This will prevent any malicious code from executing in your application until a secure version is available.
Conclusion
The 'nokire-zabuza44' package poses a significant threat due to its malicious code that alters package.json files and floods the npm registry with compromised packages. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications.
See every vulnerability recorded for nokire-zabuza44 →
FAQ
The primary risk is the injection of malicious code that modifies package.json files, potentially leading to security vulnerabilities in applications that use this package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
While specific exploits have not been detailed, the malicious behavior of the package can lead to broader security issues, including unauthorized access to sensitive data.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the npm ecosystem.
