NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

checkout-get-installment-client-agreement-amnpm

Advisory published Updated

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)

MAL-2026-12564
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall checkout-get-installment-client-agreement-am

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

1 flagged
35.1.4

Indicators of compromise (SHA-256)

b6c89ae5bb381502715feea1642012fc1c9b388a46746b357a6d8f1348e876c9

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for checkout-get-installment-client-agreement-am (version 35.1.4).

  2. 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.

  3. Did it already run?

    If checkout-get-installment-client-agreement-am was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. checkout-get-installment-client-agreement-am on npm has been identified as a malicious package (version 35.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015215

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
checkout-get-installment-client-agreement-am (npm) malicious package — MAL-2026-12564 | O3 Security