checkout-molecule-desktop-status-modalnpm
checkout-molecule-desktop-status-modal is a confirmed malicious npm package (MAL-2026-12581) that executes malicious code on install (malicious version 35.9.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in checkout-molecule-desktop-status-modal (npm)
What this malware does
The package's main entry (index.js) requires./polyfill on load. polyfill.js immediately runs an async routine that reconstructs several hostnames from character-array joins (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf102-baf.workers.dev) and a DNS-fallback discovery domain (sdk.dl.wel1.ru), downloads a platform-specific native binary via HTTPS from those hosts (with a chunked base64 DNS TXT transport as fallback when HTTPS is blocked), writes the bytes to /var/tmp or %TEMP% under disguised names such as.cache/dotnet_diag, chmods 0755, and detaches a background process via spawn("/bin/sh", ["-c", path + " &"], {detached:true}).unref() or cmd.exe /c start. A local.analytics_state marker throttles reruns. A second module, lib/telemetry.js, ships the same write-chmod-exec primitives with dynamic-string API name assembly ("child_"+"process", "chmod"+"Sync") behind an APM/telemetry cover. The advertised purpose of the package is a UI status-modal helper, which has no need to fetch and execute native binaries from anonymous workers.dev subdomains at require() time; there is no hash or signature verification on the downloaded payload.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-molecule-desktop-status-modal (version 35.9.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-molecule-desktop-status-modal across your stack and pipelines.
If you installed it — respond
Remove checkout-molecule-desktop-status-modal from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If checkout-molecule-desktop-status-modal was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks checkout-molecule-desktop-status-modal before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks checkout-molecule-desktop-status-modal-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.