Malicious Code Injection in expensive_spoonbill-gooddev Package
Summary
MAL-2025-102376: Malicious code in expensive_spoonbill-gooddev (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_spoonbill-gooddev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious scripts that alter package metadata and republish variants, leading to potential misuse and pollution of the npm registry.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the expensive_spoonbill-gooddev package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload is designed to continuously republish these variants, which can lead to a polluted npm registry and may compromise the integrity of other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall expensive_spoonbill-gooddevIf 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 expensive_spoonbill-gooddev package from your project by executing the following command: npm uninstall expensive_spoonbill-gooddev. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The expensive_spoonbill-gooddev package has been identified as containing malicious code that can compromise the integrity of the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help monitor and manage open-source vulnerabilities effectively.
See every vulnerability recorded for expensive_spoonbill-gooddev →
FAQ
The malicious code can lead to the pollution of the npm registry and compromise the integrity of other packages, potentially affecting applications that rely on them.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply using your package-lock.json file, you can check for vulnerabilities without any installation. Visit Vulert Scanner to use the Vulert playground.
Regularly audit your dependencies using tools like Vulert and keep your packages updated to the latest secure versions to minimize the risk of vulnerabilities.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to prevent any potential exploitation.
Detailed information can be found in the vulnerability report on the GitHub repository for malicious packages or through security advisories related to npm packages.
