---
title: "Santander Bank security incident"
description: "What the retained public evidence establishes about the Santander Bank 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/santander-bank-security-incident-2024"
markdown_url: "https://www.ally.security/incidents/santander-bank-security-incident-2024.md"
stix_url: "https://www.ally.security/incidents/santander-bank-security-incident-2024/stix.json"
---

# Santander Bank security incident

Stolen credentials were used against a Snowflake customer account that did not enforce MFA. Employee and customer data across multiple countries exposed.

Last modified Sep 19, 2026 · 1 source

## Summary

- **Environment:** Financial services
- **Operational impact:** Employee and customer data across multiple countries exposed
- **Financial impact:** No financial figure is established by the reviewed source evidence

## What happened

In 2024, Santander experienced an incident in its financial services environment. The retained source describes the attack path as follows: Stolen credentials were used against a Snowflake customer account that did not enforce MFA. [1](#source-1)

The documented consequence was: Employee and customer data across multiple countries exposed. [1](#source-1)

## Impact

- Documented impact: Employee and customer data across multiple countries exposed. [1](#source-1)
- 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: Stolen credentials were used against a Snowflake customer account that did not enforce MFA. 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 on unauthorized database access](https://www.santander.com/en/stories/statement). 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/santander-bank-security-incident-2024/stix.json>)

## Sources

Primary source records used to research this incident.

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

### Statement on unauthorized database access

official · Santander

<https://www.santander.com/en/stories/statement>

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

Review the supporting structured claims.

1. **Used Attack Technique · 90% confidence · current**  
   Santander Bank security incident: https://attack.mitre.org/techniques/T1078/
2. **Affected Organization · 100% confidence · current**  
   Santander Bank security incident: Santander
3. **Resulted In · 100% confidence · current**  
   Santander Bank security incident: The reviewed source documents the santander bank security incident involving Santander.
4. **Resulted In · 86% confidence · current**  
   Santander Bank security incident: Employee and customer data across multiple countries exposed.
5. **Resulted In · 84% confidence · current**  
   Santander Bank security incident: Stolen credentials were used against a Snowflake customer account that did not enforce MFA.

</details>