Malicious Code Injection in subsequent_frog_z3n Package
Summary
MAL-2025-96835: Malicious code in subsequent_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
The subsequent_frog_z3n package is part of the npm ecosystem, often associated with the tea.xyz token reward campaign. This package is designed to facilitate automated publishing of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the subsequent_frog_z3n package arises from malicious code that modifies the package.json file to remove private flags and alter version numbers. This code generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. The origin of this vulnerability is linked to a broader trend of malicious packages flooding the npm ecosystem, aimed at exploiting the token reward system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall subsequent_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 prevent the installation of the subsequent_frog_z3n package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include this package by checking your package.json and removing any references to it.
Conclusion
The subsequent_frog_z3n package poses a significant risk due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial to remove this package and monitor your project for vulnerabilities using tools like Vulert to ensure ongoing security.
See every vulnerability recorded for subsequent_frog_z3n →
FAQ
It is an npm package associated with automated publishing and token reward campaigns, but it has been identified as containing malicious code.
The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and polluting the npm registry.
You should uninstall the package immediately using 'npm uninstall subsequent_frog_z3n' and check for any other affected packages.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
