AIPolicyTracker

AI incident ·

National Company Law Tribunal Reportedly Relied on AI-Hallucinated Precedents in Pooja Ramesh Singh v. Jammu and Kashmir Bank Ltd

1 news report Synced from source · record last edited 4 Sep 2026

In brief

An AI system built by Large language model developers and AI research tool developers and deployed by National Company Law Tribunal, Lawyers and 1 other allegedly harmed Pooja Ramesh Singh, Parties to insolvency proceedings and 3 others.

Risk domain
Not classified
Occurred
Coverage
1 reportJul 2026

What happened

In Pooja Ramesh Singh v. Jammu and Kashmir Bank Ltd., India's National Company Law Tribunal (NCLT) reportedly admitted insolvency proceedings against Essel Infraprojects after relying on six purported precedents later found to be fabricated or materially inaccurate. The appellate tribunal upheld the ruling, but the Supreme Court later invalidated both decisions and sent the insolvency petition back to the NCLT for a new ruling.

Editor's notes

Timeline notes: The incident ID date is 08/28/2024, based on the NCLT ruling that relied on purported precedents later identified as AI-generated. On 07/02/2026, the Supreme Court invalidated the tribunal rulings and directed that the insolvency case be reconsidered. The incident ID was created on 07/07/2026.

Laws that address this harm

No recorded instrument yet addresses this use case where it happened. See the open queue.

Matched from the record's risk domain and country to the instruments recorded here. A reviewer can correct the match in the repository (data/external/incident_overrides.yaml).

News reports (1)

Titles link to the original publisher; report text is not reproduced here.

Who was involved

Alleged harmed party
Pooja Ramesh Singh Parties to insolvency proceedings Judicial integrity Essel Infraprojects Ltd Epistemic integrity

AI systems implicated

Large language modelsAI research toolsAI-enabled decision support systems

Classification (MIT AI Risk Repository taxonomy)

Risk domain
—
Risk subdomain
—
Causal entity
—
Intent
—
Timing
—
Harm level
—
Sectors
—
Countries
—

Source record: incident #1573 on the AI Incident Database · all 1 report