Malicious Code Injection in shallow_octopus_z3n Package

shallow_octopus_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90475: Malicious code in shallow_octopus_z3n (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The shallow_octopus_z3n package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate developer reputation scores for token rewards, making it a significant concern for developers relying on npm packages.

Vulnerability Detail

The vulnerability in the shallow_octopus_z3n package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This behavior can lead to security risks, including the potential for unauthorized access to sensitive data and the compromise of project integrity.

How To Fix

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

npm uninstall shallow_octopus_z3n

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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Additionally, consider using tools like Vulert to scan your project for vulnerabilities. You can check if your application is affected by visiting the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The shallow_octopus_z3n package poses a significant risk due to its malicious code that alters project files and repopulates the npm registry with harmful variants. It is essential for developers to take immediate action to remove this package and implement monitoring tools to safeguard their projects against similar vulnerabilities in the future.

See every vulnerability recorded for shallow_octopus_z3n →

Share this vulnerability

FAQ

shallow_octopus_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to unauthorized modifications in your project, potentially compromising its integrity and exposing sensitive data.

You should uninstall the shallow_octopus_z3n package immediately and monitor your project for any unusual behavior.

Yes, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories for the packages you use.

You can find detailed information about this vulnerability in the official npm advisory or by checking security databases like Vulert.

How To Fix

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

npm uninstall shallow_octopus_z3n

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