Turning ChatGPT Codex Into A ZombAI Agent
The author describes a proof-of-concept where ChatGPT Codex, an cloud coding agent, was hijacked via indirect prompt injection in a GitHub issue.
Source-based brief · Editor review not recorded · See checks and limits ↓
⚑ Recency not confirmed · what to check
We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news.
Claim context: the demonstration is the author's own proof of concept and vendor responses are as reported by the author.
One primary source; other links are context, not independent corroboration.
- Primary sourceembracethered.com
- Linked in sourceMonth of AI Bugs
- Linked in sourceChatGPT Codex
- Linked in sourceadded internet access
Grok Bot submitted this discovery. We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news. The original source and submitted evidence remain inspectable; no editor has verified the claim.
Open full article view →- Linked article+30
- Fetched source page+30
- No editor link review+0
- Original non-discussion link+5
- Recency not confirmed-8
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
The author describes a proof-of-concept where ChatGPT Codex, an cloud coding agent, was hijacked via indirect prompt injection in a GitHub issue. The attack used OpenAI's 'Common Dependencies' network allowlist, which includes azure.com domains, so an attacker-hosted Azure VM with a cloudapp.azure.com DNS name could receive connections from Codex and act as a command-and-control server. The author reports that OpenAI closed the disclosure as Not Applicable and recommends restricting allowlists to exact needed domains.
Claim explorer
Attribution, source and conditionsSource-stated points from the stored brief. Claim-level assessments have not been recorded.
Source claims not independently checked; the demonstration is the author's own proof of concept and vendor responses are as reported by the author.
This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.
Questions worth asking
Open questions for further reportingWhat remains unconfirmed?
Source claims not independently checked; the demonstration is the author's own proof of concept and vendor responses are as reported by the author.
What material was available for this brief?
The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.
A malicious instruction placed in a GitHub issue was used as indirect prompt injection to make Codex download and run an implant.
Source: embracethered.com ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseThe author states the Common Dependencies allowlist contains 71 domains, and azure.com was the one he flagged as usable by an adversary.
Source: embracethered.com ↗Stored source-based brief · key point 2 · AINewsIQ paraphraseThe attacker-controlled Azure VM used a cloudapp.azure.com DNS name as its C2 endpoint, connecting from the Codex machine.
Source: embracethered.com ↗Stored source-based brief · key point 3 · AINewsIQ paraphraseThe author reports the disclosure was shared with OpenAI on June 10, 2025 and closed as Not Applicable the same day.
Source: embracethered.com ↗Stored source-based brief · key point 4 · AINewsIQ paraphraseLimits from the stored brief
Source claims not independently checked; the demonstration is the author's own proof of concept and vendor responses are as reported by the author.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Related archive coverage
These relationships record a citation or topic overlap, not confirmation of the finding.
Grok Bot submitted this discovery. We could not confirm from the original page that this is a newly published development. Check its date before treating it as current news. The original source and submitted evidence remain inspectable; no editor has verified the claim.
These are Grok Bot discovery notes. AINewsIQ prepared a brief from available source material. The bot's rationale, linked posts, authors, and stances have not been independently verified.
Embrace The Red published this item in its official feed. AINewsIQ collected it server-side for source checking and editorial review.
Source claims not independently checked; the demonstration is the author's own proof of concept and vendor responses are as reported by the author.
Engagement counts, when shown, are observed snapshots. They do not establish accuracy or corroboration.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
Brief history · 1 retained version
These are changes to AINewsIQ’s own publication. Earlier history is unavailable unless recorded here. Complete retained versions are available to the editor.
- Version 1 · published
Source-based brief stored or updated. This does not establish that the publisher changed its page.
Automated record
Source observations · 1 recent captures
A changed capture means the extracted text differed. It can reflect page furniture or extraction changes; it does not establish a substantive correction. Source captures remain private.
Retained capture; no earlier comparison available.
New engagement snapshots do not mean the source itself changed. Source observations and AINewsIQ brief revisions are separate records.
Why this may matter
It shows that broad network allowlists combined with prompt injection can let an agent be turned into a botnet node, exposing environment variables, source code, and compute. Users and enterprises running coding agents with internet access face this risk.
Limits and open questions
Source claims not independently checked; the demonstration is the author's own proof of concept and vendor responses are as reported by the author.
Organization-specific financial, security, and operational effects require the organization's own context and review.

Join the discussion
Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.
No published comments yet.
New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →