Malicious Code Injection in typical_mammal_z3n Package
Summary
MAL-2025-109900: Malicious code in typical_mammal_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 typical_mammal_z3n package 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 publication of derivative packages. This package is particularly vulnerable due to its inclusion of autopublish scripts that can manipulate package metadata and publish malicious variants to the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the typical_mammal_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The primary consequence of this vulnerability is the pollution of the npm registry with numerous derivative packages, which can inflate developer reputation scores fraudulently. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall typical_mammal_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 remove the typical_mammal_z3n package from your project by executing: npm uninstall typical_mammal_z3n. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The typical_mammal_z3n package contains malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to update or remove this package to mitigate potential threats. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for typical_mammal_z3n →
FAQ
It is an npm package involved in the tea.xyz token reward campaign, designed to automate the generation and publication of packages.
The malicious code can alter your package.json, inflate reputation scores, and pollute the npm registry with unwanted packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your packages.
Consider removing the package from your project as a temporary measure until a secure version is available.
