If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
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):
- obfuscation
- The malicious code is intentionally included in a dependency of the package
- action-hidden-in-lib-usage