MAL-2026-12625 Malicious code in claims-historical-claims-domain (npm)
Malicious package
Published
MAL-2026-12625 is a malicious package: claims-historical-claims-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-12625/ (Markdown: https://insights.sbomify.com/MAL-2026-12625/index.md)
- Package
- claims-historical-claims-domain
- Registry
- npm
What is MAL-2026-12625?
MAL-2026-12625 is a malicious package in claims-historical-claims-domain, published on 5 Aug 2026.
Official description
On require, index.js loads bridge.js which selects a platform-specific URL path and downloads a binary via https.get from hostnames assembled by string-splitting fragments such as 'oob-worker.cf*-.workers.dev', with a DNS TXT-record base64 fallback under '.dl.wel1.ru'. The fetched bytes are written to a temp file under a masquerading name (dotnet_diag<rnd>.exe on Windows,.cache_<rnd> on Unix), chmodded 0755, and spawned detached via /bin/sh -c or cmd. No hash or signature verification is performed. A freshness marker file named 'analytics_state' gates re-runs to roughly once per six hours, and code comments frame the behavior as 'telemetry'/'analytics'. Host destinations and artifact names are obfuscated via array-join string splitting to defeat literal-string scanning.
What should I do about MAL-2026-12625?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.