Malicious Code Injection in close_meerkat_z3n Package
Summary
MAL-2025-93585: Malicious code in close_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 close_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 security of applications that depend on it.
Vulnerability Detail
The vulnerability in the close_meerkat_z3n package originates from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for dependency confusion attacks and the introduction of untrusted code into applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall close_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, you can remove the close_meerkat_z3n package from your project by executing the following command: npm uninstall close_meerkat_z3n. This will prevent the execution of any malicious code associated with the package until a fix is available.
Conclusion
The close_meerkat_z3n package contains a serious vulnerability due to its malicious code that alters package metadata and repackages itself. It is crucial to address this issue by updating or removing the package to protect your application from potential security threats.
See every vulnerability recorded for close_meerkat_z3n →
FAQ
The close_meerkat_z3n package is an npm package that was part of a token reward campaign, designed to generate and publish derivative packages automatically.
The vulnerability can introduce malicious code into your application, potentially leading to security breaches and untrusted code execution.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If you cannot update the package, consider removing it and replacing it with a secure alternative to mitigate the risks associated with the vulnerability.
