Which versions of octopus32 are malicious?

The following PyPI versions of octopus32 are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate octopus32 if I installed it?

octopus32 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed octopus32 — how do I know if it already compromised me?

If octopus32 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is octopus32 part of a known attack campaign?

Yes — octopus32 is associated with the RLMA-2025-03019, 2025-05-octopus32, RLUA-2026-00567 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find octopus32 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for octopus32 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging octopus32 across your stack and pipelines.

Malicious package

octopus32PyPI

Malicious code in octopus32 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-5122

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall octopus32

What this malware does

The obfuscated code downloads and starts a remote executable. The remote file has limited detection in VT, but contains at least code to add Defender exclusion paths.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-05-octopus32

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

af892547bb44db0db1c2f36d380f9ed5e5bee3186ae5653cdd57a96cec1d3e15

9bf3c65a50bb5637482dc1208f78981469231e937d80cd001b107631773b83d8

15fe4c8243ee2e3d9bb59df9134466819fdcb2e151cc4d79568dc4eb2dea9ac9

f41ad619fe0ac436fbed48ada79e2542cfc50f0b7f87adce88dd9dd03542ed6e

6acc58b795f3887a16933c00a5414ebac8b3d29e309135a2eebdaccc8a015a9e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for octopus32 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging octopus32 across your stack and pipelines.
If you installed it — respond
octopus32 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If octopus32 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks octopus32 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. octopus32 on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-030192025-05-octopus32RLUA-2026-00567

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks octopus32-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring