checkout-get-installment-client-agreement-amnpm
checkout-get-installment-client-agreement-am is a confirmed malicious npm package (MAL-2026-12564) that steals credentials and exfiltrates sensitive data (malicious version 35.1.4). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in checkout-get-installment-client-agreement-am (npm)
What this malware does
On require() of the package, init.js detects the host OS and architecture, assembles Cloudflare Workers hostnames from split string fragments (e.g. oob-worker.cf101-adf.workers.dev, oob-worker.cf99-9b3.workers.dev) with a DNS TXT fallback via *.dl.wel1.ru, downloads a platform-specific binary payload, writes it to /var/tmp or %TEMP% under disguised names (dotnet_diag<hex>.exe on Windows,.cache_<hex> on Unix), chmods 0755, and spawns it detached via /bin/sh or cmd.exe. No signature or hash verification is performed. Comments describing the code as telemetry/analytics and referencing opt-out env vars are inconsistent with the disguised filenames, string-split host obfuscation, and DNS-TXT loader fallback. The dropper fires unconditionally on module load.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-get-installment-client-agreement-am (version 35.1.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-get-installment-client-agreement-am across your stack and pipelines.
If you installed it — respond
checkout-get-installment-client-agreement-am is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If checkout-get-installment-client-agreement-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-installment-client-agreement-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-installment-client-agreement-am-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.