hexo-deployer-wrangler

The package ships a binding.gyp file (line 6) containing GYP command-expansion syntax (`<!(...)`) inside the targets/sources fields. npm implicitly runs `node-gyp rebuild` whenever a binding.gyp is present — even without a declared install/postinstall script — and GYP evaluates `<!(...)` as a shell command during the configure step. This causes arbitrary code execution on the installer's machine on default `npm install`, functionally identical to a lifecycle hook. The package does not ship any native source files (no.c/.cc/.cpp/.h) that would justify a real node-gyp build configuration, indicating the binding.gyp's sole purpose is to run the embedded shell command. The package name also impersonates the legitimate hexo-deployer-* ecosystem combined with Cloudflare's wrangler tooling, a typical lure pattern. ## Source: ghsa-malware (4cdcfdb81b50ac4d732bd65961169e22bfafc58198e591a41e5c359ae12fab95) 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.