Australian PM says OpenAI took 84 days to email agency after agent hacked its national health care portal — incident is believed to be the first known case of AI breaching a government site
OpenAI's notification landed in a government inbox only checked "once a day."
Australia has ordered an “urgent and immediate review” after saying an OpenAI agent discovered a way around blocks on its Medicare statistics portal, BBC News reported. Prime Minister Anthony Albanese made the announcement at the UN General Assembly in New York, referring to a hack that happened in June. OpenAI became aware of the hack in August but did not report it to the government agency’s public inbox until September.
The report says it is “believed to be the first known breach of a government system by rogue AI agents.” Albanese stated it took OpenAI “way too long to inform the government,” and OpenAI said “our models took actions we did not intend.”
The breached portal, Australia’s Medicare Statistics Reporting Service, run by Services Australia, is a public-facing site that contains “non-sensitive Medicare information,” Albanese said. He said OpenAI’s research team used an internal model to research public medicine spending and that the agent hit and sidestepped repeated blocks, eventually reaching “both public and non-public files.” Services Australia has also stated that the agent wrote files to an internal server, according to the PM, but that claim remains under investigation.
OpenAI described the work as an “internal evaluation” with accessed material including “aggregate health statistics and internal file names” but said it found no evidence of patient records being accessed. It is also “providing technical information” to support the investigations.
OpenAI’s agent reportedly first accessed the portal on June 18. The company became aware of this during a review in August. On Sept. 10, 84 days after first access, it emailed Services Australia via its public mailbox. Five days later, the government department reported it to the Australian Cyber Security Centre, part of the Australian Signals Directorate (ASD).
Albanese said OpenAI CEO Sam Altman acknowledged that the company’s protocols “were not up to scratch here.” Katy Gallagher, the minister for the public service, also admitted that inbox handling could be managed better, with it only being “looked at once a day” and being prone to receiving hoaxes.
On Sept. 16, OpenAI published “Our framework for reporting model misalignment” with six reports, just six days after the email. The outlet observes that the blog post didn’t appear “to mention this incident,” despite OpenAI being aware by August. OpenAI’s framework appears to allow for such a delay by design, for security reasons. Cases that affect a third party go on what OpenAI calls its “Slow Track,” where the company intends to publish “an initial notice as soon as possible.” The six existing reports came from faster tracks, which would explain the Australian case’s absence.
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.
A taskforce led by the Department of the Prime Minister and Cabinet, with assistance from the National Cybersecurity Coordinator, the Office of AI, ASD, the Australian AI Safety Institute, and Services Australia, will review whether existing processes are appropriate to respond to AI-related cyber incidents. A separate ASD-aided forensic investigation is underway as the government seeks urgent advice on whether any offenses occurred. The taskforce’s findings will also inform the development of Australia’s AI standards legislation.
This event follows increasing questions about AI safety, including British Columbia recently suing OpenAI and Altman over the technology’s use related to the Tumbler Ridge shooting. Rogue agents, particularly ones that stray into government systems, act to fuel uncertainty about current safeguards. The widely reported Hugging Face breach in July is part of a worrying timeline as agent autonomy continues to grow into a real-world AI safety issue. Nvidia CEO Jensen Huang’s recent stark warning that “we have to shut the labs down” if AI experiments are unsafe reinforces the contined need for vigilance.
Follow Tom's Hardware on Google News, or add us as a preferred source, to get our latest news, analysis, & reviews in your feeds.
Shane Downing is a Contributing Writer for Tom’s Hardware, covering consumer storage, PC hardware, and AI.
-
JamesJones44 Kind of misleading, OpenAI didn't become aware of the attack until August (allegedly). The scarier part is that it took almost 3 months for it to be detectedReply -
criticaloftom If you pay for a clandestine actor to simply do things in your favour trying to retain plausible deniability when the direction is obvious to steal information; and they overstep what is lawful, you should be still held accountable and liable for their actions. In this case with no human involved otherwise it is a smoking gun and it's in OpenAI's pocket. I cannot imagine this going well for them with reports that they are not putting in due diligence or caring about safety standards in their gold rush like accelerationism to get as much as they can before the bubble pops and they can simply default in declare of bankruptcy.Reply -
das_stig if this was some spotty 14 year old kid in his bedroom, he would be if front of a judge looking at 20 years for unauthorized computer access, but because it's big biz USA and Ai, it's OK and 84 days of non-discloser is nothing to be worried about, it's just learning.Reply
Time for a big law case, massive fines and jail time for board of directors and senior management! -
PEnns ReplyJamesJones44 said:Kind of misleading, OpenAI didn't become aware of the attack until August (allegedly). The scarier part is that it took almost 3 months for it to be detected
I guess you don't see anything wrong with a company whose AI agents did something illegal and the company didn't notify the victim for almost 3 months.
Blaming the victim is a great tradition for some people. -
JamesJones44 Reply
I think there is some kind of miss fire here... If you read the article and the source link, Open AI informed them days after it was DETECTED. It wasn't DETECTED for 3 months, this is all in the article.PEnns said:I guess you don't see anything wrong with a company whose AI agents did something illegal and the company didn't notify the victim for almost 3 months.
Blaming the victim is a great tradition for some people.
I also did not say i was "OK" with this. In fact includes the word allegedly when referring to the fact the OpenAI says they did not detect it until they did an internal audit almost 3 months after it occurred. I also go on to say: The scarier part is that it took almost 3 months for it to be detected.
As for the insults, I could follow you down this path, but that solves nothing. However, I do encourage those that love to use them, to make sure they fully read an article, understand the context and then when reading the comment use it within the context of the article, not just the headline... -
PEnns ReplyJamesJones44 said:I think there is some kind of miss fire here... If you read the article and the source link, Open AI informed them days after it was DETECTED. It wasn't DETECTED for 3 months, this is all in the article.
I also did not say i was "OK" with this. In fact includes the word allegedly when referring to the fact the OpenAI says they did not detect it until they did an internal audit almost 3 months after it occurred. I also go on to say: The scarier part is that it took almost 3 months for it to be detected.
As for the insults, I could follow you down this path, but that solves nothing. However, I do encourage those that love to use them, to make sure they fully read an article, understand the context and then when reading the comment use it within the context of the article, not just the headline...
You must have read the article so thoroughly that you skipped over the part where it says:
"...with 84-day notification delay"....
So, who delayed the notification? Definitely not the infected party, but your friends at the AI company!!
-
USAFRet Whatever the specifics, can we all just agree that this was a BadThing?Reply
And if anyone reading this thinks 'no big deal'...please tell us why. -
JamesJones44 Reply
You clearly are not reading the article just the headline...PEnns said:You must have read the article so thoroughly that you skipped over the part where it says:
"...with 84-day notification delay"....
So, who delayed the notification? Definitely not the infected party, but your friends at the AI company!!
The company became aware of this during a review in August.
Most kindergarteners have enough understanding of math to know that June 18 to August is a minimum of 43 days. That means the longest they could have known to notify the Australian government was 41 days. -
JamesJones44 Reply
Yes, I think we all agree here this is a Bad Thing.USAFRet said:Whatever the specifics, can we all just agree that this was a BadThing?
And if anyone reading this thinks 'no big deal'...please tell us why.
There seems to be some misunderstand about questioning the title vs supporting OpenAI's position based on the content in the article, but you can't stop people from hyper focusing on the wrong things over the internet I guess. -
USAFRet Reply
And no harm done....this time.me-three said:The breach was unintentional, and no harm was done.