NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

fnd-storesnpm

Advisory published Updated

fnd-stores is a confirmed malicious npm package (MAL-2026-4565) that executes malicious code on install (malicious versions 0.0.6, 0.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fnd-stores (npm)

MAL-2026-4565
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall fnd-stores

What this malware does

On npm install, the package's postinstall hook runs node index.js, which collects the installer's hostname, OS platform, current working directory, CI environment indicators, Node version, and OS username via os.hostname(), os.platform(), os.userInfo(), process.cwd(), and process env, and POSTs the payload as JSON to https://webhook.site/604bab71-0179-419e-998e-6f15e524bfd7 (a publisher-controlled webhook bin). The README self-describes the package as a dependency-confusion canary targeting an internal package namespace, and the name is chosen to collide with that internal scope. Any developer or build pipeline that resolves this package leaks internal hostnames, usernames, working-directory paths, and CI job metadata to a third party at install time, without consent. Claimed 'authorized research' status does not change the installer-side harm.

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

2 flagged
0.0.60.0.7

Indicators of compromise (SHA-256)

0ffc68b4ac2b7db114c3c44fa1a89b5ee6cd0e1a25a083513e9213549a311384
62c9035e303ec731c71c689ed77eed17b245cd4adc475cb616ff94991539aa56
70481954c70dee24f0745b6784c3499f98cd0bdb3beee58efeea1d5245f73491
d1d7f2066249d7a3e4ddc55ec1c1f28c865787e5d745503e8d656ed74a428570
a5a8570b79443f0d67df3ba972632cad2ea7227e3be9907edaa1c6e9a140f166

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for fnd-stores (2 malicious versions).

  2. If you installed it — respond

    Remove fnd-stores 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.

  3. Did it already run?

    If fnd-stores 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. fnd-stores on npm has been identified as a malicious package (versions 0.0.6, 0.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004553IN-MAL-2026-004552IN-MAL-2026-004007IN-MAL-2026-004006GHSA-wx9h-pmqq-rcgg

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks fnd-stores-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.

Explore

fnd-stores (npm) malicious package — MAL-2026-4565 | O3 Security