{"items":[{"id":"NVI-00008451","kind":"supply_chain_event","title":"Malicious code in libseal (PyPI)","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-8pwv-jgmv-fcm8"],"plain_summary":"GitHub lists this malware advisory for libseal, libseal, libseal, libseal. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-34f0a10fc7c8e3b7b46a47e7631559a6"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-34f0a10fc7c8e3b7b46a47e7631559a6","url":"https://github.com/advisories/GHSA-8pwv-jgmv-fcm8","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-8pwv-jgmv-fcm8","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T21:56:27.401Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-34f0a10fc7c8e3b7b46a47e7631559a6"],"technology":"libseal","known_exclusions":[],"conditions_summary":"## Source: kam193 (7e6d706d49a7fce89545d12c5bd5a0cab0a4919a95ff89150b28cb838967bb09)\nIn 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.\n\n\n---\n\nCategory: MALICIOUS - The campaign has clearly malicious intent, like infostealers.\n\n\nCampaign: 2026-10-iterquarry\n\n\nReasons (based on the campaign):\n\n\n - obfuscation\n\n\n - The malicious code is intentionally included in a dependency of the package\n\n\n - action-hidden-in-lib-usage\n\n---\n\nCredit: OpenSSF (source)","public_affected_ranges":["= 1.1.0"]},{"certainty":"source_listed","source_ids":["sr-34f0a10fc7c8e3b7b46a47e7631559a6"],"technology":"libseal","known_exclusions":[],"conditions_summary":"## Source: kam193 (7e6d706d49a7fce89545d12c5bd5a0cab0a4919a95ff89150b28cb838967bb09)\nIn 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.\n\n\n---\n\nCategory: MALICIOUS - The campaign has clearly malicious intent, like infostealers.\n\n\nCampaign: 2026-10-iterquarry\n\n\nReasons (based on the campaign):\n\n\n - obfuscation\n\n\n - The malicious code is intentionally included in a dependency of the package\n\n\n - action-hidden-in-lib-usage\n\n---\n\nCredit: OpenSSF (source)","public_affected_ranges":["= 1.1.1"]},{"certainty":"source_listed","source_ids":["sr-34f0a10fc7c8e3b7b46a47e7631559a6"],"technology":"libseal","known_exclusions":[],"conditions_summary":"## Source: kam193 (7e6d706d49a7fce89545d12c5bd5a0cab0a4919a95ff89150b28cb838967bb09)\nIn 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.\n\n\n---\n\nCategory: MALICIOUS - The campaign has clearly malicious intent, like infostealers.\n\n\nCampaign: 2026-10-iterquarry\n\n\nReasons (based on the campaign):\n\n\n - obfuscation\n\n\n - The malicious code is intentionally included in a dependency of the package\n\n\n - action-hidden-in-lib-usage\n\n---\n\nCredit: OpenSSF (source)","public_affected_ranges":["= 1.1.2"]},{"certainty":"source_listed","source_ids":["sr-34f0a10fc7c8e3b7b46a47e7631559a6"],"technology":"libseal","known_exclusions":[],"conditions_summary":"## Source: kam193 (7e6d706d49a7fce89545d12c5bd5a0cab0a4919a95ff89150b28cb838967bb09)\nIn 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.\n\n\n---\n\nCategory: MALICIOUS - The campaign has clearly malicious intent, like infostealers.\n\n\nCampaign: 2026-10-iterquarry\n\n\nReasons (based on the campaign):\n\n\n - obfuscation\n\n\n - The malicious code is intentionally included in a dependency of the package\n\n\n - action-hidden-in-lib-usage\n\n---\n\nCredit: OpenSSF (source)","public_affected_ranges":["= 1.1.3"]}],"null_published_at":"2026-10-31T22:13:22.847Z","source_updated_at":"2026-10-29T15:31:36.000Z","source_disclosed_at":"2026-10-22T00:32:03.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:56:27.401Z"}],"next_cursor":null,"snapshot_revision":"42594"}