Malicious Code Injection in strange_toad_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-98949: Malicious code in strange_toad_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 strange_toad_z3n package 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 npm's publishing capabilities. It is designed to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards associated with the tea.xyz protocol.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the strange_toad_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The result is a polluted npm registry, which can compromise the integrity of the ecosystem and potentially expose users to further security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall strange_toad_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 avoid using the strange_toad_z3n package and any packages that may have been derived from it. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks.
Conclusion
The strange_toad_z3n package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry with derivative packages. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for strange_toad_z3n →
FAQ
strange_toad_z3n is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the pollution of the npm registry and may expose your application to further security risks if malicious packages are inadvertently used.
If you have installed the strange_toad_z3n package, you should uninstall it immediately using the command npm uninstall strange_toad_z3n.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
