webpack-cache-reset

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (fee0027f45dd4846b52b99120af39a0bca88f8693047612e946cd8d816f36e6c)
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.

## Source: ghsa-malware (e1eba3ce620a4c719ce4540d6dba27a804a00b1adaf564be5fa4a2a4735fc5aa)
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.

Compromised versions (1)

• 0.1.4

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.