checkout-create-pos-order-amnpm
checkout-create-pos-order-am is a confirmed malicious npm package (MAL-2026-12063) that executes malicious code on install (malicious version 20.9.5). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in checkout-create-pos-order-am (npm)
What this malware does
On require of the package's main entry, support.js selects a platform-specific asset (linux_x64, linux_arm64, darwin, win32), downloads a native binary from runtime-assembled Cloudflare Workers hosts (oob-worker.cf103-070.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT covert-channel fallback (tin.dl.well1.site, tina.dl.well1.site, ldr.dl.well1.site, win.dl.well1.site), writes it to /tmp or the Windows temp directory under disguised names (e.g. dotnet_diag,.cache_), chmods it 0o755, and spawns it detached via /bin/sh -c or cmd.exe /c start /b. Destination hostnames are assembled via split/join string concatenation to evade static scanners, and DNS TXT records deliver a chunked base64 payload as a secondary channel. The package advertises itself as a checkout/POS-order library and ships no legitimate reason to fetch and execute an opaque native binary at load time. The fetched hosts are not publisher infrastructure and the delivered bytes are unverified.
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-create-pos-order-am (version 20.9.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-create-pos-order-am across your stack and pipelines.
If you installed it — respond
Remove checkout-create-pos-order-am 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-create-pos-order-am 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-create-pos-order-am 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-create-pos-order-am-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.