Malicious Code Injection in individual_frog_z3n Package
Summary
MAL-2025-95004: Malicious code in individual_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 individual_frog_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through the generation and publication of derivative packages. However, it has been identified as containing malicious scripts that compromise its integrity and the npm registry.
Vulnerability Detail
The vulnerability in the individual_frog_z3n package stems from malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards while polluting the npm registry with numerous derivative packages. The malicious payload can lead to security risks for developers and users who inadvertently install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall individual_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 this package by using npm's package-lock.json file to monitor dependencies. Additionally, consider using tools like Vulert to identify and alert for vulnerabilities in your project. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The individual_frog_z3n package contains malicious code that poses significant risks to developers and users. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for individual_frog_z3n →
FAQ
The individual_frog_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The malicious code modifies your package.json, removes private flags, and creates numerous unwanted packages, which can lead to security vulnerabilities and clutter in the npm registry.
It is recommended to remove the individual_frog_z3n package from your project immediately and check for any dependencies that may rely on it.
Yes, 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.
