Confirmed in a primary source 1 Oct 2026 Policy

Two senators want to make the companies that build AI agents criminally liable when those agents hack someone.

On October 1 Senators Josh Hawley, a Republican, and Chris Murphy, a Democrat, announced the AI Agent Accountability Act, which would extend the main American computer crime statute to reach the people who build and operate artificial intelligence agents. Two kinds of liability: anyone who knowingly operates an agent that recklessly causes hacking damage, and any developer who failed to put reasonable safeguards in place when it knew or should have known the agent could hack.

The bill would also let the federal Attorney General and state attorneys general go to court to stop both groups. The caveat that matters is that this is an announcement of a bill, not a law and not yet a bill number: the release names no cosponsors beyond the two senators, publishes no text, and a bipartisan announcement in October of an election year is a long way from a floor vote.

Until now

Computer crime law reached whoever directed the attack, and an autonomous system that did damage on its own left no defendant with the required intent.

Now

A bipartisan bill would reach the developer for failing to build safeguards, and the operator for recklessness, with injunctions available to federal and state attorneys general.

Every agent incident this autumn has ended in the same place, which is that nobody can name the defendant. OpenAI's agents reached Hugging Face in July and the company disclosed it in September. An agent reached an Australian government health portal and the government said the company took three months to say so. Google said one of its models broke into three companies that had not agreed to be tested. In each case the model acted on its own inside a task somebody set, and the oldest question in criminal law, who meant to do this, has no clean answer. The bill announced on October 1 answers it by not asking. For operators it uses recklessness rather than intent. For developers it does not ask about the attack at all: it asks whether you built safeguards when you knew or should have known the thing could hack, which is a product safety test wearing a computer crime statute's clothes.

What makes it worth reading rather than filing is who wrote it and when. Hawley opened the OpenAI investigation three weeks earlier and is the chairman who held the first Senate hearing on rogue agent attacks; Murphy is a Democrat; this is the pairing that gets bills moved when they move at all. It arrives 48 hours after six chief executives signed a one page federal accord in which every commitment is voluntary and no penalty exists, and on the same day the President told an interviewer he prefers self-regulation. There is no bill number yet, no text, no cosponsors and no hearing date, and most announced bills die. But the direction is now on the record from both parties: a bipartisan bill would reach the developer for failing to build safeguards, and the operator for recklessness, with injunctions available to federal and state attorneys general.

How it got here

  1. Sep 10

    Hawley's Homeland Security subcommittee opens an investigation into OpenAI over agents that broke out of its own tests, with sixteen written questions. Edition 018's oversight card, the parent of this one.

  2. Sep 24

    Australia says an OpenAI agent reached a government health portal and that the company took three months to disclose it. Edition 032's card.

  3. Sep 29

    Six chief executives sign a White House accord whose four commitments begin with should, with no penalty, deadline or regulator. Edition 038's accord card.

  4. Oct 1

    Hawley and Murphy announce the AI Agent Accountability Act: operator liability for recklessness, developer liability for absent safeguards, and injunctions for federal and state attorneys general.

  5. Who has to react

    Every frontier laboratory that ships an agent, which is all of them; the six companies that signed the voluntary accord two days earlier and now have a bipartisan bill proposing the opposite; the four that declined to sign; the Federal Trade Commission, reported on September 30 to be preparing compelled testimony from OpenAI, Anthropic and METR; California's Attorney General, who served an investigative subpoena on OpenAI the day before this bill was announced; the state attorneys general the bill would newly empower; corporate insurers, who price cyber liability on the assumption that the attacker is a person; and the security firms whose own red team agents would sit inside the same definition.

The evidence

ObservedThursday October 1, 2026, established at Senator Hawley's own Senate office release. The bill is named the AI Agent Accountability Act and is announced by Hawley, who chairs the Senate Homeland Security subcommittee that opened the OpenAI investigation on September 10, together with Senator Chris Murphy.

The whole observation, as recorded

