Malicious Code Detected in puny_crow-gooddev: A Threat to npm Users
Summary
MAL-2025-107421: Malicious code in puny_crow-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
puny_crow-gooddev is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. It is designed to manipulate package metadata and inflate developer reputation scores through the creation of derivative packages. The package's functionality is compromised, making it a potential risk for developers who rely on it for legitimate purposes.
Vulnerability Detail
The vulnerability originates from the package being part of a larger malicious scheme associated with the tea.xyz token reward campaign. It includes scripts that automatically generate and publish derivative packages with randomized names, which can lead to the pollution of the npm registry. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can compromise the integrity of the npm ecosystem and affect developers' projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall puny_crow-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 measure, avoid using the puny_crow-gooddev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can alert you to any open-source vulnerabilities in real-time.
Conclusion
The puny_crow-gooddev package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and flood the npm registry. It is crucial to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert to maintain the integrity of your software.
See every vulnerability recorded for puny_crow-gooddev →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
You should uninstall the package immediately using 'npm uninstall puny_crow-gooddev' and check for any dependencies that may be affected.
Yes, look for other npm packages that provide similar functionality without the associated risks. Always verify the package's reputation before installation.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, ensuring your software remains secure.
