DependencyWatch.io
FeedSolutionsSubmitScan your lockfile
Criticalnpm4 affected versions

dbmux

dbmux has 4 versions on the npm registry flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with npm ls dbmux.

  • dbmux@2.2.5
  • dbmux@2.2.4
  • dbmux@1.0.6
  • dbmux@1.0.5

The incident that flagged it

Critical

dbmux maintainer-account takeover: four backdoored versions seeded across two release branches

Between 2026-06-04 and 2026-06-05 the dbmux npm maintainer account (bhagyamudgal) was hijacked and four backdoored releases were pushed across both the legacy 1.x and current 2.x branches: 1.0.5, 1.0.6, 2.2.4, 2.2.5. GHSA-62wx-5f55-w8g2 (published 2026-06-09) classifies all four as CWE-506 embedded malicious code: any host that installed or executed them should be treated as fully compromised. npm deprecated every malicious release; the clean latest is 2.2.3.

Versions named here: 1.0.5, 1.0.6, 2.2.4, 2.2.5

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

  1. 1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
  2. 2.Pin to a version not listed above, then reinstall from a clean lockfile.
  3. 3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
  4. 4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

dbmux is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once - it runs in your browser and nothing is uploaded.

Check my package-lock.json All flagged npm packages

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.