Malicious Code Injection in married_weasel-gooddev Package
Summary
MAL-2025-105628: Malicious code in married_weasel-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 married_weasel-gooddev package is part of the npm ecosystem, typically used for various development tasks. However, it has been identified as a malicious package that is involved in the tea.xyz token reward campaign. This package is designed to inflate developer reputation scores by generating and publishing derivative packages with randomized names, thus polluting the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the married_weasel-gooddev package, which contains scripts that modify the package.json file to remove private flags and change version numbers. It generates random Indonesian-themed package names and continuously republishes variants, leading to potential security risks and pollution of the npm registry. This behavior can compromise the integrity of the npm ecosystem and affect developers relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall married_weasel-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 workaround, you can monitor your project for any unauthorized changes to your package.json file and ensure that no malicious packages are installed. Regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.
Conclusion
The married_weasel-gooddev package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to maintain the security of their projects.
See every vulnerability recorded for married_weasel-gooddev →
FAQ
It is an npm package that has been identified as malicious, involved in generating and publishing derivative packages to inflate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing unauthorized changes to your dependencies.
You should uninstall the married_weasel-gooddev package immediately and check your project for any unauthorized changes.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Regularly audit your dependencies, use trusted sources for packages, and consider using tools like Vulert to monitor for vulnerabilities.
