GitHub Copilot Chat: From Prompt Injection to Data Exfiltration
The post describes a vulnerability in the GitHub Copilot Chat VS Code extension in which instructions hidden in analyzed source code could cause the LLM to return markdown image links.
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 fix details are as reported by the author, and this brief is based on the supplied blog text only.
One primary source; other links are context, not independent corroboration.
- Primary sourceembracethered.com
- Linked in sourceGitHub Copilot Chat VS Code Extension
- Linked in sourceBing Chat (now Copilot)
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 post describes a vulnerability in the GitHub Copilot Chat VS Code extension in which instructions hidden in analyzed source code could cause the LLM to return markdown image links. Rendering those images automatically sent chat-history data to an attacker-controlled URL as a query parameter. The author reported the issue in February 2024, received confirmation in March, and reports that a fix in June 2024 stopped Copilot Chat from rendering markdown images. The article also recommends allowlisting domains or avoiding image and link rendering, and advises users not to trust LLM output when untrusted content is involved.
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 fix details are as reported by the author, and this brief is based on the supplied blog text only.
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 fix details are as reported by the author, and this brief is based on the supplied blog text only.
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.
Instructions embedded in analyzed source code could make Copilot Chat return markdown image links that exfiltrate chat context.
Source: embracethered.com ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseChat history could be appended to an image URL as a query parameter, sending data to the attacker when the image was rendered.
Source: embracethered.com ↗Stored source-based brief · key point 2 · AINewsIQ paraphraseThe author reported the issue on February 25, 2024 and reports a fix confirmed June 12, 2024.
Source: embracethered.com ↗Stored source-based brief · key point 3 · AINewsIQ paraphraseThe reported fix was that Copilot Chat no longer interprets or renders markdown images.
Source: embracethered.com ↗Stored source-based brief · key point 4 · AINewsIQ paraphraseLimits from the stored brief
Source claims not independently checked; the fix details are as reported by the author, and this brief is based on the supplied blog text only.
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 fix details are as reported by the author, and this brief is based on the supplied blog text only.
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 illustrates how prompt injection in untrusted content can turn rendered LLM output into a data exfiltration channel, a risk relevant to any LLM tool that renders markdown or fetches external resources.
Limits and open questions
Source claims not independently checked; the fix details are as reported by the author, and this brief is based on the supplied blog text only.
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 →