Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

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

    Affected
    >= 0.0.1, <= 0.0.1>= 0.0.2, <= 0.0.2
    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 (2ccf3f03f309715ca11fb3863aa89a57d4c0550606cb17839bfff9b5dfd34687) The package installs stdid_nyxprobe.pth into site-packages, whose sole content is `import stdid_nyxprobe._beacon`. Python's site.py mechanism evaluates this on every interpreter start after `pip install`, with no user-initiated import required. The imported module stdid_nyxprobe/_beacon.py collects host identifiers — hostname (socket.gethostname), LAN IP (via `hostname -I`), username (getpass.getuser), current working directory, and Python version — and POSTs them to https://api.telegram.org/bot /sendMessage using a hardcoded bot token (8984095380:AAHN...) and two hardcoded chat IDs (1841775463, -5380294525). A sentinel file at ~/.cache/.stdid_beacon_fired is written to suppress repeat beacons. The package has no documented legitimate functionality that would justify this behavior; the.pth auto-exec primitive is being used purely…

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

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

Advisory: Malicious code in stdid-nyxprobe (PyPI)
IDs: mal-2026-18406
Record: https://patchnext.com/advisories/mal-2026-18406 (revision 1, source checked 31 Oct 2026, 06:15 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 stdid-nyxprobe: affected >= 0.0.1, <= 0.0.1; >= 0.0.2, <= 0.0.2

## Suggested inspection (read-only)
- `python -m pip show stdid-nyxprobe`: 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 stdid-nyxprobe.
- 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-18406 (OSV record MAL-2026-18406 lists affected ranges: PyPI stdid-nyxprobe >=0.0.1 =0.0.2 <=0.0.2)

Commands are suggestions: review each one before running it.

Loading voting…