Malicious Code Injection in equivalent_dolphin_z3n: A Threat to npm Packages
Summary
MAL-2025-102159: Malicious code in equivalent_dolphin_z3n (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 'equivalent_dolphin_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'equivalent_dolphin_z3n' originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages and applications that depend on it.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall equivalent_dolphin_z3nIf 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 prevent the installation of this malicious package by using the following command to uninstall it: npm uninstall equivalent_dolphin_z3n. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The 'equivalent_dolphin_z3n' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for equivalent_dolphin_z3n →
FAQ
The vulnerability involves malicious code that modifies package.json files and floods the npm registry with derivative packages.
You can use Vulert, which monitors your package-lock.json for vulnerabilities, to check if your application is affected.
Remove the package using 'npm uninstall equivalent_dolphin_z3n' and check for any other affected packages.
Regularly audit your dependencies and use tools like Vulert to stay informed about vulnerabilities in your packages.
Failing to address this vulnerability can lead to compromised applications, reputation damage, and potential security breaches.
