Malicious Code Injection in future_woodpecker-teagooddev Package
Summary
MAL-2025-103004: Malicious code in future_woodpecker-teagooddev (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_woodpecker-teagooddev 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, often with randomized names, to inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on this package. The malicious code is designed to exploit the npm ecosystem for fraudulent purposes, making it a significant threat to developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall future_woodpecker-teagooddev
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 future_woodpecker-teagooddev package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The future_woodpecker-teagooddev package poses a significant security risk due to its malicious code that alters package configurations and pollutes the npm registry. It is crucial for developers to uninstall this package and monitor their projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for future_woodpecker-teagooddev →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The malicious code modifies your package.json, removes private flags, and can lead to the pollution of the npm registry, potentially compromising your application's security.
You should uninstall the package immediately and look for alternatives that do not have known vulnerabilities.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.