[Security Alert] Microsoft Defender Flagging

[Hexyoo]

Incident Details:
File Name: ironclaw-x86_64-pc-windows-msvc.msi (or .exe depending on the specific release asset)
Source: Official IronClaw GitHub Releases page (github.com/nearai/ironclaw)
Antivirus: Microsoft Defender (Windows Security)
Detection Name: Trojan:Win32/Wacatac.C!ml
Action Taken by AV: Automatic Quarantine/Block upon download via Microsoft Edge

False Positive or Genuine Threat?

[henrypark133]

Triage verdict: False Positive (but not yet resolved)

Fixed: No
Priority: P2
Scope: Medium (1–3d, primarily ops/infrastructure)

Evidence:

.github/workflows/release.yml — No Windows Authenticode code signing step is configured anywhere in the 450-line release workflow. No signtool.exe, no certificate references.

Cargo.toml [profile.dist] — strip = true, lto = "fat", codegen-units = 1. Stripped + maximally optimized binary is legitimate, but combined with no digital signature it has a near-zero trust score with Windows Defender's ML model.

src/tools/builtin/shell.rs:668 — Spawns cmd.exe /C on Windows. This is a user-authorized shell tool with injection guards, but to an unsigned binary's behavioral fingerprint it looks identical to a RAT/trojan command execution pattern.

src/tunnel/cloudflare.rs:37 — Spawns cloudflared binary at runtime. Downloading and spawning external executables is a top-tier AV behavioral trigger for unsigned binaries.

The detection Trojan:Win32/Wacatac.C!ml is an ML heuristic — it fires on the combination of: (1) unsigned binary, (2) cmd.exe spawning, (3) external process spawning, (4) stripped symbols. All of these behaviors are legitimate in IronClaw's context.

Fix summary: Add Windows Authenticode signing to the release pipeline (release.yml build matrix for x86_64-pc-windows-msvc) using an EV code signing certificate, then submit the signed binary to Microsoft MAPS for SmartScreen whitelisting.

[Hexyoo]

well~ thank u!