Malicious Code Injection in classical_guppy_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-100578: Malicious code in classical_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 package classical_guppy_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in classical_guppy_z3n stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. This code generates random package names and continuously republishes variants, leading to pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages to inflate developer reputation scores.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall classical_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 temporarily avoid using the classical_guppy_z3n package and monitor your project for any dependencies that may rely on it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The classical_guppy_z3n package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry. It is crucial to remove this package and monitor your dependencies to maintain the integrity of your projects.
See every vulnerability recorded for classical_guppy_z3n →
FAQ
classical_guppy_z3n is an npm package that has been identified as malicious, primarily associated with the tea.xyz token reward campaign.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your project's integrity and security.
You should uninstall the classical_guppy_z3n package immediately and monitor your project for any other affected dependencies.
Regularly audit your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without requiring any signup.
