Malicious Code Injection in future_spider-appteadev Package
Summary
MAL-2025-103003: Malicious code in future_spider-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 future_spider-appteadev package is part of the npm ecosystem, often utilized in various applications for its functionalities. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing system. This package is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages that compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the future_spider-appteadev package. This code is designed to manipulate the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, which can lead to pollution of the npm registry and potentially damage the reputation of developers. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall future_spider-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 future_spider-appteadev package from your project until a secure version is released. This can be done by executing the following command: npm uninstall future_spider-appteadev.
Conclusion
The future_spider-appteadev package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with unwanted variants. It is crucial to take immediate action by updating or removing the package to protect your application from potential threats.
See every vulnerability recorded for future_spider-appteadev →
FAQ
It is an npm package that has been identified as part of a malicious campaign designed to exploit the npm registry.
The malicious code modifies your package.json file and can lead to the creation of numerous derivative packages that pollute the npm registry.
You should uninstall the package immediately and check for any updates or patches that may be released.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
