Malicious Code Injection in nokire-zabuza97: A Threat to npm Packages
Summary
MAL-2025-163592: Malicious code in nokire-zabuza97 (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-zabuza97' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a target for malicious exploitation.
Vulnerability Detail
The vulnerability in 'nokire-zabuza97' stems from its malicious payload, which 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, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to the broader issue of token reward campaigns that incentivize such malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall nokire-zabuza97If 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-zabuza97' package from your project by executing: 'npm uninstall nokire-zabuza97'. This will prevent any malicious code from executing while you seek a secure alternative.
Conclusion
The 'nokire-zabuza97' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to stay informed about such vulnerabilities and take proactive measures to secure their applications.
See every vulnerability recorded for nokire-zabuza97 →
FAQ
The main issue is that it contains malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using this package can lead to the pollution of the npm registry, compromising the integrity of your application and potentially exposing it to further vulnerabilities.
Regularly updating packages, using tools like Vulert for monitoring, and being cautious with package sources can help prevent such vulnerabilities.
If an immediate update is not possible, uninstall the package to mitigate risks until a secure version is available.
