Malicious Code Detected in Respective Meerkat-Apptea Package: npm Vulnerability
Summary
MAL-2025-107962: Malicious code in respective_meerkat-apptea (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 respective_meerkat-apptea package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package being part of a campaign that floods npm with malicious packages. It includes scripts that automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can potentially harm developers and users relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall respective_meerkat-appteaIf 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 prevent the installation of this package by using the following command to uninstall it: npm uninstall respective_meerkat-apptea. Additionally, consider using npm audit to identify and address other vulnerabilities in your project.
Conclusion
The respective_meerkat-apptea package has been identified as containing malicious code that poses a significant risk to developers and users within the npm ecosystem. It is crucial to remove this package and monitor your projects for similar vulnerabilities to maintain security and integrity.
See every vulnerability recorded for respective_meerkat-apptea →
FAQ
The malicious code can lead to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising their projects.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your package-lock.json file for any affected packages.
Regularly audit your dependencies using npm audit and consider using tools like Vulert to monitor for vulnerabilities in real-time.
If immediate removal is not possible, ensure that your project is isolated and monitor it closely for any unusual behavior while planning for a future update.
Detailed information can be found in the vulnerability report from Amazon Inspector, which outlines the specifics of the malicious behavior associated with this package.
