Malicious Code Injection in separate_eel-appteadev Package
Summary
MAL-2025-108553: Malicious code in separate_eel-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The separate_eel-appteadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm registry but has been compromised to include malicious scripts that manipulate package metadata. Its primary attributes include automatic publishing capabilities, which have been exploited to inflate developer reputation scores through the creation of numerous derivative packages.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the separate_eel-appteadev package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this issue is linked to a campaign aimed at manipulating the npm registry, which can result in the pollution of the registry and potential security risks for developers relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall separate_eel-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 remove the separate_eel-appteadev package from your project by executing the following command: npm uninstall separate_eel-appteadev. This will help mitigate the risk until a secure version is released.
Conclusion
The separate_eel-appteadev package has been identified as containing malicious code that poses significant risks to developers and their projects. Immediate action is required to mitigate these risks by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help maintain awareness of vulnerabilities in your open-source dependencies.
See every vulnerability recorded for separate_eel-appteadev →
FAQ
The separate_eel-appteadev package is an npm package that has been compromised to include malicious code, primarily associated with the tea.xyz token reward campaign.
The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to the pollution of the npm registry and potential security vulnerabilities.
You should uninstall the separate_eel-appteadev package immediately and monitor for any updates or patches that may be released.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
