Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

dbmuxnpm

Malicious code in dbmux (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5243
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dbmux

What this malware does

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.

The Miasma malware is a self-propagating worm that spreads across the npm registry by abusing weaponized binding.gyp files to achieve execution during package installation, bypassing security tools that only inspect package lifecycle scripts. Upon execution, the malware attempts to exfiltrate credentials and OIDC tokens for various cloud and registry services, and propagates by compromising other packages managed by the stolen accounts or committing backdoor files to GitHub repositories.

Malicious versions

2 flagged
1.0.52.2.5

Indicators of compromise (SHA-256)

a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb
ea0eb849e9fd2ed82d7be882c76fdbb2a43f4beab87823798027cf347048c9c6

Frequently asked questions

No. dbmux on npm has been identified as a malicious package (versions 1.0.5, 2.2.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-62wx-5f55-w8g2

References

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection
dbmux (npm) malicious package — MAL-2026-5243 | O3 Security