Malicious Code Vulnerability in conventional_meerkat_z3n Package
Summary
MAL-2025-93794: Malicious code in conventional_meerkat_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 conventional_meerkat_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially harming developers who rely on the integrity of packages from this ecosystem. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate these actions, making it difficult for users to detect the compromise.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall conventional_meerkat_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, avoid using the conventional_meerkat_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json file is regularly audited for any unauthorized changes.
Conclusion
The conventional_meerkat_z3n package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor for any unauthorized changes to maintain the integrity of your software.
See every vulnerability recorded for conventional_meerkat_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code.
You should uninstall the conventional_meerkat_z3n package immediately and monitor your project for any unauthorized changes.
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.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring any signup.
