Malicious Code Injection in encouraging_cephalopod_0xrequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102085: Malicious code in encouraging_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 encouraging_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 manipulate npm's publishing system, often containing scripts that automatically generate and publish derivative packages. This behavior is aimed at inflating developer reputation scores for token rewards, making the package a target for malicious exploitation.

Vulnerability Detail

The vulnerability in the encouraging_cephalopod_0xrequest package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers who unknowingly use these packages. The malicious payload can compromise the integrity of the npm ecosystem and affect the reputation of legitimate developers.

How To Fix

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

npm uninstall encouraging_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 a temporary workaround, you can avoid using the encouraging_cephalopod_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The encouraging_cephalopod_0xrequest package poses significant security risks due to its malicious nature. It is crucial for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert. Staying informed and proactive in managing dependencies is essential to maintaining a secure development environment.

See every vulnerability recorded for encouraging_cephalopod_0xrequest →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign aimed at manipulating the npm registry for token rewards.

Using this package can lead to security risks, including the potential for your project to be associated with malicious activities and the pollution of the npm registry.

You should uninstall the package immediately and check for any dependencies that may rely on it.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

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