Which versions of @crowdstrike/logscale-search are malicious?

The following npm versions of @crowdstrike/logscale-search are flagged malicious: 1.205.1, 1.205.2. Treat any of these as compromised.

How do I remediate @crowdstrike/logscale-search if I installed it?

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

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

Yes — @crowdstrike/logscale-search is associated with the GHSA-vf8g-9pcq-qcv8 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/logscale-search 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/logscale-search (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/logscale-search across your stack and pipelines.

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

Malicious package

@crowdstrike/logscale-searchnpm

@crowdstrike/logscale-search is a confirmed malicious npm package (MAL-2025-47236) that steals credentials and exfiltrates sensitive data (malicious versions 1.205.1, 1.205.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @crowdstrike/logscale-search (npm)

MAL-2025-47236

Immediate action

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

npm uninstall @crowdstrike/logscale-search

What this malware does

The package was compromised and malicious code added.

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

1.205.11.205.2

Indicators of compromise (SHA-256)

bf328d64388e35603ec9a233e2d1ba28fa6fd2508bf245a22733a1818a670e92

2acb3191aa7b2815baad47245d3627598295b87e24e9fcd56453aebe2fc181e7

321a8c3b4c45b531a540bec1ed4c4f3c29848f402e7a31c551ffd1589d372e96

dd01ba68bddf9940a9c9ff872c0db6f566838b7c50214f88e0f3783357291f43

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/logscale-search (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/logscale-search across your stack and pipelines.
If you installed it — respond
@crowdstrike/logscale-search 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/logscale-search 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/logscale-search 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/logscale-search on npm has been identified as a malicious package (versions 1.205.1, 1.205.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vf8g-9pcq-qcv8

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @crowdstrike/logscale-search-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