Which versions of egstore-graphql-client are malicious?

The following npm versions of egstore-graphql-client are flagged malicious: 0.0.1-security, 1.0.0. Treat any of these as compromised.

How do I remediate egstore-graphql-client if I installed it?

Remove egstore-graphql-client 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 egstore-graphql-client — how do I know if it already compromised me?

If egstore-graphql-client 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.

How do I find egstore-graphql-client across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for egstore-graphql-client (2 malicious versions).

Malicious package

egstore-graphql-clientnpm

Advisory published Oct 30, 2025Updated Sep 21, 2026

egstore-graphql-client is a confirmed malicious npm package (MAL-2025-49111) that executes malicious code on install (malicious versions 0.0.1-security, 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in egstore-graphql-client (npm)

MAL-2025-49111

Immediate action

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

npm uninstall egstore-graphql-client

What this malware does

The package egstore-graphql-client was found to contain malicious code.

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

2a8f78f2a6abccca4b462d391732c3bc43094be0be51d4d3cc06a1686d1b554e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for egstore-graphql-client (2 malicious versions).
If you installed it — respond
Remove egstore-graphql-client 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 egstore-graphql-client 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. egstore-graphql-client on npm has been identified as a malicious package (versions 0.0.1-security, 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks egstore-graphql-client-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