Which versions of orchestr8-platform are malicious?

The following PyPI versions of orchestr8-platform are flagged malicious: 3.3.2. Treat any of these as compromised.

How do I remediate orchestr8-platform if I installed it?

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

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

Yes — orchestr8-platform is associated with the 2026-06-compr-woodpecker, IN-MAL-2026-009481 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 orchestr8-platform 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 orchestr8-platform (version 3.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging orchestr8-platform across your stack and pipelines.

Malicious package

orchestr8-platformPyPI

Malicious code in orchestr8-platform (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5321

Immediate action

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

pip uninstall orchestr8-platform

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Versions 3.3.2 were compromised.

Compromised packages start an obfuscated infostealer. The infostealer is a heavily obfuscated JavaScript code executed using Bun runtime on Python startup. It collectes all kinds of sensitive data, including API keys, credentials to package repositories, cryptocurrency assets, password manager data. Infostealer actively queries online services to collect additional secrets as well as attempts to gain persistence and spread further by publishing infected packages using collected credentials. Data are exfiltrated likely using Github. The code seems to threaten to wipe the user's data if it detects invalid GitHub tokens. Cleanup should be done with caution.

It seems to be related to the recent Mini Shai Hulud campaign.

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

Campaign: 2026-06-compr-woodpecker

Reasons (based on the campaign):

compromised-package
exfiltration-env-variables
exfiltration-cloud-tokens
exfiltration-credentials
abuses-pth
obfuscation
infostealer
The package contains code to detect if it is running in a sandbox environment.
exfiltration-crypto
files-exfiltration
destructive-actions

Malicious versions

1 flagged

3.3.2

Indicators of compromise (SHA-256)

6b28e6bb345bcdb4726198079a56fcbbb0e73d4d2309c1927c0c8803d515232f

df4b5ee44ce01c21d9665d68c323b41889326ffd44e2df0136231ed501209390

6e7ec4481fb2bfb43db01c7bc318dc0fd26037fe86d1984d203bf3f0fa6ce043

7d9526ae43236ac15964b307175384455975ace26d8157ef3c41ed8db8192562

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

Campaign

2026-06-compr-woodpeckerIN-MAL-2026-009481

References

Credits

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

Detect & block this

O3 blocks orchestr8-platform-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