Which versions of executor-engine are malicious?

The following PyPI versions of executor-engine are flagged malicious: 0.3.4, 0.3.5. Treat any of these as compromised.

How do I remediate executor-engine if I installed it?

Remove executor-engine from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is executor-engine part of a known attack campaign?

Yes — executor-engine is associated with the 2026-06-compr-woodpecker campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect executor-engine in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking executor-engine and packages like it before any post-install script runs.

Malicious package

executor-enginePyPI

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

MAL-2026-5298

Immediate action

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

pip uninstall executor-engine

What this malware does

Versions 0.3.4, 0.3.5 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

2 flagged

0.3.40.3.5

Indicators of compromise (SHA-256)

445bbd05ea0ef3e22608235bea18f26fc18aaaff2066b5512c9752ba04a6ab13

b4e5edf3841a60f3a2ca53c80a29c679091db234b244009e2c759e5d429c9a00

baadb337b0bff76d8e98f724885e4768a33ea2e47b7c30e0d52615e09920c4b9

287577f98316d25963f2b25e9312f4bc2e1dc1e3cb34e83d69c6a2fc9cc3e7e6

Frequently asked questions

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

Campaign

2026-06-compr-woodpecker

References

Credits

Kamil Mańkowski (kam193) · reporter

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection