Which versions of webpack-cache-cycle are malicious?

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

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

webpack-cache-cycle is a typosquat — you almost certainly intended a legitimately-named package. Remove webpack-cache-cycle, 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-cycle — how do I know if it already compromised me?

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

Yes — webpack-cache-cycle is associated with the IN-MAL-2026-005548, IN-MAL-2026-005547, GHSA-2p34-5qgm-wr3f 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-cycle 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-cycle (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-cycle across your stack and pipelines.

Malicious package

webpack-cache-cyclenpm

webpack-cache-cycle is a confirmed malicious npm package (MAL-2026-5579) 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-cycle (npm)

MAL-2026-5579

Immediate action

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

npm uninstall webpack-cache-cycle

What this malware does

On npm install, package.json's postinstall hook runs node -e "require('./loader.js')". loader.js spawns a detached node process that decodes a hex-encoded URL (https://jsonkeeper.com/b/L435A — an anonymous, mutable paste host), performs an HTTPS GET, writes the response's session field to a temporary.js file, and require()s it — executing attacker-controlled JavaScript on the installer's machine. The URL is obfuscated as a hex literal padded with whitespace inside Buffer.from(...) to evade naive string scanners. The detached spawn lets npm install exit cleanly while the dropper continues asynchronously. The package's advertised purpose is a webpack cache plugin, which does not justify any network access at install time. The package name webpack-cache-cycle and README title webpack-cache-plugin impersonate legitimate webpack tooling, with placeholder author metadata (Webpack Tools) and a non-existent GitHub repository.

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)

028ed41ba1afb95bb86e0ae1536f3e9b4a2695fc8490b7d83033ac86440d59c5

82fa37e2478a7109e376e3a062ccb203806511033930eb7390e45fe7ef404b81

1a7e46df199f0d8dbede5404aab0ad253bb78bce77001d4b875d116806d9839d

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-cycle (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-cycle across your stack and pipelines.
If you installed it — respond
webpack-cache-cycle is a typosquat — you almost certainly intended a legitimately-named package. Remove webpack-cache-cycle, 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-cycle 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-cycle 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-cycle 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-005548IN-MAL-2026-005547GHSA-2p34-5qgm-wr3f

References

Credits

Amazon Inspector · finder

Detect & block this

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