Malicious code in dbmux (npm)

---

__

Source: amazon-inspector (7843aa1ed1418bd452c243441bbe146ed7e023c5a1ad92b522d2429020ea94cd)

No evidence of installer-harming behavior was identified in dbmux@1.0.6. No lifecycle scripts performing remote fetch-and-execute, no credential or environment-variable scraping, no hardcoded attacker-controlled network destinations, and no silent-relay or backdoor mechanisms were observed.

Source: ghsa-malware (ea0eb849e9fd2ed82d7be882c76fdbb2a43f4beab87823798027cf347048c9c6)

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.

Source: google-open-source-security (a6c7977dbc054cdb7fe56da0d2fbd26e2a6fed695deb4263ccbf4adfedd86acb)

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.