# MAL-2026-6491: Malicious code in hexo-deployer-wrangler (npm)


- **Type:** Malicious package
- **Package:** `hexo-deployer-wrangler` (npm)
- **Published:** 26 Jun 2026
- **Also known as:** GHSA-vx8x-rr42-fwhx

## What is MAL-2026-6491?

MAL-2026-6491 is a malicious package in hexo-deployer-wrangler, published on 26 Jun 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-6491?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6491 is a malicious package: hexo-deployer-wrangler (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-6491/ (Markdown: https://insights.sbomify.com/MAL-2026-6491/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6491

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6491/
Summaries are generated and may contain mistakes; the official description above is the record.