Malicious code in checkout-mobile-accounts (npm)
The npm package 'checkout-mobile-accounts' version 35.6.8 contains malicious code that, upon being required, downloads and executes a remote binary payload specific to the operating system. The payload is fetched from dynamically constructed hostnames to evade static detection and uses a DNS-TXT covert channel as a fallback. The downloaded executable is saved to temporary directories with names mimicking system diagnostic files, given executable permissions, and run detached from the main process. Additionally, a lock file is created to masquerade as telemetry state. The package falsely advertises itself as a mobile SDK/platform adapter and does not include native source code to justify this behavior.
AI Analysis
Technical Summary
The 'checkout-mobile-accounts' npm package version 35.6.8 contains embedded malicious functionality that triggers on module import. It loads a platform-specific JavaScript file (_platform.js) that constructs obfuscated hostnames at runtime to download an executable payload from multiple worker.dev subdomains and a Russian domain, with a DNS-TXT covert channel fallback for payload retrieval. The payload is saved to system temporary directories under deceptive filenames (e.g., dotnet_diag_<hex>.exe on Windows, .cache_<hex> on Unix), permissions are set to executable (chmod 0755), and the payload is executed detached via shell commands (/bin/sh -c or cmd.exe). A lock file named .analytics_state is created to blend in as legitimate telemetry data. The package's behavior is inconsistent with its advertised purpose and lacks native source code that would justify fetching and executing remote binaries at import time.
Potential Impact
This malicious package can lead to arbitrary code execution on the host system when the package is imported, potentially allowing attackers to run unauthorized executables with the privileges of the importing process. The use of obfuscated hostnames and covert DNS-TXT fallback channels complicates detection and analysis. The deceptive file naming and telemetry masquerading increase the likelihood of evading user suspicion and automated defenses.
Mitigation Recommendations
No official patch or remediation is currently documented for this package version. Users should avoid using 'checkout-mobile-accounts' version 35.6.8 and remove it from their projects. Consider auditing dependencies for similar malicious behavior. Monitor for updates or advisories from the package maintainers or npm registry. Since this is a malicious package, replacing it with a trusted alternative or removing it entirely is recommended.
Malicious code in checkout-mobile-accounts (npm)
Description
The npm package 'checkout-mobile-accounts' version 35.6.8 contains malicious code that, upon being required, downloads and executes a remote binary payload specific to the operating system. The payload is fetched from dynamically constructed hostnames to evade static detection and uses a DNS-TXT covert channel as a fallback. The downloaded executable is saved to temporary directories with names mimicking system diagnostic files, given executable permissions, and run detached from the main process. Additionally, a lock file is created to masquerade as telemetry state. The package falsely advertises itself as a mobile SDK/platform adapter and does not include native source code to justify this behavior.
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 'checkout-mobile-accounts' npm package version 35.6.8 contains embedded malicious functionality that triggers on module import. It loads a platform-specific JavaScript file (_platform.js) that constructs obfuscated hostnames at runtime to download an executable payload from multiple worker.dev subdomains and a Russian domain, with a DNS-TXT covert channel fallback for payload retrieval. The payload is saved to system temporary directories under deceptive filenames (e.g., dotnet_diag_<hex>.exe on Windows, .cache_<hex> on Unix), permissions are set to executable (chmod 0755), and the payload is executed detached via shell commands (/bin/sh -c or cmd.exe). A lock file named .analytics_state is created to blend in as legitimate telemetry data. The package's behavior is inconsistent with its advertised purpose and lacks native source code that would justify fetching and executing remote binaries at import time.
Potential Impact
This malicious package can lead to arbitrary code execution on the host system when the package is imported, potentially allowing attackers to run unauthorized executables with the privileges of the importing process. The use of obfuscated hostnames and covert DNS-TXT fallback channels complicates detection and analysis. The deceptive file naming and telemetry masquerading increase the likelihood of evading user suspicion and automated defenses.
Mitigation Recommendations
No official patch or remediation is currently documented for this package version. Users should avoid using 'checkout-mobile-accounts' version 35.6.8 and remove it from their projects. Consider auditing dependencies for similar malicious behavior. Monitor for updates or advisories from the package maintainers or npm registry. Since this is a malicious package, replacing it with a trusted alternative or removing it entirely is recommended.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12570
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a735732bf8831d53913d037
Added to database: 08/05/2026, 15:30:58 UTC
Last enriched: 08/05/2026, 15:55:45 UTC
Last updated: 08/05/2026, 15:55:45 UTC
Views: 2
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.