MAL-2026-18132Critical▾ Abyssal⚠ Exploited in the wildMalicious code in libseal (PyPI)
▾ Abyssal zone — Critical with a public exploit or in-the-wild use
impact 52.3 · likelihood 0 · exploitation 18
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
-= Per source details. Do not edit below this line.=-
Package libseal version 1.1.1 was scanned across 20 files with no a static rule matches and no traced behaviors indicating installer-side harm. No install-time network I/O, no lifecycle shell execution, no credential or environment scraping, no outbound exfiltration endpoints, no dropper or remote-fetch-and-execute pattern, and no persistence or backdoor code paths were observed.
In this campaign, one package (iterquarry) holds an encrypted payload, while another one (libseal) provides algorithms to decrypt and execute it. In earlier versions, the code used an embedded key and the payload was contacting a Discord bot. Starting with iterquarry 2.2.0, the key to the encrypted payload is not embedded and the payload remains unknown.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-10-iterquarry
Reasons (based on the campaign):
obfuscation
The malicious code is intentionally included in a dependency of the package
action-hidden-in-lib-usage
libsealRefer to the advisory for the patched release.