Malicious Code Injection in conventional_scallop-gooddev Package
Summary
MAL-2025-100969: Malicious code in conventional_scallop-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 conventional_scallop-gooddev package is part of the npm ecosystem, often utilized in JavaScript projects for various development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, which can compromise the integrity of projects relying on it.
Vulnerability Detail
The vulnerability stems from the package being associated with the tea.xyz token reward campaign, which employs scripts to automatically generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry and potential exploitation of developer reputation scores.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall conventional_scallop-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 conventional_scallop-gooddev package altogether and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The conventional_scallop-gooddev package poses a significant risk due to its association with malicious activities aimed at manipulating the npm registry. It is crucial for developers to remove this package and monitor their projects for any vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for conventional_scallop-gooddev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and potentially compromise the integrity of your project by introducing malicious code.
You should uninstall the conventional_scallop-gooddev package immediately and monitor your project for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your 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.
