Malicious Code Injection in tremendous_octopus-tool: A Critical npm Vulnerability

tremendous_octopus-tool Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109824: Malicious code in tremendous_octopus-tool (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 tremendous_octopus-tool is an npm package that appears to be part of a broader malicious campaign targeting developers through the tea.xyz token reward system. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the tremendous_octopus-tool package. This payload modifies the package.json file by removing private flags, altering version numbers, and creating random package names. The scripts (auto.js, autopublish.js, etc.) continuously republish these variants, leading to pollution of the npm registry and potential exploitation of developers who unknowingly use these packages. The ramifications include compromised package integrity, loss of developer reputation, and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall tremendous_octopus-tool

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 tremendous_octopus-tool package from your project by executing the command: npm uninstall tremendous_octopus-tool. This will help prevent any malicious code from executing until a patch is available.

Conclusion

The tremendous_octopus-tool package is compromised by malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can enhance your ability to monitor and respond to vulnerabilities effectively.

See every vulnerability recorded for tremendous_octopus-tool →

Share this vulnerability

FAQ

The tremendous_octopus-tool is an npm package involved in a malicious campaign that manipulates the npm registry for token rewards.

The vulnerability can lead to the injection of malicious code into your application, compromising its integrity and security.

If you have installed the tremendous_octopus-tool package, you should uninstall it immediately and monitor for any updates or patches.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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

How To Fix

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

npm uninstall tremendous_octopus-tool

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