Which versions of checkout-total-logic are malicious?

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

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

Remove checkout-total-logic 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.

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

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

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

Malicious package

checkout-total-logicnpm

checkout-total-logic is a confirmed malicious npm package (MAL-2026-12598) that executes malicious code on install (malicious version 35.8.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in checkout-total-logic (npm)

MAL-2026-12598

Immediate action

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

npm uninstall checkout-total-logic

What this malware does

On require of the package, index.js loads platform.js, which reconstructs endpoint hostnames from split string fragments resolving to oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev, and oob-worker.cf102-baf.workers.dev, with a DNS TXT-record chunked-base64 fallback channel over .dl.wel1.ru. platform.js:74 issues https.get to those hosts, writes the returned platform-specific binary to a temp path using decoy filenames (dotnet_diag.exe,.cache*), chmods it 0o755 on Unix, and detached-spawns it via cp.spawn('/bin/sh',['-c',fp+' &'],{detached:true}) on Unix or spawn('cmd',...) on Windows. There is no hash or signature verification, the destination hosts are not publisher-associated, and the package presents itself as a trivial log transport, contradicting the fetch-and-execute behavior. A cooldown flag is dropped in /tmp. The result is unauthenticated remote code execution on any developer or CI host that installs and requires this package.

Malicious versions

1 flagged

35.8.3

Indicators of compromise (SHA-256)

297980540b58c9daf802d92602f2a809348bd6ac1492537d6e291f704702dc0a

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-total-logic (version 35.8.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-total-logic across your stack and pipelines.
If you installed it — respond
Remove checkout-total-logic 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-total-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-total-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-total-logic on npm has been identified as a malicious package (version 35.8.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015154

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks checkout-total-logic-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database