Malicious Code Exploit in sorry_clam-teagooddev Package
Summary
MAL-2025-108929: Malicious code in sorry_clam-teagooddev (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 'sorry_clam-teagooddev' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to facilitate the generation and publication of derivative packages, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the 'sorry_clam-teagooddev' package originates from its design to automatically publish derivative packages with randomized names. This malicious behavior includes modifying the package.json file to remove private flags, changing version numbers, and continuously republishing variants to pollute the npm registry. The ramifications of this vulnerability include potential security risks for developers who unknowingly use these compromised packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sorry_clam-teagooddevIf 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 avoid using the 'sorry_clam-teagooddev' package altogether. If you have dependencies that rely on it, consider finding alternative packages that do not have known vulnerabilities. Additionally, regularly audit your npm packages using npm audit to identify and address vulnerabilities.
Conclusion
The 'sorry_clam-teagooddev' package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package from their projects and to utilize tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for sorry_clam-teagooddev →
FAQ
The 'sorry_clam-teagooddev' package is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.
This vulnerability can compromise your project's security by introducing malicious code that alters package metadata and floods the npm registry.
You can use Vulert to monitor your application for vulnerabilities. Simply upload your package-lock.json file to receive real-time alerts about any open-source vulnerabilities.
You should immediately uninstall the 'sorry_clam-teagooddev' package and look for alternative packages. Regularly audit your dependencies to ensure security.
Yes, regularly auditing your dependencies, using tools like npm audit, and monitoring your packages with services like Vulert can help prevent vulnerabilities.
