Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • I am certain there would be better guardrails if there were some actual consequences for the people who built these products.
  • I've got the feeling that the definition of "hacked" can get somewhat stretched.
  • If it was the Australian Medicare Statistics Reporting Service on June 18th it may have been part of this incident: https://collusion.wiki/ - the bulk of that coordinated activity was between 16th and 21st of June, and we know they were hitting UK government data sites.

    I had a dig around in the data that they published on that site and found references to www.aihw.gov.au and viz.aihw.gov.au and vizprod.aihw.gov.au

  • I remember once at Google someone complained that GoogleBot hacked them and deleted their data, and it turned out that GoogleBot was just crawling the pages, and they had unfortunately designed their website so that there was no authentication, page URLs were generally secret, and GET requests to certain URLs were treated as requests to delete data. So once one URL leaked the site got crawled and a lot of data was deleted....
  • The fact the incident occurred in June and OpenAI only notified the Australian government on September 10 is a major issue. Hacking a nation-state's universal healthcare system is about as serious as it gets, yet OpenAI seem quite relaxed about the whole thing (presuming they have known about it for some time).
  • > He said the agent had accessed files that were publicly available as well as material that was not intended for public access.

    “Not intended”. I’ll bet you whatever this was it wasn’t even secured, it was just hosted somewhere openly.

  • Zero technical details on what the "hack" actually was. Willing to bet it was something as stupid as the data being accessible by changing the query parameter, and rather than own up to their own shoddy security (no doubt built by an offshore contractor) they are going to blame the one who found and reported the bug.

Explore Birbla archives