Malicious Code Injection in equivalent_trout_z3n: A Threat to npm Packages
Summary
MAL-2025-94285: Malicious code in equivalent_trout_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_trout_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly incorporate these malicious packages into their projects.
Vulnerability Detail
The vulnerability in 'equivalent_trout_z3n' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to security risks for developers who rely on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall equivalent_trout_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
Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package from your project.
Conclusion
The 'equivalent_trout_z3n' package presents a significant security risk due to its malicious behavior of modifying package files and republishing variants. Developers should take immediate action to remove this package and monitor their dependencies closely to avoid similar vulnerabilities in the future.
See every vulnerability recorded for equivalent_trout_z3n →
FAQ
The primary risk is that it modifies your package.json file and republishes variants, which can lead to security vulnerabilities and clutter in the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately using the command 'npm uninstall equivalent_trout_z3n' and audit your dependencies for any other malicious packages.
It is recommended to use well-known and trusted packages that have been vetted by the community. Always check the package's reputation and reviews before installation.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about the latest security advisories in the open-source community.
