dbmux (npm) · Malicious Code
Affects dbmuxSource GCVE Database
Malicious package : remove dbmux and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 15:56 UTC
Malicious package
Published to npm · OSV MAL-2026-5243
What to do
Remove dbmux 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 |
|---|---|---|
| npmdbmux | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The dbmux npm package versions 1.0.5 and 2.2.5 contain malicious code known as the Miasma malware. This malware propagates by abusing binding.gyp files during package installation, evading detection by security tools that only inspect lifecycle scripts. It attempts to exfiltrate credentials and OIDC tokens for cloud and registry services, potentially compromising the host system and spreading to other packages and repositories. Systems with this package installed should be considered fully compromised.
References
- endorlabs.com/learn/malicious-payload-in-ai-sdk-ollama-npm-package (opens in a new tab)
- stepsecurity.io/blog/binding-gyp-npm-supply-chain-attack-spreads-like-worm (opens in a new tab)
- github.com/advisories/GHSA-62wx-5f55-w8g2 (opens in a new tab)
- npmjs.com/package/dbmux/v/2.2.5 (opens in a new tab)
- npmjs.com/package/dbmux/v/1.0.5 (opens in a new tab)
- npmjs.com/package/dbmux/v/1.0.6 (opens in a new tab)