Which versions of dhqr92004 are malicious?

The following npm versions of dhqr92004 are flagged malicious: 1.251014.11322, 1.251016.11353. Treat any of these as compromised.

How do I remediate dhqr92004 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhqr92004 (2 malicious versions).

Malicious package

dhqr92004npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhqr92004 is a confirmed malicious npm package (MAL-2025-48672) that executes malicious code on install (malicious versions 1.251014.11322, 1.251016.11353). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhqr92004 (npm)

MAL-2025-48672

Immediate action

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

npm uninstall dhqr92004

What this malware does

The package dhqr92004 was found to contain malicious code.

Malicious versions

2 flagged

1.251014.113221.251016.11353

Indicators of compromise (SHA-256)

7affdf245ddc56c7549538d746b0558d6db6ec93ead1f0514e5a6c4692f5ea50

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05764

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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