Recovering Encrypted LLM Reasoning Traces
The author describes replaying encrypted LLM reasoning blobs from one OpenAI model to a less capable model to recover underlying reasoning text.
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 author says recovered text was not clearly verbatim and the attack's reliability fluctuated with unknown causes.
One primary source; other links are context, not independent corroboration.
- Primary sourceembracethered.com
- Linked in source“Stealing Reasoning Traces from Proprietary LLM APIs”
- Linked in sourceshowed
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 replaying encrypted LLM reasoning blobs from one OpenAI model to a less capable model to recover underlying reasoning text. Citing a paper and Matthew Green's May 2026 work, the post says providers likely share encryption keys across users, sessions, and models. In the author's tests, recovery worked across sessions and accounts, including a password in one trace. Results were inconsistent: attacks failed for a period and then worked again. The author notes that a scrape of public repositories yielded PII and credentials recovered from reasoning blocks.
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 author says recovered text was not clearly verbatim and the attack's reliability fluctuated with unknown causes.
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 author says recovered text was not clearly verbatim and the attack's reliability fluctuated with unknown causes.
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.
The author replayed an encrypted reasoning blob from one OpenAI model to another model and recovered substantial semantic content.
Source: embracethered.com ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseRecovery worked across separate sessions and accounts in the author's tests, including a known password from a trace.
Source: embracethered.com ↗Stored source-based brief · key point 2 · AINewsIQ paraphraseThe paper reports decoding 315,320 reasoning blocks from public repositories, recovering 367 PII items and 182 credentials.
Source: embracethered.com ↗Stored source-based brief · key point 3 · AINewsIQ paraphraseAttack reliability varied: tests stopped working for a period and later resumed, with no identified cause.
Source: embracethered.com ↗Stored source-based brief · key point 4 · AINewsIQ paraphraseLimits from the stored brief
Source claims not independently checked; the author says recovered text was not clearly verbatim and the attack's reliability fluctuated with unknown causes.
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.
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 author says recovered text was not clearly verbatim and the attack's reliability fluctuated with unknown causes.
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
If encrypted reasoning blobs can be replayed and decoded, session files shared publicly may expose sensitive data, so providers and users should treat these blobs as containing recoverable content.
Limits and open questions
Source claims not independently checked; the author says recovered text was not clearly verbatim and the attack's reliability fluctuated with unknown causes.
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 →