Which versions of openclaw-cn are malicious?

The following npm versions of openclaw-cn are flagged malicious: 0.3.0. Treat any of these as compromised.

How do I remediate openclaw-cn if I installed it?

openclaw-cn is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed openclaw-cn — how do I know if it already compromised me?

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

Yes — openclaw-cn is associated with the GHSA-w2fv-p53h-wcph 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 openclaw-cn 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 openclaw-cn (version 0.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging openclaw-cn across your stack and pipelines.

Malicious package

openclaw-cnnpm

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

MAL-2026-3847

Immediate action

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

npm uninstall openclaw-cn

What this malware does

The package openclaw-cn 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.

This package was compromised as part of the ongoing "Mini Shai-Hulud is back" worm by the TeamPCP threat actor.

The package will steal credentials and then propogate it to every package it has access to. The package also attempts to remain persistent.

Malicious versions

1 flagged

0.3.0

Indicators of compromise (SHA-256)

8f29660ec3d5b6462ff4857bf0696a14fbcf401d5f3a074376b0c9840b380612

847ef6b381d410bf176f7414a6f0fbbcf46a5f39b6d9011e126b279bd2d781df

98bf501cd2484b70d4811afe69007c54a9a94bcd9c137c0782a0c610a475b434

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for openclaw-cn (version 0.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging openclaw-cn across your stack and pipelines.
If you installed it — respond
openclaw-cn is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If openclaw-cn 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 openclaw-cn 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. openclaw-cn on npm has been identified as a malicious package (version 0.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w2fv-p53h-wcph

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks openclaw-cn-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring