Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

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

    Affected
    >= 1.4.3, <= 1.4.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 (5428d0f2f07674817697574b1993211dfa902bad746d8cd6efc1ad6b1fbbfd90) nebulallm 1.4.3 presents itself as an AI API client stub but ships a custom install command class in setup.py that executes on `pip install`. The install hook spawns regsvr32.exe with the squiblydoo LOLBin pattern (`regsvr32 -s -i: scrobj.dll`) to fetch and execute a remote COM scriptlet from https://akinomoreno.pythonanywhere.com/faye on the installer's Windows host. The subprocess is launched with DETACHED_PROCESS and stdin/stdout/stderr redirected to DEVNULL, so the dropper runs silently and produces no output during pip install. The declared package functionality is unrelated to the install-time behavior, consistent with a dropper staged behind a cover-story package.

Source: kam193 (50e0ed125f08fd7743ccfb40590c24304b4731f6a99b69bc553b5bb8b7e57fc6) During installation package first downloads a JScript script, which then…

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

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

Advisory: Malicious code in nebulallm (PyPI)
IDs: mal-2026-18297
Record: https://patchnext.com/advisories/mal-2026-18297 (revision 1, source checked 26 Oct 2026, 12:45 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 nebulallm: affected >= 1.4.3, <= 1.4.3

## Suggested inspection (read-only)
- `python -m pip show nebulallm`: 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 nebulallm.
- 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-18297 (OSV record MAL-2026-18297 lists affected ranges: PyPI nebulallm >=1.4.3 <=1.4.3)

Commands are suggestions: review each one before running it.

Loading voting…