Skip to content

Risk Digest

Robert Shiver murder case exposes two AI dangers

The Robert Shiver murder-for-hire case and a Georgia prosecutor's AI-citation sanction bookend two distinct AI risks in criminal litigation: AI-generated content that fabricates case facts, and attorneys' own AI-generated filings that fabricate legal citations. This item documents both incidents and the shared verification duty they trigger.

By Editorial TeamUpdated Jul 27, 2026Verified Jul 27, 2026
CONFIRMED
Jurisdiction
Georgia
Court
Georgia Supreme Court
Judge
Justice Benjamin Land
AI tool named
Generative AI
Ruling date
May 5, 2026
Source document
View primary court order ↗
Last verified
Jul 27, 2026

Lex Machina Review is an independent risk-tracking and reference resource. Nothing on this site is legal advice, and using it does not create an attorney-client relationship. Every record is reviewed against primary sources but may not reflect the most current status of a matter — always verify directly against the cited court order, rule text, or a licensed attorney before relying on it.

Companion explanation — secondary to the source document above

A search for “robert shiver murder plot charges” should not lead with the premise that Robert Shiver was murdered. Yet in June 2026, an Apple Podcasts listing appeared for a 38-minute AI true-crime episode titled “The Murder of Robert Shiver,” published by “AI See What You Did There - True Crime.” The available source posture is narrow but important: the listing metadata confirms the title, the publication date, the show name, and the episode’s framing; the full transcript was not retrievable, so the generated narrative cannot responsibly be quoted in detail here.[1]

That limitation does not make the error harmless. Robert Shiver is alive. In the Bahamas criminal case involving Lindsay Shiver, he is the alleged target of a murder-for-hire plot, not the deceased victim. As of July 27, 2026, the case remained active, with reported procedural movement including bail revocation, trial-delay history, and a motion to dismiss set for hearing on July 31, 2026.[2]

Illustration of false podcast content and hallucinated legal citations converging on a courthouse

The point is not that an AI podcast decides a criminal case. It does not. The point is more prosaic and more useful to lawyers: once a false AI-generated case narrative is in public circulation, someone has to decide whether to preserve it, correct it, move against it, ignore it, or prepare for it to appear in voir dire, witness conversations, client communications, or a later motion record.

The Shiver hallucination is an external contamination problem

The Shiver podcast incident sits outside the courthouse. That is why it can be dismissed too quickly. It is not a filing. It is not testimony. It is not evidence. It is not, on the available record, attributable to either side in the Bahamas prosecution.

But an active criminal case does not exist only in pleadings. Jurors, witnesses, family members, investigators, and clients consume public narratives long before a lawyer can test them in court. A false title that turns an alleged target into a murder victim changes the elementary posture of the case. It also creates an avoidable housekeeping burden: if the error is later mentioned by a prospective juror, repeated by a witness, or cited in a media summary, the parties need to know when it appeared, what it said, where it was hosted, and whether it was still available.

The first professional response is preservation, not outrage. Capture the listing, date, platform, show name, title, duration, description, URL, and any available audio. Note what was not available. If the transcript cannot be retrieved, say so. If only metadata is confirmed, do not paraphrase imagined dialogue from the episode as though it were sourced. That is the difference between documenting contamination and adding a second layer of it.

For defense counsel, the immediate concern is juror-pool confusion and client prejudice. For prosecutors, it is separating public rumor from admissible proof and preventing witnesses from absorbing a false version of the case. For both sides, the question is whether the item needs to be addressed through monitoring, a platform request, a motion, a proposed voir dire topic, a limiting instruction, or simply a preserved file note. The answer will depend on reach, timing, local procedure, and whether the false content can be tied to any concrete litigation consequence.

The Payne sanction shows the risk coming from inside the filing

The Georgia Supreme Court’s May 5, 2026 discipline of Clayton County prosecutor Deborah Leslie is a different species of AI failure. In the Hannah Payne murder case, the error was not an outside podcast misdescribing a prosecution. It was AI-generated legal fiction entering a criminal filing through counsel’s own work product.

Reuters reported that Leslie filed AI-generated fake citations in Payne’s murder appeal. Payne had been sentenced to life plus 13 years. The Georgia Supreme Court barred Leslie from appearing for six months, ordered ethics and AI continuing legal education, and vacated the lower court’s denial of a new trial. Justice Benjamin Land wrote that “citing cases that do not exist … falls far beneath the conduct we expect from Georgia lawyers.”[3]

That sanction matters because it identifies the failure at the right level. The problem is not that a lawyer touched an AI tool. The problem is that nonexistent authority was allowed to travel from a generated draft into a criminal case filing. Once that happened, the burden shifted to the court, opposing counsel, and ultimately the defendant’s appellate posture. A fake citation is not a typo when it purports to tell a court what the law is.

