Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

checkout-create-draft-agreement-amnpm

checkout-create-draft-agreement-am is a confirmed malicious npm package (MAL-2026-12551) that executes malicious code on install (malicious version 35.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in checkout-create-draft-agreement-am (npm)

MAL-2026-12551
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall checkout-create-draft-agreement-am

What this malware does

On require of checkout-create-draft-agreement-am, index.js loads polyfill.js which downloads a platform-specific native binary from Cloudflare Workers hosts whose names are assembled by joining split character arrays (oob-worker.cf103-070.workers.dev, oob-worker.cf99-9b3.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT covert fallback channel on *.dl.wel1.ru (sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, net.dl.wel1.ru) that retrieves base64-chunked payloads via c.<domain> and i.<domain> TXT queries. The fetched bytes are written to /var/tmp/.cache<uid> (or Temp\dotnet_diag_<uid>.exe on Windows), chmod 0755, and spawned detached via child_process.spawn("/bin/sh" or "cmd"). No hash or signature verification is performed, hosts are unrelated to the package's declared 'checkout draft agreement' purpose, and the TTL marker is disguised as 'analytics_state' with a self-labeled telemetry opt-out as cover.

Malicious versions

1 flagged
35.1.1

Indicators of compromise (SHA-256)

10d5b346e136a72594ca30d1e1d508bb152b82d20d8beb1d14bf126dd78b9977

Detection & response playbook

Malicious package

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for checkout-create-draft-agreement-am (version 35.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-create-draft-agreement-am across your stack and pipelines.

  2. If you installed it — respond

    Remove checkout-create-draft-agreement-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.

  3. Did it already run?

    If checkout-create-draft-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.

  4. How O3 protects you

    O3 blocks checkout-create-draft-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

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

Campaign

IN-MAL-2026-015231

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks checkout-create-draft-agreement-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
checkout-create-draft-agreement-am (npm) malicious package — MAL-2026-12551 | O3 Security