Malicious Code Injection in imefcf-devapptea: A Threat to npm Ecosystem
Summary
MAL-2025-103964: Malicious code in imefcf-devapptea (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
imefcf-devapptea is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various functionalities, but it has been compromised to include malicious scripts. These scripts are intended to manipulate the npm registry by generating and publishing derivative packages with altered metadata, thereby inflating developer reputation scores.
Vulnerability Detail
The vulnerability in imefcf-devapptea stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The malicious payload can have significant ramifications, including the potential for developers to unknowingly install compromised packages, which can lead to further security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall imefcf-devappteaIf 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 remove the imefcf-devapptea package from your project by executing: npm uninstall imefcf-devapptea. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The imefcf-devapptea package has been identified as containing malicious code that compromises the integrity of the npm ecosystem. It is crucial for developers to remain vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their applications from potential threats.
See every vulnerability recorded for imefcf-devapptea →
FAQ
The vulnerability involves malicious code that modifies package metadata to inflate developer reputation scores and pollute the npm registry.
You can use Vulert, which monitors open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected without any signup.
Using the compromised package can lead to security breaches, as it may introduce malicious code into your application, affecting its integrity and security.
Regularly updating packages, using tools like Vulert for monitoring vulnerabilities, and auditing dependencies can help prevent similar issues.
If you have installed the compromised package, it is recommended to uninstall it immediately and check for any updates or patches.
