Malicious Code Injection in strict_clam_0xrequest Package - npm Vulnerability
Summary
MAL-2025-109187: Malicious code in strict_clam_0xrequest (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 strict_clam_0xrequest 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 function 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 strict_clam_0xrequest originates from its association with a malicious campaign that aims to inflate developer reputation scores for token rewards. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall strict_clam_0xrequestIf 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 strict_clam_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to regularly check for vulnerabilities in your dependencies.
Conclusion
The strict_clam_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your project and monitor your dependencies for similar vulnerabilities to maintain the integrity and security of your applications.
See every vulnerability recorded for strict_clam_0xrequest →
FAQ
It is an npm package that has been compromised to include malicious code aimed at manipulating package metadata and inflating developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of other packages, potentially introducing security risks into your project.
You should uninstall the strict_clam_0xrequest package immediately and check for any other affected packages in your project.
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 against known vulnerabilities using the Vulert playground.
Regularly audit your dependencies using tools like npm audit and consider using automated monitoring services like Vulert to stay informed about vulnerabilities.
