Which versions of ldhpgemrdhs83600 are malicious?

The following npm versions of ldhpgemrdhs83600 are flagged malicious: 1.250921.10006, 1.250923.11035, 1.250926.11416. Treat any of these as compromised.

How do I remediate ldhpgemrdhs83600 if I installed it?

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

If ldhpgemrdhs83600 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ldhpgemrdhs83600 part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ldhpgemrdhs83600 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ldhpgemrdhs83600 across your stack and pipelines.

Malicious package

ldhpgemrdhs83600npm

ldhpgemrdhs83600 is a confirmed malicious npm package (MAL-2025-48722) that executes malicious code on install (malicious versions 1.250921.10006, 1.250923.11035, 1.250926.11416). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhpgemrdhs83600 (npm)

MAL-2025-48722

Immediate action

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

npm uninstall ldhpgemrdhs83600

What this malware does

The package ldhpgemrdhs83600 was found to contain malicious code.

Malicious versions

3 flagged

1.250921.100061.250923.110351.250926.11416

Indicators of compromise (SHA-256)

9f348a698f80b5526357ab0debeda6dd67ab978393e9d1f300cd0737f122a284

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ldhpgemrdhs83600 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ldhpgemrdhs83600 across your stack and pipelines.
If you installed it — respond
Remove ldhpgemrdhs83600 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 ldhpgemrdhs83600 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ldhpgemrdhs83600 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ldhpgemrdhs83600 on npm has been identified as a malicious package (versions 1.250921.10006, 1.250923.11035, 1.250926.11416 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05851

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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