Which versions of scrambleeer are malicious?

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

How do I remediate scrambleeer if I installed it?

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

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

Yes — scrambleeer is associated with the 2026-08-scrambleeer, IN-MAL-2026-018504, IN-MAL-2026-018521 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 scrambleeer 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 scrambleeer (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging scrambleeer across your stack and pipelines.

Malicious package

scrambleeerPyPI

scrambleeer is a confirmed malicious PyPI package (MAL-2026-14350) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in scrambleeer (PyPI)

MAL-2026-14350

Immediate action

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

pip uninstall scrambleeer

What this malware does

The package advertises a numeric shuffle utility but its sole public function scrambleeer() opens a TCP socket to bax.h4x.tv on port 6363, dup2's the socket over stdin/stdout/stderr, and spawns /bin/bash via pty. Invoking the documented API therefore hands an interactive shell on the caller's host to the operator of bax.h4x.tv. The payload is compressed onto a single semicolon-separated line inside an otherwise innocuous shuffle routine, concealing the backdoor from casual review.

When using the provided library, the code starts a reverse shell to a hardcoded location.

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

Campaign: 2026-08-scrambleeer

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
action-hidden-in-lib-usage

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

52d5b1e99e57b038247cf3b7f86a7514e75275a095ca3f3cf044d80cbe999472

7eb0e96b324df04d5ecaf0739dec60dcb2367a26def0e713519c51e24ee790df

93a5fb5bdaf11c095ec283223e6ca464e5c43afa6e4b1224c72e96f8f85a2f7d

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 scrambleeer (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging scrambleeer across your stack and pipelines.
If you installed it — respond
scrambleeer 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 scrambleeer 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 scrambleeer 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. scrambleeer 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

2026-08-scrambleeerIN-MAL-2026-018504IN-MAL-2026-018521

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database