A controlled study tested fake reasoning markers in direct secret disclosure and in malicious text embedded in agent-read documents. Entry and authority. Attackers could submit messages or alter a document that the agent was legitimately reading; simulated private financial records and effect checkpoints were in the evaluation. Observed mechanism and…
Inspect the ClaimsCase · DiggingBeagle record
Forged reasoning tags changed model disclosure and agent tool actions
A controlled study tested fake reasoning markers in direct secret disclosure and in malicious text embedded in agent-read documents.
Public disclosure: Nov 6, 2026
Attackers could submit messages or alter a document that the agent was legitimately reading; simulated private financial records and effect checkpoints were in the evaluation. Constructed reasoning-style strings were evaluated for their ability to shift a model from authorized summarization into unapproved disclosure or tool actions.
Assessment profile
Assessment method- Setting
- evaluation
- Exploitation
- demonstrated
- Evidence
- Grade C
- Remediation
- not applicable
- AI role
- AGAINST AI
Basis and provenance
Primary paper reports two controlled experiments: synthetic-record disclosure and actual containerized tool effects under a poisoned document. No field victim or universal effectiveness estimate.
Assessed Nov 11, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-DB233-THOUGHT-INJECT-01 · CLM-DB233-THOUGHT-INJECT-02 · CLM-R236-THOUGHT-629-6000 · CLM-R236-THOUGHT-50-PERCENT · I Think, Therefore I Attack: Evaluating Thought Injection Attacks on Reasoning Agents
At a glance
The tested data and execution environment were controlled; no customer breach or universal effectiveness rate is implied. Model-specific tag/voice effects may not transfer across versions or production deployments; all reported disclosure and shell/backdoor effects were in a controlled range. Whether any independent execution-policy layer, beyond tag…
Limits and uncertaintyFull account
A controlled study tested fake reasoning markers in direct secret disclosure and in malicious text embedded in agent-read documents.
Entry and authority. Attackers could submit messages or alter a document that the agent was legitimately reading; simulated private financial records and effect checkpoints were in the evaluation.
Observed mechanism and consequence. Constructed reasoning-style strings were evaluated for their ability to shift a model from authorized summarization into unapproved disclosure or tool actions.
Limits and status. The tested data and execution environment were controlled; no customer breach or universal effectiveness rate is implied.
The thought-injection study used strings imitating model reasoning to change behavior in two separate settings: disclosure of synthetic records placed in high-trust context and tool use after reading a manipulated document. Its controlled results varied substantially by model and whether the injected material resembled that model's own reasoning format. The test does not show a universal exploit of private reasoning channels in commercial products.
Measured outcomes. Study 1 used 150 synthetic financial customer records placed in protected context, 25 attack vectors with variations across three models and tags, yielding 629 disclosure runs out of 6,000. Among those 629, 67.7% leaked only in final answers, 20.8% only in reasoning and 11.4% in both, which is a distribution of already-leaking runs, not a separate success rate. Study 2 placed attacker-authored text in a document the agent had a legitimate reason to summarize. In 50 runs per condition, MiniMax-M2.5 acting on forged own-voice reasoning with tags reached a controlled listener and exposed synthetic secrets in 42%, or pushed a modified backdoor to a test Git repository in 50%; untagged versions fell to 8% and 10%, while ordinary user-style malicious instructions scored zero in these tested cells. The tests do not establish equivalent behavior across all deployed reasoning models or actual stolen financial records.
The first experiment tested whether fabricated reasoning tags could elicit records placed in a synthetic system message. The second changed the attacker-controlled surface: a document the defender was legitimately summarizing carried prose styled as the model's own internal reasoning. The second experiment measured downstream tool effects, not just whether a response reproduced hostile instructions.
These results isolate a practical trust error. A tag or apparent thought is still source material when it comes from a user document. Stripping visible thinking markers alone is not a complete control because the paper found model-specific behavior and some effective untagged payloads. A host-side check must bind each outbound connection, repository push or secret read to the original authorized task and current principal. Neither the 629/6,000 disclosure measurement nor the 50% Git result is a production incident rate.
Mechanism and trust boundary
- 01
Precondition and trust context
Attackers could submit messages or alter a document that the agent was legitimately reading; simulated private financial records and effect checkpoints were in the evaluation.
- 02
Crossed boundary
Constructed reasoning-style strings were evaluated for their ability to shift a model from authorized summarization into unapproved disclosure or tool actions.
- 03
Observed limit
The tested data and execution environment were controlled; no customer breach or universal effectiveness rate is implied.
Timeline
- Nov 6, 2026Event type unspecified
Initial documented finding
Forged reasoning tags changed model disclosure and agent tool actions
- Nov 6, 2026disclosure
Public disclosure
Claims & evidence
CLM-R236-THOUGHT-629-6000Study 1 recorded 629 disclosure runs among 6,000 synthetic tests; of leaking runs, 67.7% exposed data in the final response alone, 20.8% in reasoning alone and 11.4% in both.supported
Basis: reported finding
- supportsI Think, Therefore I Attack: Evaluating Thought Injection Attacks on Reasoning Agentsprimary disclosure
Study 1 Results: Table II and Location Table III
CLM-DB233-THOUGHT-INJECT-01The paper evaluates both direct private-record leakage and indirect model-specific attacks against tool-using agents.supported
Basis: reported finding
- supportsI Think, Therefore I Attack: Evaluating Thought Injection Attacks on Reasoning Agentsprimary disclosure
Study 1 and Study 2 experimental design
CLM-DB233-THOUGHT-INJECT-02The controlled tests compared tagged and untagged payloads and model-specific reasoning impersonation.supported
Basis: reported finding
- supportsI Think, Therefore I Attack: Evaluating Thought Injection Attacks on Reasoning Agentsprimary disclosure
Study 1 Results and Study 2 Results
CLM-R236-THOUGHT-50-PERCENTIn Study 2, MiniMax-M2.5 with own-voice tagged reasoning-style injection achieved 42% reverse-shell and 50% Git backdoor success across 50 trials per condition; the corresponding plain user-style malicious text achieved 0%.supported
Basis: reported finding
- supportsI Think, Therefore I Attack: Evaluating Thought Injection Attacks on Reasoning Agentsprimary disclosure
Study 2 Results: Table IV and evaluation design
Controls and mitigations
- Treat externally supplied reasoning-like tags and model-output formatting as untrusted content, not as hidden or privileged computation.
- Enforce tool permissions outside the model and test model-specific fake reasoning against both final answers and actual tool effects.
Unknowns and contradictions
- The tested data and execution environment were controlled; no customer breach or universal effectiveness rate is implied.
- Model-specific tag/voice effects may not transfer across versions or production deployments; all reported disclosure and shell/backdoor effects were in a controlled range.
- Whether any independent execution-policy layer, beyond tag removal or model refusal, would prevent the specific tested Git-push or listener effect while preserving the legitimate document-summary task.
Sources and citation
Material revision history
- Nov 10, 2026 · Published version · first publication · revision 235
- Nov 11, 2026 · Published version · material revision · revision 238Public fields changed: assessment_profile, claims, narrative, unknowns