Malicious Code Vulnerability in registered_guppy_z3n Package
Summary
MAL-2025-89908: Malicious code in registered_guppy_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 registered_guppy_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package metadata and republishes variants to pollute the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall registered_guppy_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 workaround, you can manually check your package-lock.json file for any references to registered_guppy_z3n and remove it. Additionally, consider using the following command to uninstall the package: npm uninstall registered_guppy_z3n.
Conclusion
The registered_guppy_z3n package contains a significant vulnerability due to its malicious code that alters package metadata and republishes variants. It is crucial to remove this package from your project to protect your application from potential security risks. Monitoring tools like Vulert can help keep your project secure from such vulnerabilities.
See every vulnerability recorded for registered_guppy_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The malicious code can compromise your application's integrity by modifying package metadata and introducing potentially harmful variants.
Currently, there is no patched version available. The best course of action is to remove the package entirely.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
