Vulnerability
Malicious code in funcdesc (PyPI)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4a5756a79331cdda67721e39889609f5c0b5e342b678dbce2de97c94ec2dbe29) The package installs `funcdesc-setup.pth`, which Python auto-executes at interpreter startup for any environment where this package is installed. The.pth file is obfuscated with single-letter aliases (`_O`, `_T`, `_G`, `_o`, `_s`, `_u`,...) and wraps its real payload in `exec()` over an inline string, gated by a `/tmp/.bun_ran` sentinel. On first run it calls `urllib.request.urlretrieve` to download the Bun JavaScript runtime release archive from `https://github.com/oven-sh/bun/releases/download/bun-v1.3.13/bun-<platform>-<arch>.zip`, extracts it to `/tmp/b/bun`, chmods it executable, and then invokes `bun run _index.js` against a bundled `_index.js` shipped inside the package. The advertised purpose of funcdesc is a Python function-description protocol; there is no legitimate reason for it to fetch and run an alternate JavaScript runtime, stage binaries in `/tmp`, or execute opaque bundled JS outside the documented Python API. The pattern (auto-loaded.pth, obfuscated exec, alternate-runtime dropper, mismatched purpose, in-file `__version__` still reading `0.2.1`) is consistent with a hijacked release rather than legitimate maintainer behavior. The harm fires automatically every time a Python interpreter starts in any environment where this version is installed, not only at `pip install`, giving the attacker arbitrary code execution on the installer's machine. ## Source: kam193 (c6f85c691f141dc4c962171ac49945286bb40e15cb8450d2f42d048a3f53bb22) Versions 0.2.2, 0.2.3 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