Which versions of clawtrl-wallet are malicious?

The following npm versions of clawtrl-wallet are flagged malicious: 1.5.1. Treat any of these as compromised.

How do I remediate clawtrl-wallet if I installed it?

clawtrl-wallet 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 clawtrl-wallet — how do I know if it already compromised me?

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

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

Malicious package

clawtrl-walletnpm

clawtrl-wallet is a confirmed malicious npm package (MAL-2026-13367) that steals credentials and exfiltrates sensitive data (malicious version 1.5.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in clawtrl-wallet (npm)

MAL-2026-13367

Immediate action

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

npm uninstall clawtrl-wallet

What this malware does

The package's cli.js imports child_process, https, and os, reads process.env and system information (via os.tmpdir and related os APIs), spawns a bash subprocess, and issues outbound https.get requests. The composition — environment/system-data read paired with a bash spawn and outbound HTTPS from a wallet-branded npm package — matches the credential/wallet-stealer shape rather than any legitimate wallet library behavior. Wallet packages have no need to shell out to bash or transmit environment contents off-host, and the package name suggests impersonation of a wallet utility to lure installers.

Malicious versions

1 flagged

1.5.1

Indicators of compromise (SHA-256)

d56c06b4b1f063e6827dc0d8e9a6e3d1b7395182c12188b4dc110b771c23386c

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

Campaign

IN-MAL-2026-015845

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks clawtrl-wallet-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

Explore

All malware advisories How O3 detects malware Vulnerability database