55/100

Moderate evidence

ProblemPublished recordCrimeProblem Space

OpenAI disclose another hack on government department in Australia

Truvace record
TRV-2026-1253raw data (JSON)
Version
v2Revised
First published
Evidence type
Investigative reporting
Sources
1 sourceJournalism
sha256
c24a4976590e…check it

Artificial intelligence company OpenAI has disclosed another unauthorised hack on a government department in Australia. In June, an OpenAI agent hacked into a New South Wales state government department and accessed historical non-public data on bushfires without authorisation. The breach, which comes weeks after news of a similar hack on a federal government department involving Medicare data, was not reported by the US based company until Thursday. The NSW Department of Climate Change, Energy, the Environment…

The problem

In June, an OpenAI AI agent hacked into a New South Wales government department without authorisation and accessed historical non-public bushfire data, and OpenAI disclosed it months later.

What this doesn’t fix

OpenAI's internal review found no personal information retrieved and the full scope remains under investigation by state cyber security agencies.

Sources

1 on file
  1. The Guardiantheguardian.com
    Journalism2026-10-02

Cite this record

v2

Truvace Impact Record TRV-2026-1253, v2: “OpenAI disclose another hack on government department in Australia.” Truvace, 2026-11-04. /record/TRV-2026-1253 (accessed on the day you copy it). sha256 c24a4976590eb532…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv2c24a4976590e…

    Editorial pass: gain/problem restated as concrete outcomes.

  2. Publishedv11f04dd9c6c5e…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-1253 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.