How do I remediate dhqr92010 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhqr92010 (10 malicious versions).

Malicious package

dhqr92010npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhqr92010 is a confirmed malicious npm package (MAL-2025-48673) that executes malicious code on install (malicious versions 1.251012.11645, 1.251012.11715, 1.251012.11737…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhqr92010 (npm)

MAL-2025-48673

Immediate action

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

npm uninstall dhqr92010

What this malware does

The package dhqr92010 was found to contain malicious code.

Malicious versions

10 flagged

1.251012.116451.251012.117151.251012.117371.251012.117401.251013.113551.251013.114131.251015.110511.251015.111061.251015.111321.251016.11353

Indicators of compromise (SHA-256)

92730eabf048376e6ea339022db015d35044833f65aef75983d4824b08de0157

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhqr92010 (10 malicious versions).
If you installed it — respond
Remove dhqr92010 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 dhqr92010 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. dhqr92010 on npm has been identified as a malicious package (versions 1.251012.11645, 1.251012.11715, 1.251012.11737, 1.251012.11740, 1.251013.11355, 1.251013.11413, 1.251015.11051, 1.251015.11106, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05765

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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