formatting-subtitles-for-claude (npm) · Malicious Code
Affects formatting-subtitles-for-claudeSource GCVE Database
Malicious package : remove formatting-subtitles-for-claude and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 19:44 UTC
Malicious package
Published to npm · OSV MAL-2026-18099
What to do
Remove formatting-subtitles-for-claude from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmformatting-subtitles-for-claude | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f683c00ef9c42d55e37cdb367179f21e58ce2441dba55485d6d19670bcefa700) The package declares a postinstall hook `sh./node_modules/unicode-title-normalizer/x.js && exit 0`, which runs arbitrary shell content shipped by the separate npm dependency `unicode-title-normalizer` on every installer at install time. The package's own visible source (index.js, cli.js, README) is a near-verbatim clone of `unicode-title-normalizer`'s documented API — the README begins `# unicode-title-normalizer` and `index.js` re-implements `normalizeTitle`/`normalizeColor` — while the package is published under the unrelated name `formatting-subtitles-for-claude`. The name/content mismatch combined with the lifecycle hook shelling out to the dependency's `x.js` is a dropper shape: the installer-facing code is a decoy, and the install-time code path executed on the host is whatever bytes the dependency's maintainer chooses to ship at `x.js`, with no pinning beyond a version range, no integrity check, and no inspection. ## Source: ghsa-malware (df3e538de57455a661949a30ffd71da5534d5f36c59147155be0b957d9e427df) 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.