GHSA-862f-55f5-vmvwDid you get the swapped OVHcloud CLI?

npx wardlatch@latest --incident ovhcloud-cli-2026-10

It never runs the program. It takes the MD5 of every file called ovhcloud on your PATH and compares it with the five compromised builds OVHcloud published, and it looks in the temp folders for an envchecker- folder followed by digits. It says EXPOSED (with what to do), SAFE, or UNKNOWN when it couldn’t look; on a Mac it skips other accounts’ temp folders, which it can’t open, without a word. It changes nothing and sends nothing.

By hand on a Mac or Linux, in bash or zsh: this prints the MD5 of every ovhcloud on your PATH, beside where it is, without running it.

printf '%s\n' "$PATH" | tr ':' '\n' | while IFS= read -r d; do case $d in "~"/*) d=$HOME/${d#"~"/} ;; /*) ;; *) continue ;; esac; if [ -f "$d/ovhcloud" ]; then if command -v md5sum >/dev/null 2>&1; then md5sum "$d/ovhcloud"; else md5 -r "$d/ovhcloud"; fi; fi; done

Then the temp folders:

command ls -a /tmp "${TMPDIR:-/tmp}" | grep -E '^envchecker-[0-9]+$'

On Windows, in PowerShell: Get-FileHash -Algorithm MD5 (Get-Command ovhcloud).Source prints the fingerprint, and Get-ChildItem $env:TEMP -Filter 'envchecker-*' looks for the trace. Wardlatch doesn’t run on Windows yet.

Exposed

An MD5 in the list below, or any envchecker- folder: don’t run the program again, and follow section C.

Not these

An MD5 not in the list, and no envchecker- folder.

Nothing

No lines from the fingerprint check: no ovhcloud on your PATH. A copy you keep elsewhere isn’t found: run md5sum (Linux) or md5 -r (Mac) on its path.

• The five compromised builds, by MD5 (OVHcloud’s advisory): macOS Apple silicon 6f2f086239f3d88eb2750e871901927d, macOS Intel 347e65eb7f2d78d1c6872690272a6cc3, Linux ARM64 01f57206d37c28cf711677f612052913, Linux x86-64 301bff0b51980b9e76c93633e7cfd3bd, Windows x86-64 (ovhcloud.exe) 6a3cf153338c416169cda2fe704c8848.

1. Don’t run it. Delete the ovhcloud program, and install 0.16.0 or later.
2. Revoke and replace the secrets the stealer could copy from this machine: cloud keys for AWS, Google Cloud, Azure and DigitalOcean; SSH keys; Kubernetes, Docker, npm and Terraform credentials; .netrc and git credentials. OVHcloud’s advisory lists everything it took.
3. Treat the histories of the AI coding tools on the machine (Claude, Cursor, VS Code, Continue, Cody, OpenCode) as read.
4. Updating doesn’t revoke a key that was already copied: replace the keys even after you install 0.16.0.

• Copies on your PATH only. A copy kept in another folder isn’t hashed; check it by hand.
• The trace is one half. OVHcloud says an envchecker- folder means exposure; it doesn’t say that no folder proves the stealer never ran. Check the fingerprint too.
• Your own temp folders. On a Mac, Wardlatch looks for the trace only in the temp folders it can open, not in other accounts’: run it as the account that ran the program.
• macOS and Linux. Windows is not supported yet; use the PowerShell lines above.

This page describes Wardlatch 0.1.9 and its incident file, ovhcloud-cli-2026-10.json.

1. OVHcloud, GHSA-862f-55f5-vmvw, published 2026-10-20: the affected versions and window (14:47 to 16:21 UTC+2, 2026-10-19); about 250 downloads; the five MD5s; the envchecker- folder; 0.16.0 clean, published from a signed tag; rotate the secrets, delete the binaries, reinstall.
2. Wardlatch 0.1.9, ovhcloud-cli-2026-10.json and README: what it checks, and the secrets to replace.

Credits · OVHcloud credits alink-tothepast, who reported the suspicious release through a GitHub issue, and thanks Ivan Kwiatkowski and the VirLabs.ai malware analysis platform (the advisory links no profile for him, so the link is to VirLabs.ai). All sources read 2026-10-25.