Malicious Code Injection in relative_capybara_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96261: Malicious code in relative_capybara_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 'relative_capybara_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. It is associated with the tea.xyz token reward campaign, which has been linked to numerous malicious packages flooding the npm registry. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in 'relative_capybara_z3n' stems from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This behavior not only compromises the integrity of the package but also affects the overall trustworthiness of the npm ecosystem, potentially leading to security breaches and misuse of developer credentials.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall relative_capybara_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 'relative_capybara_z3n' package and monitor your application for any dependencies that may inadvertently include it. Regularly audit your package-lock.json file to identify and remove any suspicious packages.
Conclusion
The 'relative_capybara_z3n' package poses a significant threat due to its malicious code that alters package metadata and affects the npm ecosystem. It is essential to remove this package from your project and implement best practices for dependency management to safeguard your applications.
See every vulnerability recorded for relative_capybara_z3n →
FAQ
The primary risk is the injection of malicious code that modifies package metadata, leading to potential security breaches and the pollution of the npm registry.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the package immediately using 'npm uninstall relative_capybara_z3n' and review your other dependencies for any potential risks.
There are no patches for the 'relative_capybara_z3n' package since it is recommended to remove it entirely from your project.
Regularly audit your dependencies, use trusted packages, and monitor your project with tools like Vulert to stay informed about potential vulnerabilities.
