What does the checkout-desktop-accounts malware do?

The package's main entry unconditionally requires./_loader on load. _loader.js reconstructs C2 hostnames from string fragments (oob-worker.cf*.workers.dev) and, on failure, reassembles a base64 payload from DNS TXT records under c. and N. on dl.wel1.ru. It downloads a platform-specific binary over HTTPS, writes it to /var/tmp/.cache_ or %TEMP%/dotnet_diag_ .exe (a name mimicking a Microsoft diagnostics tool), chmods 755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. A hidden stamp file (.analytics_state) is written to gate re-execution, and DO_NOT_TRACK/DISABLE_TELEMETRY env vars are honored to present a cooperative telemetry facade over the covert na

Which versions of checkout-desktop-accounts are malicious?

The following npm versions of checkout-desktop-accounts are flagged malicious: 35.7.4. Treat any of these as compromised.

How do I remediate checkout-desktop-accounts if I installed it?

checkout-desktop-accounts is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed checkout-desktop-accounts — how do I know if it already compromised me?

If checkout-desktop-accounts 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.

Is checkout-desktop-accounts part of a known attack campaign?

Yes — checkout-desktop-accounts is associated with the IN-MAL-2026-015225 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find checkout-desktop-accounts across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-desktop-accounts (version 35.7.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-desktop-accounts across your stack and pipelines.

Malicious package

checkout-desktop-accountsnpm

checkout-desktop-accounts is a confirmed malicious npm package (MAL-2026-12553) that steals credentials and exfiltrates sensitive data (malicious version 35.7.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in checkout-desktop-accounts (npm)

MAL-2026-12553

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall checkout-desktop-accounts

What this malware does

The package's main entry unconditionally requires./loader on load. loader.js reconstructs C2 hostnames from string fragments (oob-worker.cf*.workers.dev) and, on failure, reassembles a base64 payload from DNS TXT records under c.<domain> and N.<domain> on dl.wel1.ru. It downloads a platform-specific binary over HTTPS, writes it to /var/tmp/.cache<hex> or %TEMP%/dotnet_diag<hex>.exe (a name mimicking a Microsoft diagnostics tool), chmods 755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. A hidden stamp file (.analytics_state) is written to gate re-execution, and DO_NOT_TRACK/DISABLE_TELEMETRY env vars are honored to present a cooperative telemetry facade over the covert native payload. The runtime-assembled hostnames, DNS-TXT covert channel, disguised filename, TMP-staging, chmod+x, and detached spawn together form an unambiguous remote-code-execution dropper triggered on any require of the package.

Malicious versions

1 flagged

35.7.4

Indicators of compromise (SHA-256)

2d5571b1ecfcbc9597cee92fc50abf9c5b373ba20b62038ab0623adc05eb726b

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-desktop-accounts (version 35.7.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-desktop-accounts across your stack and pipelines.
If you installed it — respond
checkout-desktop-accounts is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If checkout-desktop-accounts 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-desktop-accounts 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

No. checkout-desktop-accounts on npm has been identified as a malicious package (version 35.7.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015225

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks checkout-desktop-accounts-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database