Malicious Code Injection in orthodox_guppy_z3n: A Threat to npm Packages
Summary
MAL-2025-106807: Malicious code in orthodox_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 'orthodox_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. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'orthodox_guppy_z3n' originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which can pollute the npm registry and compromise the security of applications relying on these packages. The malicious payload can potentially allow unauthorized access to sensitive data or lead to the execution of harmful code within affected applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall orthodox_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 temporary measure, you can avoid using the 'orthodox_guppy_z3n' package and replace it with a trusted alternative. Always verify the integrity and source of packages before including them in your project.
Conclusion
The 'orthodox_guppy_z3n' package poses a significant threat due to its malicious code that alters package metadata and can lead to the pollution of the npm registry. It is essential to uninstall this package and monitor your dependencies closely to maintain the security of your applications.
See every vulnerability recorded for orthodox_guppy_z3n →
FAQ
The primary risk is that it contains malicious code that modifies package metadata and can lead to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
You should immediately uninstall the package using 'npm uninstall orthodox_guppy_z3n' and review your project's dependencies for any other potentially malicious packages.
Yes, always look for well-reviewed and actively maintained packages that serve the same purpose as orthodox_guppy_z3n.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
