Malicious Code Injection in steady_frog_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-90747: Malicious code in steady_frog_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
steady_frog_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm registry with numerous derivative packages. The primary functionality of this package is to facilitate the automatic generation and publication of these derivative packages, which are designed to inflate developer reputation scores for token rewards. However, its malicious nature poses significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in steady_frog_z3n 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 these variants, effectively polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation of these malicious packages. The ramifications include compromised developer reputations, potential security risks for applications using these packages, and a cluttered npm registry that makes it difficult for legitimate packages to be discovered.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall steady_frog_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 steady_frog_z3n package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can utilize Vulert to monitor your project for any vulnerabilities by checking your package-lock.json file.
Conclusion
The steady_frog_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the affected package, and utilize tools like Vulert to monitor their projects for any potential vulnerabilities.
See every vulnerability recorded for steady_frog_z3n →
FAQ
steady_frog_z3n is an npm package linked to a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project's dependencies and potentially exposing your application to security risks.
You should uninstall the steady_frog_z3n package immediately using the command 'npm uninstall steady_frog_z3n' and ensure your project does not reference it.
You can use Vulert, which allows you to monitor and alert for open-source vulnerabilities in your software by simply analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
