Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious code in h13t0ry-hello-demo (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 h13t0ry-hello-demo

    Affected
    >= 0.1.0, <= 0.1.0
    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 (34a52ed4e00f54dc99a4b460ad2d881b62a7a85c636085f4166f4062cebea374) On import, the package's top-level module code opens a TCP socket to the hardcoded IP 115.190.210.22:80, duplicates the socket over stdin/stdout/stderr via os.dup2, and spawns /bin/bash through pty.spawn, handing an interactive shell on the installer's host to the remote endpoint under the installing user's account. The module also exports a trivial one-line hello() function alongside the payload, and the package name uses leet-style substitution (h13t0ry) consistent with a cover story rather than a genuine demo package. The reverse-shell path is unauthenticated, undisclosed, and fires unconditionally on any `import hello_demo`.

Source: kam193 (e27409f6c0ba5c7e7ba22f21c8b4806686ae8b64f4d7daf2dd9a7e6182bef5ab) During import package starts a reverse shell --- Category: MALICIOUS - The campaign has clearly malicious intent, like…

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

    Amended from osv record MAL-2026-18336

  2. Revision 1 · created ·

    Published from osv record MAL-2026-18336

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

Advisory: Malicious code in h13t0ry-hello-demo (PyPI)
IDs: mal-2026-18336
Record: https://patchnext.com/advisories/mal-2026-18336 (revision 2, 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 h13t0ry-hello-demo: affected >= 0.1.0, <= 0.1.0

## Suggested inspection (read-only)
- `python -m pip show h13t0ry-hello-demo`: 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 h13t0ry-hello-demo.
- 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-18336 (OSV record MAL-2026-18336 lists affected ranges: PyPI h13t0ry-hello-demo >=0.1.0 <=0.1.0)

Commands are suggestions: review each one before running it.

Loading voting…