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

# ION Trading security incident

The retained public source documents this consequence of the ION Trading incident: Disrupted derivatives clearing/settlement at major banks/brokers globally.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Financial software
- **Operational impact:** Disrupted derivatives clearing/settlement at major banks/brokers globally
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

The reviewed public record documents a cybersecurity incident involving ION Trading in 2023. It does not establish the initial access path with enough specificity to describe it here. [1](#source-1)

The documented consequence was: Disrupted derivatives clearing/settlement at major banks/brokers globally. [1](#source-1)

## Impact

- Documented impact: Disrupted derivatives clearing/settlement at major banks/brokers globally. [1](#source-1)
- No financial loss, ransom amount, recovery cost, or regulatory penalty is established by the reviewed source evidence.

## Timeline

### January 31, 2023 — Documented public update

The [Cleared Derivatives Cyber Event](https://iongroup.com/press-release/markets/cleared-derivatives-cyber-event/) 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 reviewed source does not establish a sufficiently specific initial-access vector. The article therefore does not infer credentials, malware, a vulnerability, or a social-engineering path.

### 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 retained source describes containment action intended to limit further access or disruption. [1](#source-1)

This account is bounded to [Cleared Derivatives Cyber Event](https://iongroup.com/press-release/markets/cleared-derivatives-cyber-event/). 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/ion-trading-security-incident-2023/stix.json>)

## Sources

Primary source records used to research this incident.

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

### Cleared Derivatives Cyber Event

official · ION Group

<https://iongroup.com/press-release/markets/cleared-derivatives-cyber-event/>

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

Review the supporting structured claims.

1. **Occurred At · 100% confidence · current**  
   Documented public update: 2023-01-31
2. **Resulted In · 100% confidence · current**  
   ION Trading security incident: The reviewed source documents the ion trading security incident involving ION Trading.
3. **Resulted In · 90% confidence · current**  
   ION Trading security incident: The retained source describes containment action intended to limit further access or disruption.
4. **Affected Organization · 100% confidence · current**  
   ION Trading security incident: ION Trading
5. **Resulted In · 83% confidence · current**  
   ION Trading security incident: Disrupted derivatives clearing/settlement at major banks/brokers globally.

</details>