ProductsCulture OpenAIGoogle

A sponsored Google result for OpenAI Codex led a developer to a Mac infostealer

Illustration for the fake Codex install ad infostealer story

A developer searched Google for OpenAI Codex, ran the install command from the first result, and then spent the day working out what had already been copied off their Mac.

How the attack worked

The developer described the incident on r/OpenAI on August 17. The top search result was a sponsored ad that appeared to point at a Google URL and led to a fake installation page hosted on Google Pages. The command on that page was built to pass a casual glance: an echo that printed a legitimate-looking npm line and an openai.com address, followed by a curl that fetched a base64-encoded URL and piped whatever that server returned straight into zsh. The payload host had nothing to do with OpenAI.

Afterwards, the developer found no rogue LaunchAgents, no modified shell profiles and no persistent process. That absence leaves the worst case open rather than closed. It is consistent with a one-shot infostealer, a script that copies browser passwords and cookies, keychain items, SSH keys and API tokens, uploads them and exits, leaving nothing behind to find.

Not an isolated page

This is a pattern, not a one-off. Kaspersky flagged the same technique in March 2026: sponsored search ads leading to pages that copy official install documentation. Security firm Straiker has since tracked 88 domains across at least ten hosting platforms, 32 of them still live in mid-May, impersonating Claude Code, JetBrains and NotebookLM among other developer tools.

The targets are telling. These are not consumer brands; they are tools whose install instructions consist of a single long shell command that users paste into a terminal without reading to the end. Developer tooling has quietly become prime phishing real estate for exactly that reason.

Why no vulnerability was needed

The attack exploits nothing in Codex, nothing in macOS and nothing in the browser. It needs three ordinary things: a search ad, a page that looks like documentation, and the habit of trusting the first result. Each of those is a feature of how the web and developer workflows normally operate, which is why the technique keeps reappearing across hosting platforms and brand names.

The blast radius is what makes it serious. Anything the developer has ever authenticated in that terminal is in scope, from SSH keys to the API tokens for the very AI services the fake page was impersonating. The practical defense is unglamorous. A command that starts with a familiar name is not a command you have read, and an install line that fetches and executes remote content deserves to be read to the last character before it runs.

Sources

ANOTHER News is published by ANOTHER, an AI-native content agency. Daily coverage also runs on Instagram.