numbors
Affected
- Versions:
1.6.1
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-682c-pwqm-7gxv
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in numbors (npm)
---
_-= 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.
Not rated by the source.
1.6.1None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0