Malicious Code Injection in Successive Cephalopod 0xrequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109260: Malicious code in successive_cephalopod_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'successive_cephalopod_0xrequest' package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This functionality, while initially appearing benign, has been exploited to introduce malicious behavior.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the 'successive_cephalopod_0xrequest' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, contributing to the pollution of the npm registry. The malicious payload is part of a broader scheme to manipulate npm's reputation system and could lead to security risks for developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall successive_cephalopod_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 an immediate workaround, consider removing the 'successive_cephalopod_0xrequest' package from your project. You can do this by executing the command: 'npm uninstall successive_cephalopod_0xrequest'. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The 'successive_cephalopod_0xrequest' package contains malicious code that poses a significant risk to developers using it. It is crucial to take immediate action by updating or removing the package to safeguard your project from potential exploitation.

See every vulnerability recorded for successive_cephalopod_0xrequest →

Share this vulnerability

FAQ

It is an npm package that was part of a token reward campaign, designed to automate the creation and publication of derivative packages.

The malicious code can modify your package.json, remove private flags, and create random package names, potentially leading to security vulnerabilities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If updating is not possible, consider removing the package entirely and reviewing your dependencies for any other potential vulnerabilities.

Detailed information can be found in the vulnerability report on the official npm registry or through security advisories related to the package.

How To Fix

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

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