Severity minor: The incident was contained to a single court proceeding with routine cleanup—the plaintiff's filing privileges were revoked—and no third party was touched.
Earliest source we hold 2026-09-29
A Connecticut pro se plaintiff hid instructions aimed at a court AI tool inside court filings, attempting to manipulate a court he believed was relying on an artificial intelligence tool to reach decisions. The court caught the attempt, held that the prompt injection attack offended the integrity of the proceedings, and revoked the plaintiff's electronic filing privileges.
Risk grouping: AI attacked
Who caused it
A person or organisation “A Connecticut pro se plaintiff has been caught—and sanctioned for—attempting to manipulate a court he believed was relying on an artificial intelligence tool to reach decisions by hiding instructions directed to the tool in court filings.”source
Intended or not
Intended “A Connecticut pro se plaintiff has been caught—and sanctioned for—attempting to manipulate a court he believed was relying on an artificial intelligence tool to reach decisions by hiding instructions directed to the tool in court filings.”source
The AI's part
Attacked “The court held that the plaintiff’s attempted use of an AI “prompt injection” attack offended the integrity of the proceedings, and revoked the plaintiff’s electronic filing privileges.”source
No source we hold states: before or after release.
The story
1 · What it was doingA Connecticut court was using an AI tool to help reach decisions, and a pro se plaintiff filed documents with it. The plaintiff hid instructions aimed at that tool inside court filings.
2 · What went wrongThe plaintiff tried to manipulate the court's AI tool by embedding instructions in filings, a prompt injection attack that offended the integrity of the proceedings.
3 · What it reached or didThe attempt targeted the court's AI decision tool through the court's electronic filing system; the court caught it and revoked the plaintiff's electronic filing privileges.
4 · How it was caughtThe court caught the plaintiff's attempt and sanctioned him, holding the prompt injection attack offended the integrity of the proceedings.
5 · What was doneThe court sanctioned the plaintiff and revoked his electronic filing privileges. The episode was framed as a cautionary tale about AI security and judicial concerns over AI in legal proceedings.
D inferred by us from the described behaviour, reason shown
Cause
hostile input carried instructions
C one secondary source states it
Who caused it
an outside attacker
C one secondary source states it
Where its input came from
court filings
C one secondary source states it
What was done
The court revoked the plaintiff’s electronic filing privileges.
C one secondary source states it
What went wrong
security breach
C one secondary source states it
AI agent
no AI agent acted
D inferred by us from the described behaviour, reason shown
Impact
Severity
minor
D inferred by us from the described behaviour, reason shown
Why this severity
The incident was contained to a single court proceeding with routine cleanup—the plaintiff's filing privileges were revoked—and no third party was touched.
D inferred by us from the described behaviour, reason shown
Context
Industry
Public Administration
D inferred by us from the described behaviour, reason shown
Country
United States
D inferred by us from the described behaviour, reason shown
LR-2026-0102 · version 3 · published 2026-10-25 after automatic checks; not yet checked field by field by a person · changes to this case · JSON