Vulnerability
Malicious code in executor-http (PyPI)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (cde4da7201fbc0dd3ae09240232f5767c2893e33977d6c8ee9071d15e79f0363) The package ships `executor_http-setup.pth`, which Python auto-loads at interpreter start for any environment where the package is installed. The.pth file calls `exec()` on an obfuscated single-line string (mangled one-letter underscore identifiers like `_O`, `_T`, `_G`, `_u`, `_s`, `_b`, `_z`) that downloads `https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/bun-{platform}-{arch}.zip` to `/tmp/b/bun`, chmods it executable, then runs `subprocess.run([bun, 'run', _index.js])` to execute a sibling JavaScript file under the Bun runtime. A `/tmp/.bun_ran` sentinel suppresses re-execution. The advertised purpose of executor-http is a FastAPI/uvicorn HTTP server for executor-engine — there is no legitimate reason for it to fetch a JavaScript runtime and execute JS code outside of Python's view. The legitimate FastAPI source under `executor/http/` appears unmodified, and the distribution metadata is inconsistent (`__init__.py` reports 0.1.2, METADATA says 0.1.3, RECORD references `executor_http-0.1.2.dist-info`), consistent with a hijacked publish-credential adding a dropper to an otherwise normal upstream release. The.pth-based auto-execution mechanism is itself an evasion technique that bypasses review of `__init__.py` and lifecycle hooks, and the alternate-runtime stage (Bun executing `_index.js`) places the actual payload outside any Python static analysis surface. ## Source: kam193 (4396c593615517f1abf374bf3621ad44a9d0b5c540aaf8c8e101cd4954f7d7be) 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
No CVSS base score from NVD or GHSA yet. NVD typically scores within 24–72 hours of publication; GHSA usually within a day for OSS-flagged CVEs. Last record update .
For interim severity, fall back on KEV / EXPLOIT signals and the EPSS percentile (lower panel). Re-check this CVE after one cron tick — the score lands automatically when the source publishes.
FIRST.org publishes EPSS daily. Coverage isn't universal — pre-disclosure CVEs and reserved IDs don't carry an EPSS score until at least one exploitation signal lands. Score will appear within 24 hours of the next EPSS pull.
No exploitation, limited impact or prevalence