MalwarePublished 15 Jul 2026

webpack-session-cache (npm) · Malicious Code

Affects webpack-session-cacheSource GCVE Database

Malicious package : remove webpack-session-cache and rotate any secrets on hosts that installed it.

Data as of 15 Jul 2026, 12:43 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-10653

What to do

Remove webpack-session-cache from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmwebpack-session-cache	Affected =0.1.4	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package 'webpack-session-cache' version 0.1.4 contains malicious code or a dependency with malicious code. Installation or execution of this package can lead to full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different, trusted machine. Removal of the package alone may not eliminate all malicious components due to potential persistent control by an attacker.

Impact

Full system compromise is indicated for any computer with the affected package installed or running. This includes potential unauthorized access to all stored secrets and keys, requiring immediate rotation of credentials from a secure environment. The attacker may maintain persistent control beyond the presence of the malicious package itself.

Defensive guidance

Remove the 'webpack-session-cache' package version 0.1.4 immediately. Rotate all secrets and keys stored on the compromised system from a separate, trusted computer. Because full control of the system may have been given to an attacker, consider rebuilding or thoroughly cleaning the affected system to ensure complete eradication of malicious components.

Summary

The 'webpack-session-cache' npm package version 0.1.4 has been identified as containing malicious code or depending on a malicious package. Systems with this package installed or running are considered fully compromised, with attackers potentially having full control. The malicious code presence implies that sensitive information such as secrets and keys may be exposed. Due to the severity of the compromise, simple removal of the package does not guarantee complete remediation.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Jul 2026, 12:43 UTC

Technical details

References

Community reviews