libseal
Affected
- Versions:
1.1.0,1.1.1,1.1.2,1.1.3
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in libseal (PyPI)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (50e8ebbbca9850ab1485e13a15b5425b0c7c823adaaf480881ae7223ffdc254f)
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.
Source: kam193 (7e6d706d49a7fce89545d12c5bd5a0cab0a4919a95ff89150b28cb838967bb09)
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):
Not rated by the source.
1.1.0, 1.1.1, 1.1.2, 1.1.3None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0