Malicious Code Vulnerability in firm_octopus_0xrequest Package

firm_octopus_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102739: Malicious code in firm_octopus_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The firm_octopus_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm registry, but it has been exploited to include malicious scripts that can compromise the integrity of the registry and the applications that depend on it.

Vulnerability Detail

This vulnerability originates from a malicious payload embedded within the firm_octopus_0xrequest package. It modifies the package.json file by removing private flags, altering version numbers, and generating random package names to inflate developer reputation scores. The malicious code continuously republishes these variants, leading to pollution of the npm registry and potential security risks for applications relying on this package.

How To Fix

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

npm uninstall firm_octopus_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 remove the firm_octopus_0xrequest package from your project by executing the command: npm uninstall firm_octopus_0xrequest. This will prevent the malicious code from executing until a secure version is available.

Conclusion

The firm_octopus_0xrequest package contains a serious vulnerability due to embedded malicious code that can compromise the integrity of applications using it. It is crucial to update or remove this package to ensure the security of your software. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for firm_octopus_0xrequest →

Share this vulnerability

FAQ

The firm_octopus_0xrequest package is an npm package associated with the tea.xyz token reward campaign, which has been found to contain malicious code.

The malicious code modifies your package.json file, removes private flags, and republishes variants, which can lead to security vulnerabilities and pollution of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application by using the Vulert playground at Vulert Scanner without any signup.

If an immediate update is not possible, consider uninstalling the package as a temporary workaround to mitigate the risk.

Detailed information about this vulnerability can be found in the vulnerability report provided by Amazon Inspector and on the npm registry.

How To Fix

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

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