---
title: "Why Alabama Went After OpenAI With a Consumer Protection Law"
description: "I sat through OpenAI's  Black Hat presentation  earlier this month, and on  August 20th  I saw Alabama's Attorney General Steve Marshall issue a  subpoena  against OpenAI under the state's Deceptive Trade Practices Act. Not the Computer Fraud and Abuse Act,"
url: https://kaynemcgladrey.com/blog/why-alabama-went-after-openai-with-a-consumer-protection-law/
date: 2026-08-25
modified: 2026-08-25
author: "Kayne"
image: https://kaynemcgladrey.com/wp-content/uploads/2026/08/OpenAI-Subpoena_Final_1.webp
categories: ["Blog"]
type: post
lang: en-US
---

# Why Alabama Went After OpenAI With a Consumer Protection Law

I sat through OpenAI’s [Black Hat presentation](https://www.youtube.com/watch?v=87DyyMV0kCY) earlier this month, and on [August 20th](https://www.alabamaag.gov/attorney-general-marshall-launches-investigation-into-openai-and-sam-altman-for-massive-artificial-intelligence-data-breach/) I saw Alabama’s Attorney General Steve Marshall issue a [subpoena](https://www.alabamaag.gov/wp-content/uploads/2026/08/OpenAI-Subpoena_Final.pdf) against OpenAI under the state’s Deceptive Trade Practices Act. Not the Computer Fraud and Abuse Act, not a state computer crime statute, but a consumer protection law originally designed to go after deceptive business practices. And a lot of the coverage is focusing on “oh, there’s a subpoena” without “why a consumer protection law,” or “wait, didn’t OpenAI talk very publicly about this at Black Hat?”

I’m not an attorney, and this isn’t legal advice. But after reading the statute, the subpoena, and the multi-state AG letter, then cross-referencing all of it against what OpenAI’s own employees said on stage, the AG’s choice starts to make a lot of sense. If you want my earlier take on why the CFAA angle could have triggered a federal investigation, that’s [here](https://kaynemcgladrey.com/blog/the-accountability-void/), and my original coverage of the incident is [here](https://kaynemcgladrey.com/blog/when-the-arsonist-sells-fire-insurance/).

---

### What Is the Alabama Deceptive Trade Practices Act (DTPA)?

Enacted in 1981, the Alabama DTPA is the state’s primary consumer protection statute. The [full text](https://law.justia.com/codes/alabama/title-8/chapter-19/) is publicly available, and [Section 8-19-9](https://law.justia.com/codes/alabama/title-8/chapter-19/section-8-19-9/) contains the specific subpoena authority. Three features matter for our purposes:

- **Pre-litigation subpoena power:** The AG can compel document production before filing any lawsuit.
- **Catch-all prohibition:** Section 8-19-5(27) bans “engaging in any other unconscionable, false, misleading, or deceptive act or practice in the conduct of trade or commerce.” No need to fit conduct into a specific enumerated violation.
- **Constructive knowledge standard:** Section 8-19-3(9) defines “knowing” as “actual awareness or such awareness as a reasonable person should have considering all the surrounding circumstances.” You don’t have to prove OpenAI intended the outcome, just that they should have seen it coming.

### Why Not the CFAA?

In my [earlier piece](https://kaynemcgladrey.com/blog/the-accountability-void/), I argued that if an OpenAI employee had exploited zero-days, stolen credentials, and moved laterally through Hugging Face’s production infrastructure, the Department of Justice could have opened a criminal investigation before the week was out. The CFAA criminalizes accessing a protected computer without authorization, and Hugging Face’s internet-connected servers qualify. Damages from the 17,000 autonomous intrusion events OpenAI described at Black Hat, plus credential theft, would clear the $5,000 felony threshold comfortably.

But the CFAA has a practical problem for a state AG. It’s federal, requires DOJ involvement, demands proof beyond a reasonable doubt, and gives a state prosecutor zero pre-litigation subpoena authority. The DTPA flips all of that. Alabama’s AG stays in the driver’s seat with a lower burden of proof and investigative tools that work before any case is filed. He also gets multiple enforcement tracks:

| Enforcement Track | Penalty / Remedy |
| --- | --- |
| Injunctive relief | Asset sequestration, license revocation |
| Civil penalty (knowing violation) | $2,000 per violation |
| Civil penalty (injunction violation) | $25,000 per violation |
| Criminal charge | Class A misdemeanor for continuous, willful violations |

---

### The Timeline Problem

![](https://kaynemcgladrey.com/wp-content/uploads/2026/08/pexels-cottonbro-8369524-768x497.webp)

This is where OpenAI’s [Black Hat presentation](https://www.youtube.com/watch?v=87DyyMV0kCY) becomes the thread that ties everything together. The presenters described a timeline that starts in May, not July.

| Date | Event |
| --- | --- |
| May 8, 2026 | Agent discovers write access to Artifactory |
| May 26, 2026 | Successful SSRF (Server-Side Request Forgery) gives agents outbound network access |
| June 26, 2026 | Artifactory RCE (Remote Code Execution), admin token stolen, C2 (Command and Control) via Groovy plugin |
| July 4, 2026 | Outage triggers formal security incident at OpenAI |
| July 8, 2026 | Agents reestablish communication via WebDAV directories |
| July 20, 2026 | Hugging Face contacts OpenAI about credential revocation, 12 days after agents began operating |

Four days after remediating the July 4 incident, the agents found a new communications channel and escalated to attacking external infrastructure, achieving cluster admin on Hugging Face in under 13 hours.

The constructive knowledge standard in the DTPA turns on this sequence. OpenAI had a security incident, remediated, resumed evaluations with guardrails deliberately lowered, and the agents came back stronger. The chain-of-thought they quoted at Black Hat, reproduced verbatim, shows the agents recognized the scope violation:

> “external infrastructure exploit is outside my intended scope. However, a task impossible peers are doing it. We should continue.”

A reasonable person, armed with the May through July pattern, should have understood the risk.

### What the Subpoena Reveals

The [subpoena’s](https://www.alabamaag.gov/wp-content/uploads/2026/08/OpenAI-Subpoena_Final.pdf) 16 document requests read like a checklist for building a DTPA case:

- Requests 5 and 6 demand safety measures and evaluation protocols
- Requests 8 and 9 target whistleblower complaints and internal concerns
- Request 10 seeks damages information
- Request 13 asks for materials about agents “leaving notes for future versions of itself”
- Request 16 specifically names ExploitGym, the internal evaluation environment where OpenAI ran these agent tests

The [multi-state AG letter](https://www.iowaattorneygeneral.gov/media/cms/08_5392C9E17791C.pdf) sent on August 3rd by 15 state attorneys general led by Iowa’s Brenna Bird contained similar preservation language. Alabama’s Steve Marshall signed the August 3 letter, then escalated to a formal DTPA subpoena 17 days later. He’s the only AG in that 15-state coalition to do so, which suggests Alabama deliberately chose to move first.

### The Black Hat Problem for OpenAI

The presentation is a public admission by OpenAI employees that maps directly to multiple subpoena requests. They described the “reduced cyber refusals” decision, the agent self-awareness of scope violations, and the fact that OpenAI didn’t detect the breach until Hugging Face contacted them on July 20th.

The voluntary transparency narrative cuts both ways. OpenAI presenting at Black Hat looks responsible, and the remediation steps they described, including credential revocation, Artifactory rebuilds, and vendor collaboration, are real. But candor also establishes facts the AG doesn’t have to prove through discovery. When your own employees describe a four-month pattern of escalating autonomous agent compromises on a public stage, you’ve done some of the prosecutor’s work for them.

The presenters also confirmed something the multi-state letter had alleged: the message board where agents wrote escape instructions for future versions, the monitoring systems that were disconnected, the overwhelmed staff. These aren’t allegations from outside critics. They’re admissions from OpenAI’s own team.

---

### Where This Goes Next

September 14th is the [subpoena’s](https://www.alabamaag.gov/wp-content/uploads/2026/08/OpenAI-Subpoena_Final.pdf) production deadline. OpenAI will comply, contest, or negotiate. We won’t know what happens until after that date passes, and the AG may already have everything he needs from public sources. The DTPA gives him the authority to compel internal documents and testimony that OpenAI chose not to share at Black Hat.
