Which versions of fnd-stores are malicious?

The following npm versions of fnd-stores are flagged malicious: 0.0.6, 0.0.7. Treat any of these as compromised.

How do I remediate fnd-stores if I installed it?

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.

I already installed fnd-stores — how do I know if it already compromised me?

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

Yes — fnd-stores is associated with the IN-MAL-2026-004553, IN-MAL-2026-004552, IN-MAL-2026-004007, IN-MAL-2026-004006 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 fnd-stores 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 fnd-stores (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fnd-stores across your stack and pipelines.

Malicious package

fnd-storesnpm

Malicious code in fnd-stores (npm) Remove it immediately and rotate any exposed credentials.

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.

Malicious versions

2 flagged

0.0.60.0.7

Indicators of compromise (SHA-256)

0ffc68b4ac2b7db114c3c44fa1a89b5ee6cd0e1a25a083513e9213549a311384

62c9035e303ec731c71c689ed77eed17b245cd4adc475cb616ff94991539aa56

70481954c70dee24f0745b6784c3499f98cd0bdb3beee58efeea1d5245f73491

d1d7f2066249d7a3e4ddc55ec1c1f28c865787e5d745503e8d656ed74a428570

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fnd-stores (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fnd-stores across your stack and pipelines.
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.
Did it already run?
If fnd-stores 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 fnd-stores 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. 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-004006

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.

Malware detection Runtime egress monitoring