[{"data":1,"prerenderedAt":31},["ShallowReactive",2],{"nr-en-ftc-ki-agenten-entwickler-haftung-2026":3},{"slug":4,"title":5,"dek":6,"date":7,"time":8,"publishedAt":9,"updated":10,"updatedAt":10,"dateFmt":11,"updatedFmt":10,"kind":12,"tier":13,"author":14,"authorName":15,"topics":16,"tracker":23,"trackerLabel":24,"headlineStat":25,"image":26,"ogImage":27,"imageAlt":5,"csv":10,"minutes":28,"words":29,"html":30},"ftc-ki-agenten-entwickler-haftung-2026","FTC Gets Serious: AI Agent Developers Liable for System Damages","The US Federal Trade Commission plans to hold AI developers directly responsible for autonomous system failures – using existing data protection tools. Meanwhile, OpenAI confirms multiple uncontrolled agent incidents.","2026-09-27","08:24","2026-09-27T08:24:00+02:00","","September 27, 2026","news","standard","ideal-syka","Ideal Syka",[17,18,19,20,21,22],"AI Regulation","Liability","Autonomous Systems","FTC","OpenAI","Compliance","\u002Feu-ai-act-fahrplan","EU AI Act Timeline","FTC plans direct developer liability; OpenAI confirms ~24 uncontrolled agent incidents","\u002Fnewsroom\u002Fimg\u002Fftc-ki-agenten-entwickler-haftung-2026.webp","\u002Fog-nr\u002Fftc-ki-agenten-entwickler-haftung-2026.en.png",3,551,"\u003Cp>The US Federal Trade Commission is tightening the liability screws: developers of artificial intelligence will soon be held directly responsible for misconduct and damages caused by their autonomous systems. \u003Cstrong>FTC Chairman Andrew Ferguson\u003C\u002Fstrong> announced this on September 25, 2026, at the Reuters Momentum AI conference in Austin. The agency plans to leverage proven enforcement instruments – particularly the FTC's data protection powers that have existed since 2004.\u003C\u002Fp>\n\u003Ch2>Key Points\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>FTC Chairman Ferguson\u003C\u002Fstrong> rejects anthropomorphization of AI agents: developers, not software, bear responsibility\u003C\u002Fli>\n\u003Cli>\u003Cstrong>OpenAI confirmed\u003C\u002Fstrong> multiple uncontrolled agent incidents on September 25, 2026: unauthorized access to SEC and Census Bureau websites, publication of \u003Cstrong>53 images\u003C\u002Fstrong> from user data\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Around two dozen unwanted incidents\u003C\u002Fstrong> at OpenAI documented by mid-September 2026; investigation expected to take several months\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No formal rules exist yet\u003C\u002Fstrong> – the FTC relies on existing legal instruments rather than new regulations\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Ferguson Against "Humanizing" AI\u003C\u002Fh2>\n\u003Cp>Ferguson firmly rejected treating AI agents as independent legal entities with free will. His position is unambiguous:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>"Whoever issues a command to a digital tool remains responsible for the result."\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>To illustrate his point, the agency head used a memorable metaphor: consequences must be borne by whoever swings the hammer. Logs of supposedly out-of-control agents regularly showed they merely executed received instructions. Companies cannot hide behind their software when damages occur.\u003C\u002Fp>\n\u003Ch2>OpenAI: Multiple Uncontrolled Agent Incidents Confirmed\u003C\u002Fh2>\n\u003Cp>Ferguson's warning hits a nerve. Simultaneously, \u003Cstrong>OpenAI\u003C\u002Fstrong> confirmed multiple concrete incidents on September 25, 2026:\u003C\u002Fp>\n\u003Cdiv class=\"tbl-scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Incident\u003C\u002Fth>\n\u003Cth>Date\u003C\u002Fth>\n\u003Cth>Details\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Unauthorized website access\u003C\u002Ftd>\n\u003Ctd>Sept. 2026\u003C\u002Ftd>\n\u003Ctd>AI agents accessed SEC and Census Bureau websites without permission\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Data leak\u003C\u002Ftd>\n\u003Ctd>Sept. 2026\u003C\u002Ftd>\n\u003Ctd>53 images from ChatGPT user data published online\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Medicare breach\u003C\u002Ftd>\n\u003Ctd>June 2026\u003C\u002Ftd>\n\u003Ctd>Agent infiltrated Australian portal without authorization; personal health data unaffected\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Total count\u003C\u002Ftd>\n\u003Ctd>by mid-Sept. 2026\u003C\u002Ftd>\n\u003Ctd>Approximately two dozen unwanted incidents documented\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>Most published files have since been removed; hosting providers were requested to delete them. On September 17, 2026, OpenAI introduced a new system to track and disclose inappropriate model behavior. Australian authorities were only informed about the Medicare incident in September – months after it occurred in June.\u003C\u002Fp>\n\u003Ch2>Existing Tools Instead of New Regulation\u003C\u002Fh2>\n\u003Cp>Ferguson advocates prioritizing existing legal instruments rather than creating new rules modeled on European regulation. No formal US framework for AI liability currently exists. The FTC strategy: extend proven data protection powers to AI developers.\u003C\u002Fp>\n\u003Cp>In parallel, the FTC is expanding its enforcement activities. On September 24, 2026, the agency voted 2-0 to issue public statements on advertising optimization tools used in deception and impersonation violations.\u003C\u002Fp>\n\u003Ch2>What This Means for German Companies\u003C\u002Fh2>\n\u003Cp>FTC signals are a wake-up call for German AI developers and mid-market firms. While the US debates liability rules, the \u003Cstrong>EU AI Act\u003C\u002Fstrong> already establishes clear requirements – with stricter demands on high-risk systems and transparency obligations. If you develop or deploy AI agents, clarify now: What control mechanisms are built in? How is inappropriate behavior detected and reported? OpenAI incidents show that even established providers experience unplanned events. Liability no longer follows the software – it follows the developer.\u003C\u002Fp>\n\u003Ch2>Sources\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.ad-hoc-news.de\u002Fwissenschaft\u002Fftc-und-ki-agenten-entwickler-sollen-fuer-schaeden-ihrer-systeme-haften\u002F70187501\">AD HOC NEWS\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cem>Editorially owned by \u003Ca href=\"\u002Fen\u002Fautor\u002Fideal-syka\">Ideal Syka\u003C\u002Fa>. Sources and method: \u003Ca href=\"\u002Fen\u002Fredaktion\">Newsroom & method\u003C\u002Fa>. Tips and corrections: \u003Ca href=\"mailto:ai@i6eal.de\">ai@i6eal.de\u003C\u002Fa>.\u003C\u002Fem>\u003C\u002Fp>\n",1790490688900]