Which versions of openhands-frontend are malicious?

The following npm versions of openhands-frontend are flagged malicious: 999.0.104. Treat any of these as compromised.

How do I remediate openhands-frontend if I installed it?

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

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

Yes — openhands-frontend is associated with the GHSA-f5xm-4hwm-3fmf, RLMA-2026-01473 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 openhands-frontend 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 openhands-frontend (version 999.0.104). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging openhands-frontend across your stack and pipelines.

Malicious package

openhands-frontendnpm

Malicious code in openhands-frontend (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192593

Immediate action

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

npm uninstall openhands-frontend

What this malware does

The package openhands-frontend was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

999.0.104

Indicators of compromise (SHA-256)

f2e0d05425858881101b0cd3c39d8cdc2e0b851aa8e3056f52d73e667c33b5ba

3094854e6f43f64c218e6ccdf21f319cff916fef4a412442faccf4b9cd616fe9

02d72ee884fb0e1862237ba39c0882055b018d2c41d1a9b75606d018d15f86cf

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

Campaign

GHSA-f5xm-4hwm-3fmfRLMA-2026-01473

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks openhands-frontend-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