How do I remediate dhhdbank92013 if I installed it?

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.

I already installed dhhdbank92013 — how do I know if it already compromised me?

If dhhdbank92013 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is dhhdbank92013 part of a known attack campaign?

Yes — dhhdbank92013 is associated with the RLMA-2025-05744 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dhhdbank92013 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dhhdbank92013 (7 malicious versions).

Malicious package

dhhdbank92013npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

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

Find it
Search your lockfiles and build artifacts for dhhdbank92013 (7 malicious versions).
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.
Did it already run?
If dhhdbank92013 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

getsafety.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database