MAL-2026-12643 Malicious code in claims-should-retry (npm)
Malicious package
Published
MAL-2026-12643 is a malicious package: claims-should-retry (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-12643/ (Markdown: https://insights.sbomify.com/MAL-2026-12643/index.md)
- Package
- claims-should-retry
- Registry
- npm
What is MAL-2026-12643?
MAL-2026-12643 is a malicious package in claims-should-retry, published on 5 Aug 2026.
Official description
On require of the package, index.js loads platform.js, which reconstructs destination hosts from split string arrays (e.g. Cloudflare Workers subdomains under oob-worker.cf*-*.workers.dev) via.join("") to hide them from static inspection, downloads a platform-specific binary, writes it to /tmp or %TEMP% under a misleading name (dotnet_diag.exe or.cache_), chmods it 0755, and spawns it detached with stdio ignored via child_process spawn against /bin/sh or cmd. If HTTP fetch fails, a DNS-TXT covert-channel fallback enumerates numbered TXT records under reconstructed *.dl.wel1.ru subdomains, base64-decodes and concatenates them into an executable buffer that is written and executed the same way. A.analytics_state / analytics_state marker file suppresses re-execution, opt-out environment variables (DISABLE_TELEMETRY, ANALYTICS_OPT_OUT, DO_NOT_TRACK) provide a telemetry cover story, and a no-op logger overwrites console output to suppress traces. The package is advertised as a claims-retry library and has no relation to fetching or executing platform binaries.
What should I do about MAL-2026-12643?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.