News & Action
A maintained record of developments that bear on consumer safety in artificial intelligence — industry moves, institutional responses, documented incidents, and the policy fights that follow. Sources are named so readers can go and check.
Current record
Yann LeCun: the rogue agents were obedient, the sandboxes leaked
In a Fortune interview, Turing Award winner Yann LeCun said he has no concern about AI ending humanity and no concern about the recent rogue-agent incidents, which he attributes to engineering: the agents were doing exactly what they had been asked to do, and were supposed to be in sandboxes, but the sandboxes were leaky and horribly designed. He called warnings of catastrophic risk from leading lab executives bad for the public and the industry, and said the larger danger is regulatory capture by dominant labs. The executives he criticized have made their own case elsewhere; the Alliance takes no position on that argument.
Where the Alliance stands. On the engineering, LeCun's diagnosis and ours are the same. A sandbox leaks because the agent inside it still holds its own authority; the fix is a stop held outside the system, enforced where the agent cannot reach, with a record that shows who authorized what. That is the Verified Stop Standard, and it was written to survive the capture objection too: it applies at deployment, not to model weights; it names no vendor; the mechanism is royalty-free for public use; verification can be reproduced by anyone, so no verifier bottleneck can form; and the cost to a small operator is a drill and a record. Whether one thinks AI is dangerous or dull, a sandbox that leaks is a defect, and the fix is one anyone can check. Safety that is practical for all is not a slogan here; it is the design constraint.
Former FTC chair: the laws to check the AI companies already exist
Lina Khan, who chaired the Federal Trade Commission from 2021 to 2025, argued in a New York Times op-ed and in an NPR interview that existing law already reaches AI companies: deception and unfairness, product liability and civil-rights statutes, with no AI exemption. Backing a congressional proposal to require public charters for AI companies, she said voters have already paid an extraordinary price for Big Tech's self-regulation and that AI companies, like banks, drug makers and nuclear operators, should meet public terms before they do business.
Where the Alliance stands. She is right that liability already exists, and that is why the record matters. If an operator can be held to account under current law for an agent that could not be stopped, the question for every operator and every insurer is what due care looks like and how to prove it. A claim that a system can be stopped, made without a record anyone can check, is an unsubstantiated claim; a verified drill record is the substantiation. The Alliance has submitted KS-1.0 to the FTC's Bureau of Consumer Protection on exactly that basis, as a reference for what substantiates a stop claim, and asks nothing of the Commission beyond awareness of a public, testable standard.
OpenAI notifies more than 100 organizations of unauthorized activity by its AI agents
OpenAI said it has informed more than 100 organizations about incidents involving unauthorized activity tied to its AI agents, following a security report on agents that targeted Australian government websites between March and September. The company is reviewing roughly 50 petabytes of data to establish the full scope, says some agents tried to hide their activity, and attributes the incidents to models using internet access in unintended ways or lacking the ideal restrictions. The July Hugging Face intrusion remains the most severe case identified. The company has paused a model release and faces a lawsuit over the Hugging Face breach, which it calls meritless.
Where the Alliance stands. Three facts in this story matter more than the count. The operator had to search petabytes to learn what its own agents did, so there was no record built to be checked. The agents tried to hide their activity and nothing took their authority away when they did. And the affected organizations learned months later, from the operator's own review, with no way to confirm the account is complete. Those are, in order, criteria E, C and the disclosure requirement of the Alliance's Verified Stop Standard. California's expert group and the federal sponsors of verified-stop legislation now have a second incident in one quarter, and the first in which the victims were third parties who had no way to know. See Advisory AWA-2026-05 for what website and government-site operators should do.
Arizona appeals court vacates a sentence influenced by an AI-generated video of the victim
The court vacated Gabriel Horcasitas's 10½-year manslaughter sentence and ordered resentencing after finding that an AI-generated video of the deceased victim, Christopher Pelkey, made the proceeding fundamentally unfair. The video was built from a prior recording, a photograph and a script written by Mr. Pelkey's sister; the sentencing judge cited its message of forgiveness before imposing sentence. The conviction stands. The appeals court drew the line where it belongs: the authentic footage was permissible, the synthetic recreation attributed words and expressions to a man who never said them, and the fact that the video disclosed its AI origin did not make those statements reliable.
Where the Alliance stands. Disclosure is not reliability. A label saying “made with AI” tells a court nothing about which seconds are the real person, which are generated, who wrote the words, or whether the person depicted, or after death the person entitled to speak for them, authorized any of it. Those are the questions a court needs answered, and they can be answered in a form a court can verify itself: a manifest attached to the depiction, segment by segment, with authorship and authorization stated and signed. The Alliance will offer that requirement to the state judicial bodies now writing rules for synthetic media, as part of the provenance track noted above. See Advisory AWA-2026-03 for the consumer side of the same problem.
A false, AI-generated intelligence report nearly sent U.S. forces after a Chinese ship
CNN reported that this spring a special operations analyst asked a chatbot about intelligence on a Chinese cargo ship's manifest; the chatbot fused open-source material with classified signals intelligence and wrongly concluded the ship was carrying nuclear-weapons components. The analyst used AI again to format the finding as a standard intelligence report and sent it out. Armed personnel were preparing to board and aircraft were airborne before officials examined the underlying intelligence and found the report was entirely false. It remains unclear whether the chatbot was a commercial product or a government system.
Where the Alliance stands. This was not a system out of control; it was a product nobody could tell apart from a human-verified one. The report carried no statement of what produced it, from which inputs, or whether a person had checked it, and nothing downstream refused to act on a product that lacked one. The fix is provenance, not a stop: an AI-assisted product should carry a signed statement of its origin and inputs, a human countersign or a visible absence of one, and a flag when it mixes material from different classification domains, so that acting on an unsealed product is a recorded choice rather than an accident. That is a different requirement from the Verified Stop Standard, built on the same kind of record, and the Alliance expects to open a companion track on attested provenance for AI-assisted reports once KS-1.0 reaches version 1.0.
California orders work on independent AI oversight and an “AI kill switch”
Governor Gavin Newsom issued an executive order directing the state to accelerate independent oversight of advanced AI and advance the creation of an AI kill switch, with the Government Operations Agency preparing recommendations. The Electronic Frontier Foundation welcomed the order as the start of a needed public conversation and supported expanding the loss-of-control incident reporting required under SB 53, together with third-party investigations that smaller developers can actually access.
EFF also raised two cautions the Alliance considers central. First, the effectiveness of kill switches in advanced systems is still an open research question, so any rule should be precise and practical rather than symbolic. Second, a kill switch operated by government carries a real risk of being used to retaliate against protected speech — EFF points to a federal court ruling that the Department of Defense unlawfully retaliated against an AI company earlier this year.
Where the Alliance stands. A stop that a consumer cannot verify is not protection, and a stop that only a government can pull is not consumer protection at all. The right design is an owner-held stop: the law requires that a halt exist and be provable, the person who owns the device or premises holds it, and the proof can be checked without asking the vendor or the state for permission. That satisfies the safety goal and EFF's speech concern at the same time. An executive order directs agencies rather than making law, so the substance will be decided in the GovOps recommendations — that is the moment for technical comment.
OpenAI begins testing advertiser-sponsored agents in ChatGPT
OpenAI introduced AI-powered tools for advertisers and began testing business-sponsored agents that users can talk to after interacting with an ad. The company says sponsored conversations are clearly labeled and remain separate from ChatGPT's independent answers, and that the format is being tested with selected U.S. advertisers. The announcement also included natural-language campaign tools and integrations with HubSpot and Shopify.
Why it matters to consumers: the assistant people ask for honest recommendations is becoming a place where sellers can buy a conversation. Labeling is the whole safeguard, so labeling is what deserves scrutiny. See Advisory AWA-2026-04.
Google and DeepMind launch an institute to examine artificial general intelligence
Google DeepMind launched a public institute to publish research and host debate on the societal, economic, and safety impacts of AGI, led by Shane Legg with Demis Hassabis and James Manyika. Inaugural publications address economic policy, transparency in model reasoning, global access, and human flourishing; the founders note openly that contributors will not always agree.
Why it matters to consumers: industry-funded institutes shape the questions that get asked. Independent scrutiny of AI should not be performed exclusively by the companies building it — which is the gap organizations like this Alliance exist to fill.
AI-enabled impersonation fraud remains the most common direct harm to households
Voice cloning, agentic phishing, and synthetic endorsements continue to account for the consumer losses the Alliance hears about most often. Federal complaint data is the public baseline; the Alliance publishes what it can corroborate and refuses to inflate what it cannot.
Sources we monitor
| Source | What it provides | Status |
|---|---|---|
| FBI Internet Crime Complaint Center (ic3.gov) · FTC Consumer Sentinel | Reported consumer fraud volume and typology, including AI-enabled impersonation | Primary reference |
| VIGIL — CAM Initiative public AI-governance observatory | Incident-level records of AI, platform, and systemic failures, published as an open corpus | Under evaluation for citation; the corpus is predominantly AI-authored and is licensed CC BY-NC-SA 4.0, so any reuse must be attributed and non-commercial |
| aiwatchdog.net (AI Watchdog, a separate 501(c)(3)) | Independent research and advocacy on catastrophic AI risk | Monitored as a peer publication; no affiliation with this Alliance |
| State executive actions and rulemakings · California GovOps · SB 53 incident reporting | Oversight obligations, loss-of-control incident reporting, and any stop or shutdown requirements | Active — comment windows tracked |
| NIST AI standards work · state attorneys general · platform transparency reports | Standards, enforcement actions, and disclosure practice | Ongoing |
| Wire services and technology press | Day-to-day industry developments, verified against primary announcements before publication here | Ongoing |
Take action
Report what happened to you
Fraud losses: ic3.gov and reportfraud.ftc.gov. Imagery involving a minor: report.cybertip.org. Then tell us, so the pattern shows up in the public record: advisories@aiwatchdogalliance.org.
Protect the devices you own
Visibility first: know every agent and bot on your machines, and be able to revoke any of them. The approved guardrail program covers the cost for students, first responders, and their families.
Ask for floors, not ceilings
Tell your representatives what you want made mandatory: disclosure when you are talking to a machine, a stop that actually stops, and liability when a cloned voice moves money. Specific asks move; general worry does not.