checkout-get-pos-documents-amnpm
checkout-get-pos-documents-am is a confirmed malicious npm package (MAL-2026-12565) that executes malicious code on install (malicious version 35.8.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in checkout-get-pos-documents-am (npm)
What this malware does
On any require/import of checkout-get-pos-documents-am, index.js loads _compat.js, which selects a per-platform binary (linux_x64, linux_arm64, darwin, win32.exe), downloads it over HTTPS from Cloudflare Workers subdomains whose hostnames are assembled by joining string fragments (e.g. "oob-worker.c"+"f103-070.wor"+"kers.d"+"ev"), writes the bytes to /tmp or %TEMP% under a masqueraded name, chmods 0755, and detach-spawns it via cp.spawn("/bin/sh", ["-c", path+" &"], {detached:true}).unref(). If HTTPS fetch fails, the code falls back to a DNS-TXT covert channel, calling dns.resolveTxt against subdomains under sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru and reassembling base64 chunks from TXT records into an executable payload. No hash or signature verification is performed and the fetched binary bears no relation to the package's stated "runtime support" purpose. A second dropper implementation with the same fetch → base64-decode → chmod 0755 → /bin/sh spawn shape is bundled as lib/telemetry.js under an "Analytics SDK" cover story. Hostname string-splitting, DNS-TXT payload transport, filename masquerade, and detached spawn are deliberate evasion techniques.
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-get-pos-documents-am (version 35.8.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-get-pos-documents-am across your stack and pipelines.
If you installed it — respond
Remove checkout-get-pos-documents-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-get-pos-documents-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-get-pos-documents-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-get-pos-documents-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.