Malicious Code Vulnerability in worried_cod-gooddev Package
Summary
MAL-2025-111005: Malicious code in worried_cod-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 worried_cod-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 identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the worried_cod-gooddev package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall worried_cod-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 worried_cod-gooddev package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package-lock.json file for any vulnerabilities using tools like Vulert.
Conclusion
The worried_cod-gooddev package has been identified as containing malicious code that poses significant risks to developers and the integrity of the npm registry. It is essential to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for worried_cod-gooddev →
FAQ
The worried_cod-gooddev package is an npm package that is part of a token reward campaign, designed to automatically generate and publish derivative packages.
The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to security vulnerabilities and pollution of the npm registry.
You should uninstall the worried_cod-gooddev package immediately using the command: npm uninstall worried_cod-gooddev.
You can use Vulert to monitor your project for vulnerabilities in real-time by analyzing your package-lock.json file. You can check your application using the Vulert playground without any signup.
Yes, you should look for alternative packages that provide similar functionality without the associated risks of malicious code.
