Which versions of store-webpack-config are malicious?

The following npm versions of store-webpack-config are flagged malicious: 0.0.1-security, 1.0.0. Treat any of these as compromised.

How do I remediate store-webpack-config if I installed it?

Remove store-webpack-config 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 store-webpack-config — how do I know if it already compromised me?

If store-webpack-config 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 store-webpack-config across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for store-webpack-config (2 malicious versions).

Malicious package

store-webpack-confignpm

Advisory published Oct 30, 2025Updated Oct 7, 2026

store-webpack-config is a confirmed malicious npm package (MAL-2025-49241) 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 store-webpack-config (npm)

MAL-2025-49241

Immediate action

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

npm uninstall store-webpack-config

What this malware does

The package store-webpack-config was found to contain malicious code.

Malicious versions

2 flagged

0.0.1-security1.0.0

Indicators of compromise (SHA-256)

13f10add046b94b627520507423f73982964e7be0734c7b4909acee5710f1e7e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for store-webpack-config (2 malicious versions).
If you installed it — respond
Remove store-webpack-config 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 store-webpack-config 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. store-webpack-config 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 store-webpack-config-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