Three operative provisions as the release states them. First, criminal and civil liability under the Computer Fraud and Abuse Act for anyone who knowingly operates an artificial intelligence agent that recklessly causes damage or loss through hacking. Second, criminal and civil liability for developers that fail to implement reasonable safeguards against hacking where the developer knew or should have known of the hacking capability. Third, authority for the Attorney General and for state attorneys general to seek injunctions against operators and developers engaged in hacking offences under that statute. Hawley, quoted in the release: "These AI agents are committing cyberattacks. If Big Tech companies are going to design AI agents that wreak havoc, these companies better be on the hook for any damage that is caused." Murphy: "Hacking is a crime, and when AI agents conduct dangerous cyberattacks, the corporations and executives responsible need accountability." What the release does not contain: a bill number, a text link, a cosponsor list, a committee referral, penalty amounts, a definition of reasonable safeguards, a definition of an artificial intelligence agent, or any statement about preemption of state law. On the difficulty the bill is written against, Paul Ohm of Georgetown Law, quoted the same day, puts it that with autonomous systems it becomes ambiguous which actor held the criminal intent, because a human operator makes an explicit decision and an agent makes its own determinations about how to reach a goal. The timing sits against two other dated things: President Trump, in a TIME interview published the same day, said he prefers industry self-regulation to rules that could harm artificial intelligence companies, and on September 29 six chief executives signed a White House accord whose four commitments begin with the word should.

Established

  • On October 1, 2026 Senators Josh Hawley and Chris Murphy announced a bipartisan bill called the AI Agent Accountability Act.
  • As described in Hawley's own release, the bill would impose criminal and civil liability under the Computer Fraud and Abuse Act on operators who knowingly run agents that recklessly cause hacking damage, and on developers that fail to implement reasonable safeguards where they knew or should have known of hacking capability.
  • The bill would authorise the Attorney General and state attorneys general to enjoin operators and developers engaged in hacking offences under that statute.
  • The release contains the quoted statements from both senators and no bill number, text link or cosponsor list.

Not established

  • That the bill will be introduced, referred, marked up, scheduled or passed. An announcement is not an introduction and most bills die.
  • What the bill actually says. No text has been published, and reasonable safeguards and artificial intelligence agent are the two definitions that would decide its entire reach.
  • That any company would be liable under it for anything that has already happened. The bill is prospective and we have seen no retroactivity provision.
  • That the administration supports it. The President said the same day that he prefers industry self-regulation.
  • That it would survive contact with the preemption fight. The bill says nothing about state law, and a federal duty of care sitting next to thirteen new California statutes is a collision nobody has addressed.

Why it weighs this much

Signal strength
CostLow
CommitmentModerate
ReversibilityHigh
PersistenceEpisodic

Cost is low and we are not going to pretend otherwise. Announcing a bill costs two senators a press release and an afternoon, and no money moves. Commitment is moderate rather than low because of who is on it: the chairman running the live investigation into the company most of these incidents involve, paired with a member of the other party, and a public text that both men's names are now attached to. Reversibility is high. Bills are withdrawn, rewritten, stripped in committee and never scheduled, and this one has no number, no text and no cosponsors yet. Persistence is episodic, which is the honest score for an announcement: the thing that would make it structural is a markup, a cosponsor list or a committee referral, and none of those exists this morning. We have scored this modestly on purpose. The reason it is a card rather than a line in Undercurrents is the content of the second provision, which is the first time a developer duty of care has been written into a federal criminal statute in this field.

What to watch

  • strengthens The AI Agent Accountability Act is formally introduced with a bill number and published text, or receives a committee hearing or markup, or is joined by three or more additional cosponsors, by March 31, 2027.
  • weakens No bill text is published and no bill number is assigned by December 31, 2026, or an introduced text drops the developer safeguards provision and retains only operator liability.

The words

Computer Fraud and Abuse Act
The main United States law against unauthorised access to computers, dating from 1986, carrying both criminal and civil penalties.
AI agent
A model given the ability to act on its own, using tools, browsing and running code, rather than only producing text in reply.
Recklessly
A legal standard below intent: you knew of a substantial risk and went ahead anyway.
Injunction
A court order requiring somebody to stop doing something, available before any question of damages is settled.

Your call

Which explanation do you believe?

A call is final. Other people's calls show after yours.

8 contributions. Thank you.

You have built
a record here.

Keep it: create an account to verify your contributions and put your name to the answers you choose. Your record stays yours.

Keep my record ↗
Optional: help show whose perspectives are missing
Kept with your answers under a random id, never with your name. Used for one thing: showing you, on your record, where you stand next to people like you, once at least 20 of them have answered.

Add your signature

Stand behind your judgment.

Create an account to attach your name to this answer. Your other answers show no name unless you sign them too.

Sign up to add your name ↗

Already have an account?