Malicious Code Injection in troubled_eel_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-109849: Malicious code in troubled_eel_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
troubled_eel_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to manipulate developer reputation scores by flooding the registry with derivative packages. The package's functionality is compromised, leading to potential security risks for users and developers relying on it.
Vulnerability Detail
The vulnerability in troubled_eel_z3n originates from its design to include malicious scripts that automatically modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, contributing to the pollution of the npm registry. The ramifications include the potential for unauthorized access to sensitive information, as well as the degradation of the integrity of the npm ecosystem. The malicious payload can lead to further exploitation if not addressed promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall troubled_eel_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 file to monitor dependencies. Ensure that your project does not include troubled_eel_z3n in its dependencies. You can also use Vulert to monitor your project for vulnerabilities in real-time without requiring code access. Visit https://vulert.com/scanner to check if your application is affected.
Conclusion
The troubled_eel_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for troubled_eel_z3n →
FAQ
troubled_eel_z3n is an npm package identified as part of a malicious campaign that manipulates the npm registry.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing sensitive data and degrading the integrity of your project.
You should uninstall the package immediately using the command: npm uninstall troubled_eel_z3n.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. Visit https://vulert.com for more information.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without requiring a signup.
