Malicious Code Injection in loyal_frog_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-105360: Malicious code in loyal_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 loyal_frog_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 related to the tea.xyz token reward system. It is designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered names and metadata, thereby inflating developer reputation scores.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the loyal_frog_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, contributing to the pollution of the npm registry. The malicious payload is designed to continuously republish these variants, which can lead to significant reputational damage for developers and potential security risks for users who unknowingly install these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall loyal_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 loyal_frog_z3n package and any packages that depend on it. Regularly audit your package-lock.json file to identify and remove any potentially malicious packages. You can also utilize tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The loyal_frog_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and flood the registry. 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 loyal_frog_z3n →
FAQ
The loyal_frog_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The malicious code can alter your package metadata, remove private flags, and flood the npm registry with derivative packages, potentially harming your project's reputation and security.
You can use the Vulert platform to monitor your application for vulnerabilities. By analyzing your package-lock.json file, Vulert can alert you to any open-source vulnerabilities.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid installing packages from untrusted sources.
If you have installed the loyal_frog_z3n package, you should uninstall it immediately using npm uninstall loyal_frog_z3n and check for any dependencies that may be affected.
