Which versions of webpack-cache-clean are malicious?

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

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

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

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

Yes — webpack-cache-clean is associated with the IN-MAL-2026-005544, GHSA-82q4-cw9w-vjj4 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-clean 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-clean (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-clean across your stack and pipelines.

Malicious package

webpack-cache-cleannpm

webpack-cache-clean is a confirmed malicious npm package (MAL-2026-5578) that executes malicious code on install (malicious version 0.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in webpack-cache-clean (npm)

MAL-2026-5578

Immediate action

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

npm uninstall webpack-cache-clean

What this malware does

On npm install, the package runs a postinstall hook (node -e "require('./loader.js')") that spawns a detached child process. The child decodes an obfuscated base64 URL (mislabeled as 'hex' with large whitespace padding) resolving to https://jsonkeeper.com/b/L435A, an anonymous JSON paste host, performs an HTTPS GET, extracts JavaScript source from a manifest.session field, writes it to a temp file, and require()s it — with no signature, hash, or pinned-version check. The fetched code runs with the installer's privileges and can be changed by the attacker between fetches. The package metadata is also inconsistent: the package name is webpack-cache-clean, the README is titled webpack-cache-plugin, the repository URL points at webpack-tools/webpack-cache-plugin, and the author is the generic Webpack Tools — a cover story to lure installers searching for legitimate webpack cache tooling. This satisfies install-time-rce: attacker-controlled, unpinned, obfuscated remote code execution fires automatically on default install.

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)

8f8656d094ec59721c08eb72a1ec8f1530cd07985edf705032926dd9a19461d9

6f98923d9f08741f534522f4b816b09d5953f8d73ddbaef49710ba42236a9cff

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 webpack-cache-clean (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-clean across your stack and pipelines.
If you installed it — respond
Remove webpack-cache-clean 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 webpack-cache-clean 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-clean 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-clean 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-005544GHSA-82q4-cw9w-vjj4

References

Credits

Amazon Inspector · finder

Detect & block this

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