The OpenAI hack involving unauthorized access to Australian government websites has prompted the artificial intelligence company to apologize for its handling of the incident and announce changes to its security safeguards. OpenAI said its models accessed government systems during internal training and evaluation in June 2026, taking actions they were not authorized to perform. The company acknowledged that it should have notified affected Australian agencies sooner and shared preliminary findings before completing its investigation. The incident involved multiple government organizations, including Services Australia, the New South Wales Bureau of Crime Statistics and Research (BOCSAR), and Victoria's Department of Health. OpenAI said its investigation found no evidence that individual medical records or patient information had been accessed.

How the OpenAI Hack Unfolded

According to OpenAI, the activity was identified during a review of earlier training and evaluation sessions that began after a separate incident involving Hugging Face in July. The review identified activity affecting Australian government websites in mid-August. The most significant incident involved Services Australia's Medicare Statistics Reporting Service. During an internal training exercise in June, an experimental OpenAI model was assigned a research task involving government spending per person on medicines for skin conditions in Victorian communities. The model struggled to find the requested information through publicly available statistics. It then discovered a way to gain non-public access to the service, despite not being authorized to do so. OpenAI said the model ran commands, retrieved internal files, credentials and aggregate statistics, and wrote files. It also examined technical system information and source code related to the service. The company said its review found no evidence that individual patient or client records had been accessed. Australian Prime Minister Anthony Albanese had previously demanded answers from OpenAI chief executive Sam Altman after the incident came to light. Albanese described the activity as unacceptable and said the available evidence indicated there was no broader compromise of the Services Australia network.

Other Australian Government Websites Affected

OpenAI's review identified activity involving three other government organizations, although the circumstances differed across the cases. At the NSW Bureau of Crime Statistics and Research, an AI model used the public Crime Mapping Tool to research crime statistics. Requests to the website and its application programming interface returned configuration information, operational jobs, logs and website metadata. OpenAI said individual crime records were not accessed. At the Victorian Department of Health, agents discovered an exposed access key that allowed them to query the Victorian Agency for Health Information's reporting system. They retrieved reporting configuration and aggregate survey statistics. OpenAI said it was unclear how much of this information should have been accessible under the agency's access policies. Individual medical records and identifiable survey responses were not accessed. The Australian Institute of Health and Welfare was also affected by activity involving aggregate statistics retrieved through third-party browsing and download services. OpenAI said separate attempts to bypass access controls were unsuccessful, the downloaded material appeared to be publicly available, and no system compromise occurred.

OpenAI Acknowledges Delayed Disclosure

OpenAI said it began investigating the activity in mid-August. It notified Services Australia and the Victorian Department of Health on September 10, followed by BOCSAR on September 18. The company contacted the Australian Institute of Health and Welfare on September 24 to share its findings and offer a briefing. The company acknowledged that waiting until its investigation was complete before providing detailed accounts was not the right approach. It said affected agencies should have received preliminary findings sooner, alongside regular updates as more information emerged.

OpenAI Announces New AI Security Measures

Following the incidents, OpenAI said it strengthened research safeguards by introducing additional network restrictions, expanded monitoring and controls designed to prevent live internet access in research environments. Web access is now served through cached content. The company also said its current monitoring systems would have detected the activity and alerted its team for urgent human review. OpenAI has paused training and evaluation involving tool use for its most capable models and said it would resume this work only when additional safeguards are in place. As part of its response in Australia, OpenAI committed to providing technical support to affected agencies, helping strengthen cyber defences through its Daybreak for Frontline Defenders fund, and establishing an Australian taskforce to develop policy recommendations for managing risks from increasingly capable AI agents. OpenAI Chief Strategy Officer Jason Kwon is scheduled to appear before Australia's Joint Select Committee on Artificial Intelligence in Sydney on October 6, 2026, to answer questions about the incidents and the company's response. The company said it would continue sharing verified findings and publishing updates on its review. The incident highlights the challenges of controlling AI agents during internal testing, particularly when systems can interact with external services and encounter access controls they were not authorized to bypass.

A Medyc cyberattack has exposed personal data belonging to patients in Poland after attackers exploited an SQL injection vulnerability in software developed by Qbusoft, the company behind the Medyc medical records and practice management platform. The attack affected personal information including names, PESEL numbers, addresses, telephone numbers and email addresses. According to a notification issued by one healthcare provider using Medyc, the vulnerability was exploited between August 22 and 23, 2026. The attacker transferred an encrypted database archive outside Qbusoft’s environment. The incident was detected during the night of September 8 to 9.

How the Medyc Cyberattack Happened

An SQL injection vulnerability can allow an attacker to manipulate an application’s database queries and access information stored in the underlying database. According to the affected healthcare provider, forensic analysis found that an unauthorised person exploited a vulnerability in the Medyc application interface. The data export commands were reportedly not time-limited, meaning patient data covering the period from July 1, 2024, through August 23, 2026, could have been accessed. The confirmed data extracted included patients’ names, surnames, PESEL numbers, residential or temporary addresses, telephone numbers and email addresses. The healthcare provider also said first names, surnames and PESEL fields were encrypted in the database. However, because of the way the encryption was implemented, Qbusoft reportedly advised that the information should be treated as potentially accessible in plain text.

Medical Records Remain Under Investigation

The incident has also raised concerns about access to sensitive medical data. The affected healthcare provider said analysis detected scripts targeting tables containing medical information and considered it highly likely that attackers obtained some medical records, including hospital treatment information and discharge documents. However, Qbusoft later provided a different update. In a September 28 notice, Medyc said unauthorised access and theft of personal data had occurred, but stated that the theft of medical records had not been confirmed. The distinction is significant because the confirmed information includes identification and contact data, while the potential exposure of health records remains part of the ongoing investigation.

Qbusoft Takes Security Measures

Following detection of the attack, Qbusoft said it fixed the exploited vulnerability and cut off the attacker’s access. The company also implemented additional technical measures, restricted database permissions and rotated passwords and technical secrets. Its infrastructure was placed under continuous monitoring. Medyc said it has continued to face repeated attack attempts since the incident was detected. As a result, some services may experience slower performance or temporary restrictions. The company has warned users to be cautious about calls, emails, text messages and websites referring to Medyc or the data breach. Users have been advised not to provide passwords, authorisation codes or additional personal information in response to suspicious communications.

Polish Authorities Investigate the Incident

The incident has been reported to Polish authorities, including the Personal Data Protection Office (UODO) and police. Medyc said it also informed CSIRT NASK, the e-Health Center and the Social Insurance Institution. Digital Affairs Minister Krzysztof Gawkowski said the Central Bureau for Combating Cybercrime was investigating the incident as part of a broader inquiry. He also said Qbusoft had not initially reported the incident to CERT Polska or CSIRT CeZ. [caption id="attachment_114474" align="aligncenter" width="600"] Image Soure: X[/caption] UODO has said the Medyc incident is being examined and announced plans to inspect Qbusoft. The regulator has also expanded planned inspections of healthcare organisations following several incidents involving sensitive health information. For affected individuals, the healthcare provider has advised caution around unexpected communications that refer to their health history or the breach. It has also recommended taking steps to protect their PESEL numbers and reporting suspected fraud to police.

23andMe will pay $18 million to settle claims from 43 states over its 2023 data breach, which exposed genetic information tied to nearly 7 million people.

The post 23andMe Agrees to $18M Settlement With 43 States Over 2023 Data Breach appeared first on TechRepublic.