Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in html-to-gutenberg (npm)

GHSA-2gqj-wrf5-35w8

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm html-to-gutenberg

    Affected
    >= 4.2.11, <= 4.2.11>= 4.2.14, <= 4.2.14>= 4.2.16, <= 4.2.16>= 4.2.15, <= 4.2.15>= 4.2.13, <= 4.2.13>= 4.2.12, <= 4.2.12>= 4.2.17, <= 4.2.17>= 4.2.18, <= 4.2.18>= 4.2.19, <= 4.2.19>= 4.2.20, <= 4.2.20>= 4.2.21, <= 4.2.21>= 4.2.22, <= 4.2.22>= 4.2.26, <= 4.2.26>= 4.2.25, <= 4.2.25>= 4.2.24, <= 4.2.24
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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

Source: amazon-inspector (ad55bd01687902eea54021b3d30ce0b10f795a1521b425b32e57ef46b7a4ae77) The published tarball contains api.js at the package root, a heavily obfuscated loader using an obfuscator.io-style XOR-decoded string table (key 0x46) that reconstructs identifiers including 'constructor', stashes require and module on the global object, and uses Function(...) to compile and immediately invoke an approximately 9.6 KB decoded payload. The file is referenced only by the author's manual scripts.build step (node api.js && tsc); it is not referenced by the package's main entry (index.js), not imported by any reachable module, and not invoked by the declared postinstall. The postinstall script performs a local file-copy of vendor/fetch-page-assets/index.ts into node_modules via fs.copyFileSync with no network I/O and no shell exec of api.js. Because the obfuscated loader is dormant on both npm install and require of the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record MAL-2026-6359

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-2gqj-wrf5-35w8

Advisory: Malicious code in html-to-gutenberg (npm)
IDs: GHSA-2gqj-wrf5-35w8
Record: https://patchnext.com/advisories/mal-2026-6359 (revision 1, source checked 30 Oct 2026, 06:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm html-to-gutenberg: affected >= 4.2.11, <= 4.2.11; >= 4.2.14, <= 4.2.14; >= 4.2.16, <= 4.2.16; >= 4.2.15, <= 4.2.15; >= 4.2.13, <= 4.2.13; >= 4.2.12, <= 4.2.12; >= 4.2.17, <= 4.2.17; >= 4.2.18, <= 4.2.18; >= 4.2.19, <= 4.2.19; >= 4.2.20, <= 4.2.20; >= 4.2.21, <= 4.2.21; >= 4.2.22, <= 4.2.22; >= 4.2.26, <= 4.2.26; >= 4.2.25, <= 4.2.25; >= 4.2.24, <= 4.2.24

## Suggested inspection (read-only)
- `npm ls html-to-gutenberg --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on html-to-gutenberg.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-6359 (OSV record MAL-2026-6359 lists affected ranges: npm html-to-gutenberg >=4.2.11 =4.2.14 =4.2.16 =4.2.15 =4.2.13 =4.2.12 =4.2.17 =4.2.18 =4.2.19 =4.2.20 =4.2.21 =4.2.22 =4.2.26 =4.2.25 =4.2.24 <=4.2.24)

Commands are suggestions: review each one before running it.

Loading voting…