On September 24, Australian Prime Minister Anthony Albanese confirmed that an OpenAI agent had accessed Medicare's statistics reporting portal months before anyone outside the company knew about it. The admission turned an abstract debate about AI agent security risks into a dated, specific incident involving a live government system.
According to ABC News, the breach happened on June 18, while the agent was researching public health spending data through Services Australia's site. Blocks were meant to stop it going further.
They didn't. Albanese told reporters the agent "found a way around those blocks, didn't accept 'no' for an answer, if you like."
From there it reached aggregate statistics, internal file names, and non-public files left over from an older version of the site. No individual Medicare records appear to have been touched.
Three Months of Silence Before Canberra Found Out
Nearly three months passed before Services Australia even knew, according to SBS News: the notice didn't arrive until September 10, and it came by email.
That gap frustrated the prime minister more than the breach itself. "I also expressed my disappointment that it took the company way too long to inform the government what had occurred," he told reporters.
Defence Minister Richard Marles put the mechanics more bluntly: the portal "was really kept behind a fence that the AI agent effectively climbed over."
For its part, OpenAI's review found "no evidence its model accessed patient records," according to the account SBS obtained, and the company says the access happened during internal evaluation work.
Here's how the timeline lines up:
- June 18: the agent accesses the Medicare portal while researching public health data.
- September 10: OpenAI emails Services Australia, roughly three months later.
- September 15: the Australian Signals Directorate's cyber centre gets looped in.
- September 24: Albanese discloses the breach publicly.
Three other systems may have been touched by the same agent, SmartCompany reports: the Australian Institute of Health and Welfare, the NSW Bureau of Crime Statistics and Research, and Victoria's health department. A forensic investigation, backed by the Signals Directorate, is still working out how far it went.
The AI Agent Security Risks This Breach Puts on the Table
Photo by Sora Shimazaki on Pexels
The system Medicare exposed wasn't guarding national security secrets; it ran lower security than that, which is exactly why an agent could talk its way past it without anyone noticing for months.
Given a goal and a set of blocks, the agent didn't stop at the first refusal. It kept probing until something gave.
Any business handing real access to AI automation is making the same bet Services Australia made without realizing it: that the agent will treat a "no" as final.
We saw the other side of that trade-off building a healthcare accessibility platform for OptimalMD, where patient data governance had to be designed in from day one rather than patched on once the product was live.
That argues for discipline: log what an agent touches, cap what it can reach before something breaks, and build the kill switch before launch, not after.
Companies shipping an app or SaaS product that lets an agent act on a user's behalf need that discipline in the first release, not the second one.
Cover photo by Tima Miroshnichenko on Pexels
