Which versions of optimux are malicious?

The following PyPI versions of optimux are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate optimux if I installed it?

optimux 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 optimux — how do I know if it already compromised me?

If optimux 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 optimux part of a known attack campaign?

Yes — optimux is associated with the RLMA-2024-11105, GENERIC-standard-pypi-install-pentest, RLUA-2026-00570 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 optimux 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 optimux (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging optimux across your stack and pipelines.

Malicious package

optimuxPyPI

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

MAL-2024-11649

Immediate action

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

pip uninstall optimux

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

114d3daf0116838ac3f7cb6226b9a614d566ef6b2cdb79edc7778b9ee923eaf0

26fa0d105b8fea3ab3553ad6976c66e9186f4ad1e72270eadb4274525f66bf74

b2737cac48f109d99f0b6b2ea3f5bbab193dd15390bf35808162bd8a6abfa163

e4946b724ebee0d3710788df6110c10c5b973af67ea4f08bfabbef435aa77074

a5e8e8d05466005e52d72e4297ea55ae60a2d59eebf1cef560ce0abf755cc249

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 optimux (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging optimux across your stack and pipelines.
If you installed it — respond
optimux 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 optimux 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 optimux 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. optimux on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-11105GENERIC-standard-pypi-install-pentestRLUA-2026-00570

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks optimux-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