How do I remediate dhhdbank92015 if I installed it?

Remove dhhdbank92015 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 dhhdbank92015 — how do I know if it already compromised me?

If dhhdbank92015 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 dhhdbank92015 part of a known attack campaign?

Yes — dhhdbank92015 is associated with the RLMA-2025-05745 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 dhhdbank92015 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dhhdbank92015 (8 malicious versions).

Malicious package

dhhdbank92015npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

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

Malicious code in dhhdbank92015 (npm)

MAL-2025-48648

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dhhdbank92015

What this malware does

The package dhhdbank92015 was found to contain malicious code.

Malicious versions

8 flagged

1.250516.107541.250516.114021.250516.115451.250728.1132525.501.325.515.125.515.225.515.3

Indicators of compromise (SHA-256)

631a06e4d5164ff0733c30baadd55c3121b6abcc261f087cb08d38c70ad3db36

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhhdbank92015 (8 malicious versions).
If you installed it — respond
Remove dhhdbank92015 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 dhhdbank92015 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. dhhdbank92015 on npm has been identified as a malicious package (versions 1.250516.10754, 1.250516.11402, 1.250516.11545, 1.250728.11325, 25.501.3, 25.515.1, 25.515.2, 25.515.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05745

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks dhhdbank92015-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