Malicious Code Vulnerability in nokire-zabuza7 Package
Summary
MAL-2025-163562: Malicious code in nokire-zabuza7 (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 nokire-zabuza7 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in the nokire-zabuza7 package stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially harm developers by inflating reputation scores fraudulently. 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 malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zabuza7If 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-zabuza7 package entirely and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The nokire-zabuza7 package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is crucial for developers to uninstall this package and monitor their projects for any vulnerabilities to maintain security and integrity.
See every vulnerability recorded for nokire-zabuza7 →
FAQ
The nokire-zabuza7 package is an npm package that is part of a campaign to generate and publish derivative packages for token rewards, but it has been identified as containing malicious code.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your project's integrity and security.
You should uninstall the nokire-zabuza7 package immediately using 'npm uninstall nokire-zabuza7' and check for any dependencies that may be affected.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground.
Regularly update your dependencies, monitor your package-lock.json file for changes, and utilize tools like Vulert to stay informed about potential vulnerabilities.
