Which versions of @crowdstrike/falcon-shoelace are malicious?

The following npm versions of @crowdstrike/falcon-shoelace are flagged malicious: 0.4.1, 0.4.2. Treat any of these as compromised.

How do I remediate @crowdstrike/falcon-shoelace if I installed it?

@crowdstrike/falcon-shoelace 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 @crowdstrike/falcon-shoelace — how do I know if it already compromised me?

If @crowdstrike/falcon-shoelace 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 @crowdstrike/falcon-shoelace part of a known attack campaign?

Yes — @crowdstrike/falcon-shoelace is associated with the GHSA-865r-gxc5-8692 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 @crowdstrike/falcon-shoelace 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 @crowdstrike/falcon-shoelace (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @crowdstrike/falcon-shoelace across your stack and pipelines.

Part of a larger attack: @crowdstrike published 9 malicious packages. See the full campaign →

Malicious package

@crowdstrike/falcon-shoelacenpm

@crowdstrike/falcon-shoelace is a confirmed malicious npm package (MAL-2025-47215) that steals credentials and exfiltrates sensitive data (malicious versions 0.4.1, 0.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @crowdstrike/falcon-shoelace (npm)

MAL-2025-47215

Immediate action

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

npm uninstall @crowdstrike/falcon-shoelace

What this malware does

postinstall script executes bundle.js. bundle.js triggers unsigned_bitwise_math_excess YARA rule. Suspicious behavior indicates malware.

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 by the Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

2 flagged

0.4.10.4.2

Indicators of compromise (SHA-256)

035c35169c1f3c6c939e3237ce0bb606645b05601db61892b5d54cbeea095b57

6779896e34376639f726be3f52e03b5c52b57a2088113c755511de4c7c9e367b

acad1ba0cc0e3df8b17fcb6eb6355c4beb31b0511cf1c6e66a1fd569952e2ddf

ac4a745253d7accb8068782c086c058549af026b20d9043970099f5b6a105b40

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

Campaign

GHSA-865r-gxc5-8692

References

Credits

SafeDep · finder

Detect & block this

O3 blocks @crowdstrike/falcon-shoelace-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