Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

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

    Affected
    >= 1.1.0, <= 1.1.0>= 1.1.1, <= 1.1.1>= 1.1.2, <= 1.1.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 (3818fe7f3387637c23d6bc51d62f8fd64dc981c82167750cd3059eec73d2849c) netweavex is a typosquat of the popular NetworkX library, reusing its public API, module layout, and README examples (including the `import netweavex as nx` idiom) under a lookalike name. On `import netweavex`, the top-level init.py loads netweavex.netweavex, whose module scope invokes exec() on a payload produced by reversing a string literal, base64-decoding it, and zlib-decompressing it (the decoded header is a valid zlib stream, `x\xda...`). This causes attacker-controlled, opaque bytecode to run on the installer's host at import time. A graph library has no legitimate reason to layer reverse+base64+zlib obfuscation around an exec() sink; the combination of lookalike name, API cloning, and import-time execution of hidden code is the canonical PyPI typosquat dropper shape.

Source: kam193…

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

    Amended from osv record MAL-2026-18328

  2. Revision 2 · amended ·

    Amended from osv record MAL-2026-18328

  3. Revision 1 · created ·

    Published from osv record MAL-2026-18328

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

Advisory: Malicious code in netweavex (PyPI)
IDs: mal-2026-18328
Record: https://patchnext.com/advisories/mal-2026-18328 (revision 3, 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 netweavex: affected >= 1.1.0, <= 1.1.0; >= 1.1.1, <= 1.1.1; >= 1.1.2, <= 1.1.2

## Suggested inspection (read-only)
- `python -m pip show netweavex`: 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 netweavex.
- 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-18328 (OSV record MAL-2026-18328 lists affected ranges: PyPI netweavex >=1.1.0 =1.1.1 =1.1.2 <=1.1.2)

Commands are suggestions: review each one before running it.

Loading voting…