Malicious Code Injection in troubled_lynx_z3n Package
Summary
MAL-2025-109853: Malicious code in troubled_lynx_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 troubled_lynx_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through automated publishing of malicious variants.
Vulnerability Detail
The vulnerability in the troubled_lynx_z3n package originates from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then continuously republished to pollute the npm registry. The ramifications include potential security risks for developers who unknowingly install these malicious packages, leading to compromised systems and loss of integrity in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall troubled_lynx_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 avoid using the troubled_lynx_z3n package until a secure version is released. Additionally, consider using npm audit to check for vulnerabilities in your project and remove any affected packages.
Conclusion
The troubled_lynx_z3n package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remain vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for troubled_lynx_z3n →
FAQ
troubled_lynx_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The malicious code modifies your package.json file, potentially leading to the installation of compromised packages that can harm your project and system.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed the troubled_lynx_z3n package, it is recommended to remove it immediately and update your project dependencies to ensure security.
Yes, tools like Vulert can help monitor your project for vulnerabilities in real-time using just your package-lock.json file.
