Malicious Code Injection in relative_wallaby_z3n: A Threat to npm Packages
Summary
MAL-2025-96262: Malicious code in relative_wallaby_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_wallaby_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 significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'relative_wallaby_z3n' stems from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to compromised developer accounts, loss of trust in the npm ecosystem, and potential exploitation of users who unknowingly install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall relative_wallaby_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 'relative_wallaby_z3n' package and instead look for alternative packages that provide similar functionality without the associated risks. Regularly audit your project's dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'relative_wallaby_z3n' package poses a significant threat due to its malicious code designed to manipulate npm package metadata. Users are advised to uninstall this package and regularly audit their dependencies to maintain the security of their applications. Utilizing tools like Vulert can further enhance your ability to monitor and respond to vulnerabilities in real-time.
See every vulnerability recorded for relative_wallaby_z3n →
FAQ
The vulnerability involves malicious code that alters package metadata and floods the npm registry with harmful variants.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using compromised packages can lead to security breaches, data loss, and damage to your application's reputation.
Regularly audit your dependencies, use trusted sources, and keep your packages updated to minimize the risk of vulnerabilities.
Immediately uninstall the package using 'npm uninstall relative_wallaby_z3n' and review your project's dependencies for any other potential threats.
