Which versions of process-lhpm are malicious?

The following npm versions of process-lhpm are flagged malicious: 1.1.79. Treat any of these as compromised.

How do I remediate process-lhpm if I installed it?

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

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

Yes — process-lhpm is associated with the IN-MAL-2026-020062 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 process-lhpm 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 process-lhpm (version 1.1.79). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging process-lhpm across your stack and pipelines.

Malicious package

process-lhpmnpm

process-lhpm is a confirmed malicious npm package (MAL-2026-16178) that executes malicious code on install (malicious version 1.1.79). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in process-lhpm (npm)

MAL-2026-16178

Immediate action

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

npm uninstall process-lhpm

What this malware does

On require/import, index.js auto-invokes initialize(), which spawns a detached, stdio-suppressed node loader.js background process. loader.js performs an HTTPS GET to https://api.npoint.io/33e8d008c334b060adad, base64-decodes the code field of the JSON response, and executes it via new Function('require','__dirname','__filename','module','exports', decodedCode)(...) with full Node privileges and require access. The remote payload URL is stored in a variable named API_KEY to obscure its role. api.npoint.io is a mutable third-party JSON hosting service, so the executed code can be swapped by the operator at any time without republishing the package. The detached child process outlives the importing application, establishing a persistent remote-code-loading channel on any host that imports this package.

Malicious versions

1 flagged

1.1.79

Indicators of compromise (SHA-256)

a663308c4051eb4b31faf7fb984989f3e1b3498e505dc05052e2beb5fbf7e6d2

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

Campaign

IN-MAL-2026-020062

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks process-lhpm-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