Malicious Code Injection in Causal Scallop 0xRequest Package

causal_scallop_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100288: Malicious code in causal_scallop_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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'causal_scallop_0xrequest' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate automated publishing of derivative packages, which can inflate developer reputation scores for token rewards. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to pollution of the npm registry and can potentially harm developers by inflating reputation scores artificially, making it difficult to identify legitimate packages.

How To Fix

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

npm uninstall causal_scallop_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 'causal_scallop_0xrequest' package and replace it with a trusted alternative. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The 'causal_scallop_0xrequest' package is compromised by malicious code that alters its behavior and metadata. It is crucial to remove this package from your project and monitor for any updates. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.

See every vulnerability recorded for causal_scallop_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.

The vulnerability can lead to the pollution of the npm registry, making it difficult to identify legitimate packages and potentially harming your project's integrity.

You should remove the 'causal_scallop_0xrequest' package from your project and monitor for any updates or patches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can also check your application against vulnerabilities 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.

How To Fix

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

npm uninstall causal_scallop_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