This is why the Shiver podcast and the Payne sanction should not be flattened into one generic “AI is dangerous” story. They are factually independent. They involve different jurisdictions, different tools, different actors, and different points of entry. Their usefulness is analytical: they bookend the two directions from which AI error now enters criminal litigation. In one, fabricated case content approaches the courthouse from the public sphere. In the other, fabricated authority leaves a lawyer’s workflow and lands on the court’s desk.

The broader hallucination record is now large enough to remove the novelty defense

The Payne sanction is not an isolated oddity in the legal profession’s AI record. Damien Charlotin’s AI Hallucination Cases database tracked more than 1,782 global cases as of July 18, 2026, including 53 criminal cases. The database also reflects a disciplinary spectrum that has moved beyond mild correction, with consequences described across tracked matters ranging from admonishments to bar referrals and indefinite suspension.[4]

Those numbers should be handled carefully. A tracker count is not an effectiveness study, and it does not measure how often lawyers use AI responsibly. It does, however, defeat the argument that fabricated legal citations are a surprise failure mode. By Q3 2026, the risk is known, documented, and professionally foreseeable.

Formal Opinion 512 leaves verification with the lawyer

ABA Formal Opinion 512, issued in July 2024, places generative AI use inside ordinary professional duties rather than outside them. Its practical instruction is straightforward: lawyers using generative AI must understand the relevant risks and verify AI-generated content before relying on it. That duty belongs to the lawyer; it is not delegated to the model, the vendor, the software, or the associate who copied the output into a draft.[5]

The same verification habit applies to the two risk categories, even though the operational response differs. For external AI-generated case narratives, verification means checking the public claim against the actual procedural record before responding to it or repeating it. For internal AI-assisted filings, verification means pulling every cited authority, confirming that it exists, confirming that it says what the brief claims, and checking that the procedural posture has not been distorted.

Prosecutors do not get a lower standard because they are busy. Defense lawyers do not get a lower standard because an AI tool is marketed as legal-grade. In-house counsel supervising criminal investigations do not get a lower standard because the AI output is only “background.” If the output affects a case decision, a filing, a witness interview, a charging recommendation, a public response, or litigation strategy, someone with professional responsibility has to verify it.

A practical file note for criminal practitioners in 2026

When AI-generated public content appears in or around a criminal matter, the first pass should be a record-control exercise:

  • Preserve the item as it appeared: URL, platform, title, description, date, duration, screenshots, audio or video if available, and any access limitations.
  • Separate confirmed metadata from unconfirmed substance. If no transcript is available, do not invent one.
  • Compare the public claim against court filings, docket entries, orders, bail status, hearing dates, and counsel-confirmed posture.
  • Assess case consequence rather than platform drama: juror exposure, witness contamination, client prejudice, media correction, or a need for court notice.
  • Decide who owns the follow-up: trial counsel, appellate counsel, media counsel, investigator, or a designated litigation-support professional.

When AI is used in drafting a criminal filing, the control point is citation-by-citation review:

  • Pull every authority from an official or trusted legal research source before filing.
  • Confirm the case name, court, date, reporter citation, procedural posture, holding, and pinpoint quotation.
  • Check whether the authority remains good law and whether the cited proposition is narrower than the AI summary suggested.
  • Do not rely on a generated quotation unless it has been matched against the source text.
  • Keep an internal verification trail for any AI-assisted draft that reaches a court, opposing counsel, or a client-facing litigation recommendation.

The Shiver podcast item belongs in a forthcoming Risk Digest record on AI-generated false case narratives. The Payne discipline belongs in a separate Risk Digest record on AI-hallucinated citations in criminal filings. A companion verification workflow for AI use in criminal briefs should treat both as live examples of the same professional obligation: before a lawyer relies on generated content, the lawyer has to make it true enough for the purpose at hand.

References

  1. The Murder of Robert Shiver — Apple Podcasts, June 7, 2026.
  2. Lindsay Shiver timeline — NewsNation.
  3. AI errors in US murder case lead to discipline for Georgia prosecutor — Reuters, May 5, 2026.
  4. AI Hallucination Cases — Damien Charlotin, updated July 18, 2026.
  5. Formal Opinion 512 — American Bar Association, July 2024.

Report a correction or tip

Spotted an outdated figure, a misstated fact, or a ruling this case record should reflect? Public comments are disabled for this content given the professional cost of a misreported case outcome, penalty amount, or rule text — use the structured correction channel instead.

Report a correction or tip for this record →