Which versions of ldhpgemrdhs92009 are malicious?

The following npm versions of ldhpgemrdhs92009 are flagged malicious: 1.250920.11031, 1.250923.11038, 1.250926.11419. Treat any of these as compromised.

How do I remediate ldhpgemrdhs92009 if I installed it?

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

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

Yes — ldhpgemrdhs92009 is associated with the RLMA-2025-05856 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 ldhpgemrdhs92009 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 ldhpgemrdhs92009 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ldhpgemrdhs92009 across your stack and pipelines.

Malicious package

ldhpgemrdhs92009npm

ldhpgemrdhs92009 is a confirmed malicious npm package (MAL-2025-48727) that executes malicious code on install (malicious versions 1.250920.11031, 1.250923.11038, 1.250926.11419). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhpgemrdhs92009 (npm)

MAL-2025-48727

Immediate action

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

npm uninstall ldhpgemrdhs92009

What this malware does

The package ldhpgemrdhs92009 was found to contain malicious code.

Malicious versions

3 flagged

1.250920.110311.250923.110381.250926.11419

Indicators of compromise (SHA-256)

e2554c0086d6e81dc2c07667183cb62eae880d798ca1d328356eabdad8693c0f

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 ldhpgemrdhs92009 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ldhpgemrdhs92009 across your stack and pipelines.
If you installed it — respond
Remove ldhpgemrdhs92009 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 ldhpgemrdhs92009 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 ldhpgemrdhs92009 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. ldhpgemrdhs92009 on npm has been identified as a malicious package (versions 1.250920.11031, 1.250923.11038, 1.250926.11419 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05856

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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