---
id: "MAL-2026-18132"
kind: "package"
aliases: ["MAL-2026-18132"]
title: "Malicious code in libseal (PyPI)"
severity: "critical"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "libseal", "fixed": [], "affected": "= 1.1.0; = 1.1.1; = 1.1.2; = 1.1.3", "ecosystem": "pypi"}]
ecosystems: ["pypi"]
tags: ["malicious", "package"]
not_affected_if: []
published_at: "2026-10-21T22:02:05+00:00"
first_seen_at: "2026-10-26T20:52:00+00:00"
updated_at: "2026-10-26T21:05:48+00:00"
sources: [{"source": "osv-malicious", "url": "https://osv.dev/vulnerability/MAL-2026-18132", "first_seen_at": "2026-10-26T20:52:00+00:00"}]
---

# Malicious code in libseal (PyPI)

## Affected

- pypi:libseal affected = 1.1.0; = 1.1.1; = 1.1.2; = 1.1.3 fixed ?

## Timeline

- 2026-10-26T20:52:00+00:00 osv-malicious https://osv.dev/vulnerability/MAL-2026-18132

## From the sources

---
_-= Per source details. Do not edit below this line.=-_

## 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

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_