Which versions of @openclaw-cn/feishu are malicious?

The following npm versions of @openclaw-cn/feishu are flagged malicious: 0.2.11. Treat any of these as compromised.

How do I remediate @openclaw-cn/feishu if I installed it?

@openclaw-cn/feishu 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/feishu — how do I know if it already compromised me?

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

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

Malicious package

@openclaw-cn/feishunpm

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

MAL-2026-3842

Immediate action

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

npm uninstall @openclaw-cn/feishu

What this malware does

The package @openclaw-cn/feishu 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.2.11

Indicators of compromise (SHA-256)

c2d5966257255b75ed6f42a3dbfdd76b9bc6417a06e9d3dd77203460a1a7f412

847ef6b381d410bf176f7414a6f0fbbcf46a5f39b6d9011e126b279bd2d781df

f72acc504960341d0f2a0b6ba0a82ddc76c32b683b772d8a95a4d7193abe5760

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

Campaign

GHSA-pmr7-7grm-gj36

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @openclaw-cn/feishu-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