AINewsIQ by Triuna Labs
Menu
SOURCE-LINKED SIGNAL / ARTICLE / SECURITY

ChatGPT: Hacking Memories with Prompt Injection

The author describes how ChatGPT's memory feature, which stores information across sessions and is on by default, can be manipulated through indirect prompt injection.

READ THE ORIGINAL SOURCEOpen original sourceembracethered.com UTC

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 attack reproduction was reported by the author and the techniques worked only intermittently.

Recorded links

One primary source; other links are context, not independent corroboration.

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 →
How this score was derived
  • 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 how ChatGPT's memory feature, which stores information across sessions and is on by default, can be manipulated through indirect prompt injection. Three attack avenues are explored: Connected Apps (Google Docs referenced in a chat), uploaded images, and browsing. In the Connected Apps scenario, instructions in a referenced document caused ChatGPT to store memories and could also delete existing ones. The author reports the browsing vector was partly mitigated, though bypassable, and that OpenAI closed the disclosure as a model safety issue rather than a security vulnerability.

Claim explorer

Attribution, source and conditions

Source-stated points from the stored brief. Claim-level assessments have not been recorded.

A Google Doc referenced via Connected Apps contained prompt injection text that caused ChatGPT to write memories,…
Source assertionNot independently checked
Primary sourceembracethered.comInspect source ↗
Attributed toClaimant not recorded per pointSource assertion
Conditions / limitsClaim-specific conditions not recorded. Read the source and limits below.

Source claims not independently checked; the attack reproduction was reported by the author and the techniques worked only intermittently.

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 reporting
What remains unconfirmed?

Source claims not independently checked; the attack reproduction was reported by the author and the techniques worked only intermittently.

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.

Limits from the stored brief

Source claims not independently checked; the attack reproduction was reported by the author and the techniques worked only intermittently.

This is a source-based abstract, not independent validation of the source's claims.

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.

Checking sign-in…

New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →