Malicious Code Injection in representative_trout_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-107911: Malicious code in representative_trout_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 'representative_trout_z3n' is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability in 'representative_trout_z3n' originates from its association with a malicious campaign that floods the npm registry with spam packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional dependency on compromised packages, leading to potential security breaches in applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall representative_trout_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 malicious package by using npm's package-lock.json to lock your dependencies. Additionally, consider using the following command to audit your project for vulnerabilities: npm audit.
Conclusion
The 'representative_trout_z3n' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies to maintain application security.
See every vulnerability recorded for representative_trout_z3n →
FAQ
The vulnerability involves malicious code that modifies package metadata and floods the npm registry with spam packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.
Remove the package from your project and check for any dependencies that may still reference it. Update to a patched version if available.
Yes, relying on compromised packages can lead to security breaches, as they may introduce malicious behavior into your application.
Regularly audit your dependencies using tools like npm audit and monitor for vulnerabilities using services like Vulert.
