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

@su-doughnym/react-dlbnpm

Malicious code in @su-doughnym/react-dlb (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6410
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @su-doughnym/react-dlb

What this malware does

Package self-identifies as a dependency-confusion bug-bounty proof-of-concept and is published at version 99.99.99 to win resolution priority over an internal package of the same name. The shipped postinstall script (postinstall.js lines 11-13) only reads os.hostname(), os.userInfo().username, process.version, and process.pid and prints them to stdout — no network call, no file write, no credential read, no remote fetch. The current tarball therefore does not exfiltrate or execute attacker-controlled bytes on the installer. The risk is that any organization whose internal package resolution accidentally pulls @su-doughnym/react-dlb instead of an internal package of the same name will execute this author's lifecycle scripts, and a future version under the same name+scope could replace the harmless beacon with a weaponized payload.

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.

Malicious versions

1 flagged
99.99.99

Indicators of compromise (SHA-256)

3c4b5ea9035f910a7193b9da02623e92d8364869382bf683b3469ea3a2b46fdc
2269beae8c30caccda966ca3aba35c3eddb4795fba0161045f14758ff150f58b

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @su-doughnym/react-dlb (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @su-doughnym/react-dlb across your stack and pipelines.

  2. If you installed it — respond

    @su-doughnym/react-dlb is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @su-doughnym/react-dlb was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @su-doughnym/react-dlb before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @su-doughnym/react-dlb on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3g2q-cw4h-3g67IN-MAL-2026-008111

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @su-doughnym/react-dlb-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.