Malicious Code Vulnerability in possible_emu-teagooddev Package
Summary
MAL-2025-107157: Malicious code in possible_emu-teagooddev (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 possible_emu-teagooddev package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior is indicative of a broader issue within the npm ecosystem, where malicious actors exploit the system for personal gain.
Vulnerability Detail
This vulnerability originates from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The intent is to continuously republish these variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload can lead to security risks, including unauthorized access to sensitive data and the potential for further exploitation of affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall possible_emu-teagooddevIf 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 lock your dependencies. Ensure that you do not include possible_emu-teagooddev in your package.json or package-lock.json files.
Conclusion
The possible_emu-teagooddev package contains malicious code that poses significant risks to developers and their projects. It is crucial to remove this package and monitor your dependencies for any similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your open-source projects.
See every vulnerability recorded for possible_emu-teagooddev →
FAQ
It is a package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.
The vulnerability can lead to unauthorized modifications of your package.json file and the potential pollution of the npm registry, which can compromise your project's integrity.
You should uninstall the package immediately using the command: npm uninstall possible_emu-teagooddev.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
