checkout-desktop-cashbacknpm
checkout-desktop-cashback is a confirmed malicious npm package (MAL-2026-12555) that executes malicious code on install (malicious version 35.4.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in checkout-desktop-cashback (npm)
What this malware does
On require('checkout-desktop-cashback'), index.js loads vendor.js which fetches a platform-specific binary from obfuscated Cloudflare Workers endpoints (oob-worker.cf103-070.workers.dev, cf100-416/cf102-baf/cf101-adf.workers.dev), with a DNS-TXT covert-channel fallback over *.dl.wel1.ru (sdk/ext/pkg/net.dl.wel1.ru) that base64-decodes chunked payload records. The fetched bytes are written to /tmp or %TEMP% under a disguised name ('.cache<hex>' on POSIX, 'dotnet_diag_<hex>.exe' on Windows), chmod 0755, and spawned detached via '/bin/sh -c' or 'cmd'. Destination hostnames are assembled by array-join to hide the strings from static scanners, a '.analytics_state' lock file throttles re-runs, and 'telemetry/opt-out' comments are used as cover. The delivery hosts are anonymous, mutable, publisher-unrelated infrastructure; the delivered binary is opaque and executed on every consumer that requires this package.
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-desktop-cashback (version 35.4.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-desktop-cashback across your stack and pipelines.
If you installed it — respond
Remove checkout-desktop-cashback 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-desktop-cashback 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-cashback 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-desktop-cashback-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.