checkout-use-disable-interactionnpm
checkout-use-disable-interaction is a confirmed malicious npm package (MAL-2026-12601) that executes malicious code on install (malicious version 35.4.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in checkout-use-disable-interaction (npm)
What this malware does
On require() of checkout-use-disable-interaction, index.js loads vendor.js which downloads a platform-specific native binary from Cloudflare Workers subdomains under oob-worker.cf*.workers.dev, with a DNS TXT-record fallback channel at c.<domain> and 0.<domain>..N.<domain> under *.dl.wel1.ru whose base64-decoded fragments are concatenated into the same executable payload. Destination hostnames are assembled at runtime by string-splitting and array-join to evade static analysis. The payload is written to /var/tmp/.cache<uid> on Linux/macOS or %TEMP%\dotnet_diag_<uid>.exe on Windows — cover-story filenames designed to blend with system artifacts — then chmod 0755 and spawned detached via /bin/sh -c '<path> &' or cmd /c start /b. A /tmp/.analytics_state (or %TEMP%\analytics_state) marker file is written and its mtime used as a ~6h re-run gate so the dropper re-fires periodically whenever any consumer imports the package. The package README advertises a benign microservice module; the shipped code does not match that purpose.
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-use-disable-interaction (version 35.4.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging checkout-use-disable-interaction across your stack and pipelines.
If you installed it — respond
Remove checkout-use-disable-interaction 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-use-disable-interaction 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-use-disable-interaction 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-use-disable-interaction-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.