The developer of RACE, a native macOS terminal multiplexer, says Google restored his advertising account after an unexplained suspension for “malicious software” and a “compromised site.” The reinstatement followed public attention to his account of the dispute, but he said Google still had not explained what triggered the enforcement action.
RACE is written in Rust and lets users arrange terminal windows freely while preserving shell sessions across application restarts. Its website is a static Bridgetown site served through Cloudflare, with downloads stored in Cloudflare R2. The developer said he spent $500 on a Google Ads campaign before the account was suspended.
According to his account, appeals supplied details about the website, download infrastructure and the signed and notarized application. Google rejected the initial challenges without identifying a malicious file, affected page or compromised resource. The developer said Google's Safe Browsing checks for both the main and download domains showed no unsafe content, while Search Console reported no security issues. He correctly noted that those results do not prove the Ads review used the same criteria.
The application itself starts and manages background shell processes, behavior fundamental to a terminal multiplexer but potentially similar to activity monitored by security systems. RACE offers its own persistent pseudo-terminal host, support for the external `dtach` tool, or an option without persistence. The developer suspected that legitimate process management might have produced a false positive, though Google did not confirm that theory.
He also changed the application so a later version would clean up after deletion, then resubmitted it. His published evidence said scans still found no malware. The account was eventually reinstated after the story circulated on Hacker News, according to an update added by the developer. No reason for the original suspension or reversal was provided in the supplied evidence.
The episode highlights a recurring problem for small software vendors that depend on automated platform enforcement. A generic security label may protect users while revealing too little for a legitimate developer to diagnose a false positive. Clean results from adjacent Google security products can deepen that confusion when advertising enforcement offers no specific artifact to remediate.
This account is one developer's documented experience, not an independent audit of RACE or Google's systems. Even so, the unresolved reinstatement leaves the central procedural question intact: how can a software publisher meaningfully appeal a malware classification when the platform does not disclose the item or behavior it believes is unsafe?
