Malicious Code Injection in permanent_wallaby_z3n: A Threat to npm Packages
Summary
MAL-2025-95877: Malicious code in permanent_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 'permanent_wallaby_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publishing of derivative packages. This package is particularly vulnerable due to its inclusion of scripts that manipulate package metadata, potentially leading to reputation inflation and registry pollution.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the package, which includes scripts that modify the package.json file to remove private flags and alter version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior can lead to a polluted registry and can compromise the integrity of the npm ecosystem, affecting developers and users relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall permanent_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 'permanent_wallaby_z3n' package until a fix is released. Additionally, you can monitor your package-lock.json file for any unauthorized changes that may indicate the presence of this malicious package.
Conclusion
The 'permanent_wallaby_z3n' package presents a significant risk due to its malicious code that alters package metadata and floods the npm registry with derivative packages. 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 permanent_wallaby_z3n →
FAQ
The vulnerability involves malicious scripts that alter package metadata and republish variants to the npm registry, leading to potential reputation inflation and registry pollution.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
If you find 'permanent_wallaby_z3n' in your project, you should remove it or update to a patched version if available.
Yes, this vulnerability can affect your development environment by polluting the npm registry and potentially compromising other packages that depend on it.
To prevent such vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and ensure you only install packages from trusted sources.
