Malicious Code Injection in other_marmot_z3n: A Threat to npm Packages
Summary
MAL-2025-89331: Malicious code in other_marmot_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 'other_marmot_z3n' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores in exchange for token rewards. Its functionality is compromised due to the presence of malicious scripts that modify important package metadata.
Vulnerability Detail
The vulnerability in 'other_marmot_z3n' stems from malicious code that alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants that pollute the npm registry, potentially harming developers and users by introducing unreliable and possibly harmful packages. The origin of this vulnerability is linked to a campaign aimed at exploiting the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall other_marmot_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 'other_marmot_z3n' package from your project by executing the following command: npm uninstall other_marmot_z3n. This will prevent any malicious scripts from executing until a fix is applied.
Conclusion
The 'other_marmot_z3n' package is compromised by malicious code that alters critical package metadata, posing a significant risk to users and developers. It is crucial to take immediate action by updating or removing the package to safeguard your projects.
See every vulnerability recorded for other_marmot_z3n →
FAQ
The malicious code modifies package.json to remove private flags and changes version numbers, allowing for the automatic generation and publishing of derivative packages.
This vulnerability can lead to the introduction of unreliable packages into your project, potentially compromising its integrity and security.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground.
If you are using 'other_marmot_z3n', you should uninstall the package and check for updates or alternatives to ensure your project remains secure.
You can find detailed information about this vulnerability in the official npm advisory or by checking the malicious packages database.
