Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

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

    Affected
    >= 1.2.1, <= 1.2.1>= 1.2.2, <= 1.2.2>= 1.2.3, <= 1.2.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 (8fdb099f519e4b3349d3800684dd052bd2eef6149061f36587fe69ffab780397) Package sysdiagd version 1.2.2 on PyPI was examined across 15 files. No a static rule matches were produced and no concrete behavioral findings are available from the traced code review. The package name suggests a system diagnostics daemon, but no specific file, function, network destination, credential read, or install-time execution path has been corroborated with evidence in this record. Without a named installer-side data read tied to a specific destination, a named install-time or import-time execution path, or any other concrete fingerprint, the behavior of this version cannot be characterized as benign or malicious from the available signals alone.

Source: kam193 (0d396ad34176d29956d695014d261847ada859c184d7a8e7820d96087af7eafe) Disguised as a system monitoring tool, the package delivers a Discord bot acting as an…

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

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

Advisory: Malicious code in sysdiagd (PyPI)
IDs: mal-2026-17861
Record: https://patchnext.com/advisories/mal-2026-17861 (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 sysdiagd: affected >= 1.2.1, <= 1.2.1; >= 1.2.2, <= 1.2.2; >= 1.2.3, <= 1.2.3

## Suggested inspection (read-only)
- `python -m pip show sysdiagd`: 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 sysdiagd.
- 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-17861 (OSV record MAL-2026-17861 lists affected ranges: PyPI sysdiagd >=1.2.1 =1.2.2 =1.2.3 <=1.2.3)

Commands are suggestions: review each one before running it.

Loading voting…