---
title: "Optus security incident"
description: "What the retained public evidence establishes about the Optus incident, its attack path, impact, and response."
incident_type: "Cybersecurity incident"
status: "active"
last_modified: "2026-09-19"
canonical_url: "https://www.ally.security/incidents/optus-security-incident-2022"
markdown_url: "https://www.ally.security/incidents/optus-security-incident-2022.md"
stix_url: "https://www.ally.security/incidents/optus-security-incident-2022/stix.json"
---

# Optus security incident

The retained public source describes the Optus incident as Exposed, unauthenticated API endpoint. Other material details remain unresolved.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Telecom (Australia)
- **Operational impact:** The reviewed source does not establish a precise operational or data impact
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

In Sept 2022, Optus experienced an incident in its telecom (australia) environment. The retained source describes the attack path as follows: Exposed, unauthenticated API endpoint. [1](#source-1)

## Impact

- The reviewed source does not establish a precise affected-person count, data scope, or operational consequence.
- No financial loss, ransom amount, recovery cost, or regulatory penalty is established by the reviewed source evidence.

## Timeline

### March 10, 2023 — Documented public update

The [OAIC opens investigation into Optus over data breach](https://www.oaic.gov.au/news/media-centre/oaic-opens-investigation-into-optus-over-data-breach) records the incident facts used in this briefing. [1](#source-1)

### September 19, 2026 — Briefing updated

This briefing was last reviewed and updated on September 19, 2026.

## Threat Group & Attack Vector

The retained source describes the attack path as follows: Exposed, unauthenticated API endpoint. The canonical record does not add intrusion steps beyond those supported by the source. [1](#source-1)

### Actors

- No threat actor group has been identified in the reviewed public evidence.

### TTPs

- No specific MITRE ATT\&CK technique is currently mapped for this case.

## Response

The reviewed source does not describe containment, notification, or restoration steps in enough detail to summarize them responsibly.

This account is bounded to [OAIC opens investigation into Optus over data breach](https://www.oaic.gov.au/news/media-centre/oaic-opens-investigation-into-optus-over-data-breach). Details absent from that evidence are left unresolved rather than inferred. [1](#source-1)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/optus-security-incident-2022/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### OAIC opens investigation into Optus over data breach

regulatory · Office of the Australian Information Commissioner

<https://www.oaic.gov.au/news/media-centre/oaic-opens-investigation-into-optus-over-data-breach>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 84% confidence · current**  
   Optus security incident: Exposed, unauthenticated API endpoint.
2. **Resulted In · 100% confidence · current**  
   Optus security incident: The reviewed source documents the optus security incident involving Optus.
3. **Affected Organization · 100% confidence · current**  
   Optus security incident: Optus
4. **Occurred At · 100% confidence · current**  
   Documented public update: 2023-03-10

</details>