Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Malicious code in numbors (npm)

GHSA-682c-pwqm-7gxv

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

  • npm numbors

    Affected
    >= 1.6.1, <= 1.6.1
    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 (e9965eb6c2b7018707d2ca2ea1840355875eec43f0fc1efb9f03b45cf0566e1a) The numbors npm package publishes its entire shipped surface as heavily obfuscated JavaScript: every file under dist/ (the main entry dist/mcp.js, dist/config.js, dist/format.js, dist/command-catalog.js, dist/surface-parity.js, and ~90 command modules under dist/commands/) is minified with hex-identifier obfuscation (_0x variable names) rather than readable source. The package appears to be a CLI/MCP tool covering accounting, CRM, payroll, POS, and billing operations against a backend service. No concrete installer-harm fingerprint is visible from the shipped artifact — no lifecycle scripts fetching remote payloads, no identified credential-store reads, no hardcoded attacker C2, and no identified exfiltration path were observed — but the uniform obfuscation across every shipped file prevents semantic verification of what the CLI…

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

  2. Revision 1 · created ·

    Published from osv record MAL-2026-18322

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-682c-pwqm-7gxv

Advisory: Malicious code in numbors (npm)
IDs: GHSA-682c-pwqm-7gxv
Record: https://patchnext.com/advisories/mal-2026-18322 (revision 2, source checked 30 Oct 2026, 06:05 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
- npm numbors: affected >= 1.6.1, <= 1.6.1

## Suggested inspection (read-only)
- `npm ls numbors --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## 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 numbors.
- 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-18322 (OSV record MAL-2026-18322 lists affected ranges: npm numbors >=1.6.1 <=1.6.1)

Commands are suggestions: review each one before running it.

Loading voting…