Malicious Code Injection in excited_pheasant-gooddev: A Threat to npm Ecosystem
Summary
MAL-2025-102337: Malicious code in excited_pheasant-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 package excited_pheasant-gooddev is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system, often containing scripts that automatically generate and publish derivative packages. This behavior is intended to inflate developer reputation scores for token rewards, making the package a potential threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in excited_pheasant-gooddev stems from its inclusion in a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to the exploitation of unsuspecting developers who may inadvertently use these compromised packages. The origin of this vulnerability is linked to the malicious intent behind the tea.xyz token reward campaign, which aims to manipulate npm's reputation system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall excited_pheasant-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 avoid using the affected package and monitor your package-lock.json file for any unauthorized changes. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The excited_pheasant-gooddev package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and take immediate action to remove this package from their projects. Utilizing tools like Vulert can help in monitoring and preventing such vulnerabilities in the future.
See every vulnerability recorded for excited_pheasant-gooddev →
FAQ
excited_pheasant-gooddev is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising your application's security and integrity.
You should uninstall the package immediately and monitor your project for any unauthorized changes.
Yes, regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
