Malicious Code Injection in warm_kangaroo-appteadev: A Threat to npm Packages
Summary
MAL-2025-110655: Malicious code in warm_kangaroo-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 package 'warm_kangaroo-appteadev' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of such packages is to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability in 'warm_kangaroo-appteadev' originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names to inflate the number of published packages. The ramifications include pollution of the npm registry, potential exposure of sensitive data, and a compromised development environment. The malicious payload is designed to continuously republish variants, making it difficult to track and mitigate the threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall warm_kangaroo-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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include 'warm_kangaroo-appteadev' in its dependencies. You can also use the following command to audit your packages for vulnerabilities: npm audit.
Conclusion
The 'warm_kangaroo-appteadev' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for warm_kangaroo-appteadev →
FAQ
The primary risk is the injection of malicious code that can alter your project's dependencies and compromise your development environment.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should immediately remove the package from your project and audit your dependencies for any other vulnerabilities.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages.
Regularly audit your packages, keep them updated, and use tools like Vulert to monitor for vulnerabilities.
