checkout-resend-pos-order-sms-amnpm
checkout-resend-pos-order-sms-am is a confirmed malicious npm package (MAL-2026-12590) that executes malicious code on install (malicious version 35.3.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in checkout-resend-pos-order-sms-am (npm)
What this malware does
On require() of this package, index.js loads polyfill.js which reconstructs attacker-controlled hostnames via array-join concatenation (e.g. 'oob-worker.cf10x-*.workers.dev' variants) and issues an https.get to download a platform-specific executable. The bytes are written to /var/tmp/.cache<rnd> on Unix or %TEMP%\dotnet_diag_<rnd>.exe on Windows, chmodded to 0755, and spawned detached via spawn('/bin/sh', ['-c', <path> + ' &']) or the Windows equivalent. A DNS-TXT base64-chunk fallback via .dl.wel1.ru resolvers is used when direct HTTPS fetch fails. The child_process module reference and 'chmodSync' string are also concatenated at runtime ('child_'+'process', 'chmod'+'Sync') to defeat static string matching. A sibling module lib/telemetry.js contains the same fetch/chmod-0755/sh-c-spawn dropper pattern, indicating shared payload infrastructure. The package's stated purpose (an SMS/POS order helper) is unrelated to downloading and executing native binaries from Cloudflare Workers subdomains, and the disguised on-disk filenames (.cache_, dotnet_diag_*.exe) further indicate concealment rather than legitimate runtime setup.
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-resend-pos-order-sms-am (version 35.3.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-resend-pos-order-sms-am across your stack and pipelines.
If you installed it — respond
Remove checkout-resend-pos-order-sms-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-resend-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-resend-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-resend-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.