Entropy Backdoor in text-qrcode

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

All versions of text-qrcode contain malicious code that overwrites the randomBytes method for the crypto module with a function that generates weak entropy. Instead of generating 32 bytes, the infected randomBytes will generate 3 bytes of entropy and hash them, resulting in a 32 byte value being returned, but one that is easily guessable. Recommendation Uninstall text-qrcode immediately. If the module was used to generate entropy that is load bearing, all such instances of generated entropy must be replaced. This includes things like bitcoin wallets, private keys, encrypted messages, etc.

Published by the source

1 Sep 2020, 21:22 UTC

Last modified by the source

9 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 12:09 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-h5vj-f7r9-w564

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-h5vj-f7r9-w564

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

# Patch Next advisory brief: GHSA-h5vj-f7r9-w564

Advisory: Entropy Backdoor in text-qrcode
IDs: GHSA-h5vj-f7r9-w564
Record: https://patchnext.com/advisories/ghsa-h5vj-f7r9-w564 (revision 2, source checked 26 Oct 2026, 12:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
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 text-qrcode: affected every version

## Suggested inspection (read-only)
- `npm ls text-qrcode --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 text-qrcode.
- 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/GHSA-h5vj-f7r9-w564 (OSV record GHSA-h5vj-f7r9-w564 lists affected ranges: npm text-qrcode >=0.0.0)
- Verified: https://github.com/advisories/GHSA-h5vj-f7r9-w564 (GitHub-reviewed advisory GHSA-h5vj-f7r9-w564 lists affected ranges: npm text-qrcode >=0.0.0)

Commands are suggestions: review each one before running it.