Malicious Code Injection in marked_meerkat_z3n: A Threat to npm Packages
Summary
MAL-2025-88313: Malicious code in marked_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
marked_meerkat_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the campaign, is designed to manipulate package metadata and inflate developer reputation scores through automated publishing of derivative packages. The malicious nature of this package poses significant risks to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in marked_meerkat_z3n originates from its association with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. These packages contain scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall marked_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 marked_meerkat_z3n and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like Vulert to monitor for vulnerabilities.
Conclusion
The marked_meerkat_z3n package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for marked_meerkat_z3n →
FAQ
marked_meerkat_z3n is an npm package identified as part of a malicious campaign that manipulates package metadata.
This vulnerability can lead to the pollution of the npm registry and may introduce security risks into your application by allowing malicious code to be executed.
You should uninstall the package immediately using 'npm uninstall marked_meerkat_z3n' and check your package-lock.json for any references.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, consider using other reputable npm packages that provide similar functionality without the associated risks.
