GHSA-682c-pwqm-7gxv: Malicious code in numbors (npm)

Published Oct 26, 2026
·
Updated

--- -= 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<hex> 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 does when invoked, including how it handles any API tokens or financial data a user provides.

Source: ghsa-malware (287297439c9bdf199a88d43f3722ab361fde262c2ff3ee0f813fff21275211db) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Affected Software

1 affected component
npm/numbors=1.6.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove numbors (npm) from your environment.

    Remove the numbors npm package from any computer where it is installed or running.

  2. Operational

    Rotate all secrets and keys stored on the affected computer immediately, using a different computer.

Event History

Oct 26, 2026
Advisory Published
via GitHub·02:39 AM
Data Sourced
via GitHub·02:39 AM
DescriptionWeaknessAffected Software
Data Sourced
via OSV·02:39 AM
DescriptionAffected Software

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203