Malicious Code Injection in disappointed_grouse-appteadev Package
Summary
MAL-2025-101613: Malicious code in disappointed_grouse-appteadev (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 disappointed_grouse-appteadev package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that exploits npm's package management system. This package is linked to the tea.xyz token reward scheme, which has been known to flood the npm registry with derivative packages that can compromise developer reputation scores.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the disappointed_grouse-appteadev package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The primary aim is to continuously republish these variants, polluting the npm registry and potentially leading to security risks for developers who unknowingly use these compromised packages. The malicious payload can inflate the reputation of the attackers while compromising the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall disappointed_grouse-appteadevIf 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 avoid using the disappointed_grouse-appteadev package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The disappointed_grouse-appteadev package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.
See every vulnerability recorded for disappointed_grouse-appteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
Using this package can lead to security risks, including the potential for your project to be associated with malicious activities and compromised integrity.
You should uninstall the package immediately and check for any alternative packages that can fulfill your requirements.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
