Which versions of webpack-cache-reset are malicious?

The following npm versions of webpack-cache-reset are flagged malicious: 0.1.4. Treat any of these as compromised.

How do I remediate webpack-cache-reset if I installed it?

webpack-cache-reset is a typosquat — you almost certainly intended a legitimately-named package. Remove webpack-cache-reset, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed webpack-cache-reset — how do I know if it already compromised me?

If webpack-cache-reset 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 webpack-cache-reset part of a known attack campaign?

Yes — webpack-cache-reset is associated with the IN-MAL-2026-005545, IN-MAL-2026-005543, GHSA-x29m-589q-wmg6 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 webpack-cache-reset 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 webpack-cache-reset (version 0.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging webpack-cache-reset across your stack and pipelines.

Malicious package

webpack-cache-resetnpm

webpack-cache-reset is a confirmed malicious npm package (MAL-2026-5580) that typosquats a legitimate package to trick installs (malicious version 0.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in webpack-cache-reset (npm)

MAL-2026-5580

Immediate action

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

npm uninstall webpack-cache-reset

What this malware does

On npm install, the package's postinstall hook runs loader.js, which hex-decodes the URL https://jsonkeeper.com/b/INN1F (an anonymous JSON paste host), fetches the response, writes the embedded manifest.session payload to a temporary.js file, and require()'s it inside a detached child node process — executing attacker-controlled JavaScript on the installer's machine. The URL is obfuscated via Buffer.from(<hex>, 'hex') and the temporary file is cleaned up after load to hide traces. The package additionally impersonates a webpack utility: README is titled 'webpack-cache-plugin' and instructs users to npm install webpack-cache-plugin --save-dev, while the published name is 'webpack-cache-reset' and the declared repository (github.com/webpack-tools/webpack-cache-plugin) does not exist. Installers are lured under a webpack-ecosystem name into running arbitrary remote code at install time.

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

1 flagged

0.1.4

Indicators of compromise (SHA-256)

7092bc577f8d9ec2d9b04d6afd5beffb37f4e9d7677a3c378397c0f350766be5

fee0027f45dd4846b52b99120af39a0bca88f8693047612e946cd8d816f36e6c

e1eba3ce620a4c719ce4540d6dba27a804a00b1adaf564be5fa4a2a4735fc5aa

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for webpack-cache-reset (version 0.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging webpack-cache-reset across your stack and pipelines.
If you installed it — respond
webpack-cache-reset is a typosquat — you almost certainly intended a legitimately-named package. Remove webpack-cache-reset, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If webpack-cache-reset 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 webpack-cache-reset 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. webpack-cache-reset on npm has been identified as a malicious package (version 0.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005545IN-MAL-2026-005543GHSA-x29m-589q-wmg6

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks webpack-cache-reset-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