Malicious Code Injection in expensive_snipe-apptea Package
Summary
MAL-2025-102375: Malicious code in expensive_snipe-apptea (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 expensive_snipe-apptea package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been compromised to include malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. It contains scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the pollution of the npm registry, potentially affecting developers' reputations and the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall expensive_snipe-apptea
If 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 expensive_snipe-apptea package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The expensive_snipe-apptea package has been identified as containing malicious code that can compromise the integrity of projects using it. It is crucial to remove this package and monitor your dependencies for any vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for expensive_snipe-apptea →
FAQ
The malicious code can lead to unauthorized modifications of your project's package.json, potentially compromising your project's integrity and reputation.
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.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities. Additionally, only use packages from trusted sources.
Remove the expensive_snipe-apptea package immediately and check your project for any unauthorized changes. Consider using a secure alternative.
Yes, you can report vulnerabilities to the npm security team or through platforms like GitHub where the package is hosted.