Malicious Code Injection in statistical_clam_0xrequest Package

statistical_clam_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109087: Malicious code in statistical_clam_0xrequest (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The statistical_clam_0xrequest package is part of a broader ecosystem that has been exploited for malicious purposes, particularly in the context of the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm ecosystem but has been compromised to serve harmful scripts that manipulate package metadata and inflate developer reputation scores. The presence of such malicious packages poses a significant risk to developers and users relying on npm for secure and reliable packages.

Vulnerability Detail

The vulnerability in the statistical_clam_0xrequest package stems from its association with malicious scripts that are designed to autopublish derivative packages with randomized names. These scripts modify the package.json file by removing private flags, altering version numbers, and generating misleading package names. The continuous republishing of these variants leads to pollution of the npm registry, making it difficult for developers to identify legitimate packages. This vulnerability can result in security breaches, loss of trust in the npm ecosystem, and potential exploitation of applications relying on these packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall statistical_clam_0xrequest

If 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 statistical_clam_0xrequest package and replace it with a reputable alternative that provides similar functionality without the associated risks. Always verify the integrity of packages before installation.

Conclusion

The statistical_clam_0xrequest package presents a significant security risk due to its malicious code designed to manipulate npm package metadata. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining a secure software environment.

See every vulnerability recorded for statistical_clam_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been compromised to include malicious scripts aimed at manipulating package metadata for fraudulent purposes.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Using compromised packages can lead to security vulnerabilities, data breaches, and loss of trust in the software supply chain.

It is recommended to check for vulnerabilities regularly, ideally as part of your continuous integration and deployment processes.

Immediately remove the affected package, replace it with a secure alternative, and monitor for updates or patches from the package maintainers.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall statistical_clam_0xrequest

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback