monobing (npm) · Malicious Code
Affects monobingSource GCVE Database
Malicious package : remove monobing and rotate any secrets on hosts that installed it.
Data as of 4 Nov 2026, 17:16 UTC
Malicious package
Published to npm · OSV MAL-2025-49367
What to do
Remove monobing from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmmonobing | Affected– | Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (441b7951912d3fb98c9e3b96bbb2d93b7a99c024e860f3424d3f09befcb1c3c9) The package monobing was found to contain malicious code. ## Source: ghsa-malware (387a8c28d992f25a42764f6d247a0c1c0a70119f99f570f157549646628995e6) 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.