Malicious Code Injection in spicy_spider-appteadev: npm Package Vulnerability
Summary
MAL-2025-109011: Malicious code in spicy_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 spicy_spider-appteadev package is part of the npm ecosystem, often utilized for various development tasks. However, it has been identified as part of a malicious campaign associated with the tea.xyz token reward initiative. This package is designed to manipulate npm's publishing system, leading to potential security risks for developers and users alike.
Vulnerability Detail
The vulnerability stems from the package's inclusion in a malicious campaign that floods the npm registry with derivative packages. It contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores fraudulently but also pollutes the npm registry, making it difficult for users to trust legitimate packages. The malicious payload can lead to unauthorized access and exploitation of systems relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall spicy_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 avoid using the spicy_spider-appteadev package altogether. If it is already in use, consider replacing it with a trusted alternative that does not exhibit malicious behavior. Additionally, you can use the following command to uninstall the package: npm uninstall spicy_spider-appteadev.
Conclusion
The spicy_spider-appteadev package poses significant security risks due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remove this package and monitor their dependencies closely to avoid potential exploitation. Utilizing tools like Vulert can aid in maintaining a secure development environment.
See every vulnerability recorded for spicy_spider-appteadev →
FAQ
The vulnerability involves malicious code that alters package metadata and floods the npm registry with fake packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using this package can lead to unauthorized access, exploitation of your application, and a compromised development environment.
Regularly audit your dependencies, use trusted sources, and employ tools like Vulert to monitor for vulnerabilities in your packages.
Immediately remove the package and replace it with a secure alternative. Conduct a security audit of your application to ensure no malicious code has been executed.
