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

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

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

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

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

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

Malicious package

@openclaw-cn/libsignalnpm

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

MAL-2026-3843

Immediate action

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

npm uninstall @openclaw-cn/libsignal

What this malware does

The package @openclaw-cn/libsignal 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

2.1.1

Indicators of compromise (SHA-256)

0b5dce9628f99687cff8d08fed8e5bbdc9f65b5f823459cb1a0d7fcc4593a476

847ef6b381d410bf176f7414a6f0fbbcf46a5f39b6d9011e126b279bd2d781df

85fb1bd455a85140d13ec5cb826c0f8c6164c87a6eeacd72f7fc525440b76f24

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

Campaign

GHSA-wcjp-mfw5-77g8

References

Credits

Amazon Inspector · finder

Detect & block this

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