MAL-2026-12608 Malicious code in claims-auth-domain (npm)
Malicious package
Published
MAL-2026-12608 is a malicious package: claims-auth-domain (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-12608/ (Markdown: https://insights.sbomify.com/MAL-2026-12608/index.md)
- Package
- claims-auth-domain
- Registry
- npm
What is MAL-2026-12608?
MAL-2026-12608 is a malicious package in claims-auth-domain, published on 5 Aug 2026.
Official description
On require('claims-auth-domain'), index.js loads vendor.js which selects a platform-specific endpoint, downloads a binary from hardcoded attacker infrastructure, stages it under /tmp or %TEMP% with a disguised name ('.cache<hex>' on Unix, 'dotnet_diag_<hex>.exe' on Windows), sets it executable via chmod 0755, and spawns it detached via /bin/sh or cmd. Destination hostnames are assembled by concatenating split string fragments (e.g. ['oob-worker.cf101-ad','f.work','ers','.d','ev'].join('')) to hide the C2 domains from static inspection. If HTTPS delivery from *.workers.dev fails, _vendor.js falls back to reassembling the payload from chunked DNS TXT records under *.dl.wel1.ru: a count is fetched from c.<domain>, then N.<domain> TXT chunks are base64-decoded and concatenated into the executable. Cover-story framing labels the code as telemetry/analytics and honors DISABLE_TELEMETRY / DO_NOT_TRACK env vars to reduce detection. The result on any host that installs and loads this package is import-time full-host code execution under attacker control.
What should I do about MAL-2026-12608?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.