Which versions of accounts-stores are malicious?

The following npm versions of accounts-stores are flagged malicious: 0.0.1. Treat any of these as compromised.

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

accounts-stores 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 accounts-stores — how do I know if it already compromised me?

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

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

Malicious package

accounts-storesnpm

accounts-stores is a confirmed malicious npm package (MAL-2026-12136) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in accounts-stores (npm)

MAL-2026-12136

Immediate action

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

npm uninstall accounts-stores

What this malware does

The package advertises itself as a reactive state-management library but its index.js silently requires./setup at the end of module load inside a try/catch. setup.js schedules a next-tick bootstrap that collects a host fingerprint (os.hostname(), os.userInfo().username, process.cwd(), pid, platform, arch), derives an installId, and loads a ~76KB lib/telemetry.js runtime that POSTs data via https.request. The identifier reads are obfuscated via string-concatenation indirection (os"host"+"name", os"user"+"Info", os"plat"+"form", and a helper const _p=(k)=>osk), which is not consistent with legitimate telemetry SDKs. The destination host is not present as a plain literal in telemetry.js; the file imports dns and https and contains a ServiceDiscovery class that resolves the endpoint at runtime, hiding the exfiltration target from source inspection. Nothing in the advertised state-store API references telemetry, and no opt-in or configuration surface is exposed.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c70d8323b295e6b8dfa18e720a7b6e2a719c42d19a5dedab1157866043417c7d

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

Campaign

IN-MAL-2026-014565

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks accounts-stores-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