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

dhhdbank92013npm

dhhdbank92013 is a confirmed malicious npm package (MAL-2025-48647) that executes malicious code on install (malicious versions 1.250516.10754, 1.250516.10917, 1.250516.11333…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhhdbank92013 (npm)

MAL-2025-48647
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall dhhdbank92013

What this malware does

The package dhhdbank92013 was found to contain malicious code.

Malicious versions

7 flagged
1.250516.107541.250516.109171.250516.113331.250516.115451.250722.1104025.515.125.515.2

Indicators of compromise (SHA-256)

f4223a5bfde2afa72c610fab47f882bb54f5f77ed3f2dd102924ff810c854732

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove dhhdbank92013 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If dhhdbank92013 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 dhhdbank92013 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. dhhdbank92013 on npm has been identified as a malicious package (versions 1.250516.10754, 1.250516.10917, 1.250516.11333, 1.250516.11545, 1.250722.11040, 25.515.1, 25.515.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05744

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks dhhdbank92013-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

dhhdbank92013 (npm) malicious package — MAL-2025-48647 | O3 Security