Which versions of scan-store are malicious?

Every published version of scan-store on npm is considered malicious. Remove the package entirely.

How do I remediate scan-store if I installed it?

Remove scan-store from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed scan-store — how do I know if it already compromised me?

If scan-store was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is scan-store part of a known attack campaign?

Yes — scan-store is associated with the GHSA-v858-hgfg-q94p 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 scan-store across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for scan-store (all published versions).

Malicious package

scan-storenpm

Advisory published Feb 20, 2026Updated Feb 23, 2026

scan-store is a confirmed malicious npm package (MAL-2026-969) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in scan-store (npm)

MAL-2026-969

Immediate action

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

npm uninstall scan-store

What this malware does

The package scan-store 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

ebbe0d7aca9839086433d668a6b236303aa5f4c8be102ffbb7ffc9a8d73ad79c

b30789e67692889309fe10b2d66e73649dfffbf9644ad1d11175b74334e5473c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for scan-store (all published versions).
If you installed it — respond
Remove scan-store from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If scan-store was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. scan-store on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-v858-hgfg-q94p

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks scan-store-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database