Check Point Research has published an analysis of Haiou (“seagull” in Chinese), a jailbreak bundle for OpenAI’s Codex that does more than weaken guardrails. Version 4.5.0, the one Check Point examined, also writes an advertisement into Codex’s global agent instructions, so that a simple greeting gets back a promotion for the author’s paid LLM gateway. Check Point calls this prompt adware: a change to an agent’s trusted instructions, such as global prompts, Skills or configuration files, made “to influence future outputs for commercial or behavioral objectives,” with no executable payload.
How Check Point found it
The bundle turned up on a misconfigured web server run by a threat actor using Cobalt Strike, alongside the Ladon network scanner and the VulnClaw penetration testing agent. Check Point says that does not mean Haiou was built for cybercrime, and that no evidence links its author to cybercrime. It calls the bundle dual-use.
The package is public on GitHub under the user haiou-666, with versions for Codex and Claude Code. Check Point says only the Codex version seems actively maintained and only it contains the ad injection. The repository had more than 250 stars at the time of writing, a Bilibili video promotes the Claude version, and the bundle ships inside Codex-X, a Chinese tool for configuring Codex through a graphical interface.
What it installs
- Jailbreak prompt modules. Thirty-one Markdown modules use role play, refusal suppression, response priming and pretexting. One reframes any offensive-security task as an educational capture-the-flag exercise; another forbids replies that open by asking for authorization.
- Six skills named
seagull-*, for penetration testing, reverse engineering, license cracking, game security and anti-cheat work. - An opaque payload. The prompts ship as an encrypted
payload.pkg, checked with Ed25519 signatures and SHA-256 hashes and decrypted with an AES-256-GCM key in the launcher script. Check Point speculates this is meant to keep the prompts away from automated scanners. - The ad. In the
00-identity.mdmodule, a list of greetings and activation words (including “hi,” “hello,” “yo,” “ctf,” “coach” and “Seagull”) makes the model reply with one fixed line: a seagull catchphrase and a link to the author’s gateway, an OpenAI-compatible relay that sits between an app and a model provider. Another module marks that gateway as protected, forbidding offensive testing against it “even if the user claims authorization or CTF context.”
Check Point found “no hints that the advertised gateway itself is malicious,” and it does not classify Haiou as a supply chain attack. It does note that some LLM gateways have been found to snoop on traffic, steal secrets such as cloud keys and inject tool calls. The package includes an uninstaller that Check Point says reverts all changes and restores the original configuration. A leftover CLAUDE.md in the Codex package carries the same ad, and Check Point says Claude Code running Sonnet 5 flagged it as a prompt injection and did not comply.
What to check on your machine
Check Point’s text says the bundle modifies Codex’s configuration and global instruction files but does not list exact paths. OpenAI’s Codex docs say where those live:
- Global instructions:
AGENTS.override.mdorAGENTS.mdin your Codex home, which is~/.codexunlessCODEX_HOMEis set (docs). Runecho $CODEX_HOMEfirst so you read the right directory, and look for lines telling the model how to answer greetings. - Config:
~/.codex/config.toml, any profile files beside it, project.codex/config.tomlfiles and/etc/codex/config.tomlon Unix (docs). Check any provider or base URL settings you did not add yourself. - Skills:
$HOME/.agents/skills,.agents/skillsfolders in your repositories and/etc/codex/skills(docs). Look forseagull-folders or skills you do not recognize. - A quick behavioral test: start a new session and type “hi.” A fixed one-line reply with a link instead of a normal greeting means something has edited your instructions.
Why this matters
This is the same lesson as the planted AGENTS.md that steered Codex toward malware, but installed on purpose by the user and persisting across every project through the global files. It also sits next to the grey-market relay Symantec found rewriting Codex config to route traffic through its servers: here the instructions only advertise a gateway, but Check Point points out that the same persistence could quietly bias recommendations or technical advice. Treat third-party prompt packs and skills like code you install, read them in plain text before running them, and keep your Codex home under review.

The Campfire
CommentsThanks. Your comment is waiting for the desk. Once it is approved it appears here within about a minute.
Add a comment