checkout-confirm-pos-order-sms-amnpm
checkout-confirm-pos-order-sms-am is a confirmed malicious npm package (MAL-2026-12549) that typosquats a legitimate package to trick installs (malicious version 35.6.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in checkout-confirm-pos-order-sms-am (npm)
What this malware does
On require() of this package, index.js loads _init.js which invokes init() immediately. init() downloads an opaque binary from hardcoded Cloudflare Workers endpoints (oob-worker.cf99-9b3.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) whose hostnames are reconstructed at runtime via split-join of small string fragments to evade static scanners. A DNS-TXT fallback reassembles the payload from base64 chunks served under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The downloaded bytes are written to /tmp or %TEMP% under a disguised name (.cache_<hex> on Unix or dotnet_diag_<hex>.exe on Windows mimicking a.NET diagnostic tool), chmod 0755 on Unix, and spawned detached via /bin/sh -c '<path> &' or cmd.exe; the spawn is unref()'d so it outlives the Node process. Execution is throttled by a /tmp cooldown file. The tarball also ships lib/telemetry.js (~81 KB, framed with 'Analytics SDK' comments) containing an equivalent dropper: split require('child_'+'process'), base64 chunk assembly, fs['chmod'+'Sync'](path, 0o755), and cp.spawn('/bin/sh', ['-c', filePath+' &']). The require('child_process'), fs.chmodSync, and spawn identifiers are string-split throughout to hide from keyword scanners. Package name lookalike of a checkout/POS SMS confirmation utility. Installing or requiring this package executes attacker-controlled native code on the installer's machine.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-confirm-pos-order-sms-am (version 35.6.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-confirm-pos-order-sms-am across your stack and pipelines.
If you installed it — respond
checkout-confirm-pos-order-sms-am is a typosquat — you almost certainly intended a legitimately-named package. Remove checkout-confirm-pos-order-sms-am, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If checkout-confirm-pos-order-sms-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-confirm-pos-order-sms-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-confirm-pos-order-sms-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.