Which versions of executor-http are malicious?

The following PyPI versions of executor-http are flagged malicious: 0.1.3, 0.1.4. Treat any of these as compromised.

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

Remove executor-http 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-http part of a known attack campaign?

Yes — executor-http 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-http 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-http and packages like it before any post-install script runs.

Malicious package

executor-httpPyPI

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

MAL-2026-5281

Immediate action

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

pip uninstall executor-http

What this malware does

Versions 0.1.3, 0.1.4 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.1.30.1.4

Indicators of compromise (SHA-256)

4396c593615517f1abf374bf3621ad44a9d0b5c540aaf8c8e101cd4954f7d7be

2f8706fa6e3490fd1604a5b98627ead50d01a949c03d7b1e69e3c45e63039f1c

fe7612103d2f4e8241cf1309b18f861afcd61541fbf822907f4d79cbbf5ca436

f9c1d1f9ab790bc8106fcfd74c547bcc4068a1b3f482dee948103e9db825c523

Frequently asked questions

No. executor-http on PyPI has been identified as a malicious package (versions 0.1.3, 0.1.4 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