Malicious Code Injection in harsh_emu-appteadev: A Threat to npm Packages
Summary
MAL-2025-103611: Malicious code in harsh_emu-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 harsh_emu-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. Its primary functionality is to facilitate the development and distribution of applications, but it has been compromised to include harmful scripts that can manipulate package metadata.
Vulnerability Detail
The vulnerability in harsh_emu-appteadev originates from its association with a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and creating random package names. This not only pollutes the npm registry but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall harsh_emu-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 measure, you can avoid using the harsh_emu-appteadev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The harsh_emu-appteadev package poses a significant security risk due to its malicious code injection. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. By staying informed and proactive, you can protect your applications from potential threats.
See every vulnerability recorded for harsh_emu-appteadev →
FAQ
The main risk is the potential for malicious code execution, which can compromise the integrity of your application and lead to unauthorized access or data breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file, you can quickly check for vulnerabilities without needing to install any software.
If you have installed the harsh_emu-appteadev package, you should uninstall it immediately and look for alternative packages to avoid potential security risks.
Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your project dependencies effectively.
Vulert is a service that monitors open-source vulnerabilities in your software. It uses your package-lock.json to provide real-time alerts about vulnerabilities, helping you maintain secure applications.
