Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in libseal (PyPI)

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI libseal

    Affected
    >= 1.1.0, <= 1.1.0>= 1.1.1, <= 1.1.1>= 1.1.2, <= 1.1.2>= 1.1.3, <= 1.1.3
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

--- _-= 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:…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record MAL-2026-18132

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: mal-2026-18132

Advisory: Malicious code in libseal (PyPI)
IDs: mal-2026-18132
Record: https://patchnext.com/advisories/mal-2026-18132 (revision 1, source checked 30 Oct 2026, 06:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI libseal: affected >= 1.1.0, <= 1.1.0; >= 1.1.1, <= 1.1.1; >= 1.1.2, <= 1.1.2; >= 1.1.3, <= 1.1.3

## Suggested inspection (read-only)
- `python -m pip show libseal`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on libseal.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-18132 (OSV record MAL-2026-18132 lists affected ranges: PyPI libseal >=1.1.0 =1.1.1 =1.1.2 =1.1.3 <=1.1.3)

Commands are suggestions: review each one before running it.

Loading voting…