Which versions of ldhpgemrdhs92004 are malicious?

The following npm versions of ldhpgemrdhs92004 are flagged malicious: 1.250916.10837, 1.250923.10905, 1.250923.11036, 1.250926.11417. Treat any of these as compromised.

How do I remediate ldhpgemrdhs92004 if I installed it?

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

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

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

Search your lockfiles and build artifacts for ldhpgemrdhs92004 (4 malicious versions).

Malicious package

ldhpgemrdhs92004npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhpgemrdhs92004 is a confirmed malicious npm package (MAL-2025-48724) that executes malicious code on install (malicious versions 1.250916.10837, 1.250923.10905, 1.250923.11036…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhpgemrdhs92004 (npm)

MAL-2025-48724

Immediate action

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

npm uninstall ldhpgemrdhs92004

What this malware does

The package ldhpgemrdhs92004 was found to contain malicious code.

Malicious versions

4 flagged

1.250916.108371.250923.109051.250923.110361.250926.11417

Indicators of compromise (SHA-256)

dc3947179861f0fa6bf0b6aa75d2b97d79e9cdc38a7a8da42ac38065c55cb061

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05853

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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