Which versions of checkout-accounts-logic are malicious?

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

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

checkout-accounts-logic establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If checkout-accounts-logic 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-accounts-logic part of a known attack campaign?

Yes — checkout-accounts-logic is associated with the IN-MAL-2026-015229 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-accounts-logic 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-accounts-logic (version 35.9.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-accounts-logic across your stack and pipelines.

Malicious package

checkout-accounts-logicnpm

checkout-accounts-logic is a confirmed malicious npm package (MAL-2026-12542) that opens a backdoor for remote access (malicious version 35.9.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in checkout-accounts-logic (npm)

MAL-2026-12542

Immediate action

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

npm uninstall checkout-accounts-logic

What this malware does

On require(), the package loads adapter.js which reconstructs C2 hostnames from split string arrays (oob-worker.cf99-9b3.workers.dev, oob-worker.cf103-070.workers.dev, oob-worker.cf102-baf.workers.dev, and *.dl.wel1.ru assembled from ['sdk.d','l.','wel1','.r','u']), fetches a platform-specific binary via https.get, writes it to a temp path with a disguised name (dotnet_diag.exe,.cache_), chmods it 0o755, and detached-spawns it via /bin/sh -c or cmd.exe /c. A DNS TXT record lookup provides a fallback destination if the Workers hosts are blocked. stderr is stubbed to suppress logging. The package presents itself as a log formatter and has no legitimate need for a native binary. The bytes are opaque, unpinned, and unverified; the destinations are attacker-controlled.

Malicious versions

1 flagged

35.9.2

Indicators of compromise (SHA-256)

005b3edb78076f5105de32feda80276d41059215378d6ab90f2d11a332685c6a

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-accounts-logic (version 35.9.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-accounts-logic across your stack and pipelines.
If you installed it — respond
checkout-accounts-logic establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If checkout-accounts-logic 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-accounts-logic 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-accounts-logic on npm has been identified as a malicious package (version 35.9.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015229

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database