Which versions of dhhdbank87015 are malicious?

The following npm versions of dhhdbank87015 are flagged malicious: 1.250708.10934, 1.250708.10938, 1.250708.11022, 1.250708.11025, 1.250708.11038. Treat any of these as compromised.

How do I remediate dhhdbank87015 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhhdbank87015 (5 malicious versions).

Malicious package

dhhdbank87015npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhhdbank87015 is a confirmed malicious npm package (MAL-2025-48646) that executes malicious code on install (malicious versions 1.250708.10934, 1.250708.10938, 1.250708.11022…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhhdbank87015 (npm)

MAL-2025-48646

Immediate action

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

npm uninstall dhhdbank87015

What this malware does

The package dhhdbank87015 was found to contain malicious code.

Malicious versions

5 flagged

1.250708.109341.250708.109381.250708.110221.250708.110251.250708.11038

Indicators of compromise (SHA-256)

130862291ce055606faaa05c9171a136778158aa8d1a787318458b9eb95b986c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhhdbank87015 (5 malicious versions).
If you installed it — respond
Remove dhhdbank87015 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 dhhdbank87015 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. dhhdbank87015 on npm has been identified as a malicious package (versions 1.250708.10934, 1.250708.10938, 1.250708.11022, 1.250708.11025, 1.250708.11038 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05743

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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