Malicious code in claims-should-retry (npm)
The npm package 'claims-should-retry' version 35.6.8 contains malicious code that downloads and executes platform-specific binaries under misleading filenames. It uses obfuscated domain reconstruction to evade static detection and employs a DNS-TXT record covert channel as a fallback to retrieve executable payloads. The package suppresses telemetry and console output to hide its activity. It is advertised as a claims-retry library but performs unauthorized code execution.
AI Analysis
Technical Summary
The 'claims-should-retry' npm package (version 35.6.8) loads a platform-specific binary by reconstructing obfuscated destination hosts from split string arrays to evade static inspection. It downloads the binary, writes it to temporary directories with misleading names (e.g., dotnet_diag_*.exe), sets executable permissions, and spawns it detached with ignored stdio. If the HTTP fetch fails, it falls back to a covert DNS-TXT channel that enumerates and base64-decodes TXT records from specially crafted subdomains to reconstruct and execute the payload. The package suppresses re-execution via marker files and disables telemetry and logging to conceal its behavior. Despite being advertised as a claims-retry library, it performs unauthorized binary execution.
Potential Impact
This malicious package can execute arbitrary platform-specific binaries on the host system, potentially leading to full system compromise or unauthorized actions. The use of obfuscation and covert DNS channels complicates detection and analysis. The suppression of telemetry and logging further hinders incident response efforts.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately remove the affected version (=35.6.8) of the 'claims-should-retry' package from their environments. Avoid installing or using this package until a trusted, verified version is available. Monitor for unexpected child processes spawned by this package and network connections to suspicious domains such as *.dl.wel1.ru. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Malicious code in claims-should-retry (npm)
Description
The npm package 'claims-should-retry' version 35.6.8 contains malicious code that downloads and executes platform-specific binaries under misleading filenames. It uses obfuscated domain reconstruction to evade static detection and employs a DNS-TXT record covert channel as a fallback to retrieve executable payloads. The package suppresses telemetry and console output to hide its activity. It is advertised as a claims-retry library but performs unauthorized code execution.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'claims-should-retry' npm package (version 35.6.8) loads a platform-specific binary by reconstructing obfuscated destination hosts from split string arrays to evade static inspection. It downloads the binary, writes it to temporary directories with misleading names (e.g., dotnet_diag_*.exe), sets executable permissions, and spawns it detached with ignored stdio. If the HTTP fetch fails, it falls back to a covert DNS-TXT channel that enumerates and base64-decodes TXT records from specially crafted subdomains to reconstruct and execute the payload. The package suppresses re-execution via marker files and disables telemetry and logging to conceal its behavior. Despite being advertised as a claims-retry library, it performs unauthorized binary execution.
Potential Impact
This malicious package can execute arbitrary platform-specific binaries on the host system, potentially leading to full system compromise or unauthorized actions. The use of obfuscation and covert DNS channels complicates detection and analysis. The suppression of telemetry and logging further hinders incident response efforts.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should immediately remove the affected version (=35.6.8) of the 'claims-should-retry' package from their environments. Avoid installing or using this package until a trusted, verified version is available. Monitor for unexpected child processes spawned by this package and network connections to suspicious domains such as *.dl.wel1.ru. Patch status is not yet confirmed — check the vendor advisory or trusted security sources for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12643
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a735734bf8831d53913e576
Added to database: 08/05/2026, 15:31:00 UTC
Last enriched: 08/05/2026, 16:14:35 UTC
Last updated: 09/07/2026, 22:13:34 UTC
Views: 18
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.