Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in ps-bool (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 ps-bool

    Affected
    >= 0.2.0, <= 0.2.0>= 0.2.1, <= 0.2.1>= 0.2.3, <= 0.2.3>= 0.2.4, <= 0.2.4>= 0.2.5, <= 0.2.5
    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 (5dcafa44d321e5c6169bbdd949fa1d421e5039bc53d017c00d3e5411f33db5ec) The sole module shipped in both the sdist and the wheel, main.py, consists entirely of `exec(zlib.decompress(base64.b85decode('...')))` at the top level. The package exposes this module as `py_modules=['main']` and wires it as the `psbool` console_script, so the opaque, compressed-and-encoded blob is decoded and executed unconditionally the first time the module is imported or the CLI is invoked. There is no source, documentation, or API surface — the entire implementation is a single encoded payload, deliberately concealing its behavior from anyone inspecting the package before it runs. A boolean-logic utility has no legitimate reason to ship its implementation as an opaque exec-of-decoded-bytes blob; this is the canonical obfuscated-payload import-time execution shape and causes an arbitrary author-controlled program to run on…

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

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

Advisory: Malicious code in ps-bool (PyPI)
IDs: mal-2026-19934
Record: https://patchnext.com/advisories/mal-2026-19934 (revision 1, source checked 15 Nov 2026, 06:55 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 ps-bool: affected >= 0.2.0, <= 0.2.0; >= 0.2.1, <= 0.2.1; >= 0.2.3, <= 0.2.3; >= 0.2.4, <= 0.2.4; >= 0.2.5, <= 0.2.5

## Suggested inspection (read-only)
- `python -m pip show ps-bool`: 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 ps-bool.
- 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-19934 (OSV record MAL-2026-19934 lists affected ranges: PyPI ps-bool >=0.2.0 =0.2.1 =0.2.3 =0.2.4 =0.2.5 <=0.2.5)

Commands are suggestions: review each one before running it.

Loading voting…