---
title: "Latitude Financial security incident"
description: "What the retained public evidence establishes about the Latitude Financial 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/latitude-financial-security-incident-2023"
markdown_url: "https://www.ally.security/incidents/latitude-financial-security-incident-2023.md"
stix_url: "https://www.ally.security/incidents/latitude-financial-security-incident-2023/stix.json"
---

# Latitude Financial security incident

The retained public source describes the Latitude Financial incident as Compromised employee credentials at two third-party vendors. Other material details remain unresolved.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Consumer finance (Australia/NZ)
- **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 2023, Latitude Financial experienced an incident in its consumer finance (australia/nz) environment. The retained source describes the attack path as follows: Compromised employee credentials at two third-party vendors. [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.

## Threat Group & Attack Vector

The retained source describes the attack path as follows: Compromised employee credentials at two third-party vendors. 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

- [T1078 — Valid Accounts](https://attack.mitre.org/techniques/T1078/) — mapped from the cited behavior. [1](#source-1)

## Response

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

This account is bounded to [Statement of notification](https://www.latitudefinancial.com.au/cyber-statement-of-notification/). 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/latitude-financial-security-incident-2023/stix.json>)

## Sources

Primary source records used to research this incident.

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

### Statement of notification

official · Latitude Financial

<https://www.latitudefinancial.com.au/cyber-statement-of-notification/>

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

Review the supporting structured claims.

1. **Used Attack Technique · 90% confidence · current**  
   Latitude Financial security incident: https://attack.mitre.org/techniques/T1078/
2. **Affected Organization · 100% confidence · current**  
   Latitude Financial security incident: Latitude Financial
3. **Resulted In · 89% confidence · current**  
   Latitude Financial security incident: Compromised employee credentials at two third-party vendors.
4. **Resulted In · 100% confidence · current**  
   Latitude Financial security incident: The reviewed source documents the latitude financial security incident involving Latitude Financial.

</details>