MAL-2026-13950 Malicious code in fmt-util-k7x2 (npm)
Malicious package
Published
MAL-2026-13950 is a malicious package: fmt-util-k7x2 (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-13950/ (Markdown: https://insights.sbomify.com/MAL-2026-13950/index.md)
- Package
- fmt-util-k7x2
- Registry
- npm
What is MAL-2026-13950?
MAL-2026-13950 is a malicious package in fmt-util-k7x2, published on 13 Aug 2026.
Official description
[email protected] advertises itself as a trivial string-formatting utility (index.js exports two-line pad/trim helpers), but its package.json declares a postinstall hook that runs setup.js on every npm install. setup.js probes a list of Twilio-internal hostnames (including code.hq.twilio.com, stage.twilio.com, twilio.jfrog.io, artifacts.twilio.com) and the AWS EC2 instance metadata endpoint at 169.254.169.254, then concatenates the per-target reachability results and sends them as a query string to a hardcoded external host at http://whstool.brkd.no/cb53e6db-e043-4383-89e9-853c9088ee5d?v=<results>. The per-install UUID callback identifies each victim uniquely, and the target set (internal corporate hostnames + cloud metadata service) matches the dependency-confusion reconnaissance pattern. The exfil destination is not owned by Twilio and is unrelated to the package's advertised purpose. The random-suffix name and mismatch between advertised functionality and postinstall behavior are consistent with a targeted dependency-confusion package aimed at Twilio build environments.
What should I do about MAL-2026-13950?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.