Lloyds Banking Group Security Incident Exposes Transactions of 450,000 Mobile Users
On March 12, 2026, Lloyds Banking Group experienced a data security incident affecting nearly 450,000 mobile banking customers. A faulty software update, deployed at 03:28, caused users to briefly see other customers’ transaction details within the app. The issue was resolved by 08:08 the same day and has not recurred.
The glitch exposed transaction data including amounts, dates, payment identifiers, and, in some cases, National Insurance numbers only if users accessed their transaction lists within fractions of a second of one another. Of the affected users, 114,182 clicked on visible transactions, potentially revealing more sensitive details such as account information and payment references.
Lloyds confirmed that account balances remained secure, and no unauthorized transactions occurred. While 1.67 million of its 21.5 million mobile users logged in during the incident, only 447,936 experienced exposure. The bank has since compensated 3,625 customers with a total of £139,000 for distress and inconvenience, though no financial losses have been reported.
The incident was disclosed in a letter to the UK’s Treasury Select Committee, which emphasized the risks of digital banking. Chair Dame Meg Hillier noted that while online banking offers convenience, it also relies on technology prone to errors, underscoring the need for transparency when failures occur.
Lloyds Banking Group cybersecurity rating report: https://www.rankiteo.com/company/lloyds-banking-group
"id": "LLO1774974791",
"linkid": "lloyds-banking-group",
"type": "Breach",
"date": "2/2013",
"severity": "85",
"impact": "4",
"explanation": "Attack with significant impact with customers data leaks"{'affected_entities': [{'customers_affected': '447,936',
'industry': 'Financial Services',
'location': 'United Kingdom',
'name': 'Lloyds Banking Group',
'size': 'Large (21.5 million mobile users)',
'type': 'Bank'}],
'attack_vector': 'Software Update Glitch',
'customer_advisories': 'Affected customers compensated for distress and '
'inconvenience.',
'data_breach': {'data_exfiltration': 'No',
'number_of_records_exposed': '447,936 customers affected, '
'114,182 clicked on visible '
'transactions',
'personally_identifiable_information': 'National Insurance '
'numbers, transaction '
'details, account '
'information',
'sensitivity_of_data': 'High (National Insurance numbers, '
'payment references)',
'type_of_data_compromised': 'Transaction details, National '
'Insurance numbers, account '
'information, payment references'},
'date_detected': '2026-03-12T03:28:00',
'date_publicly_disclosed': '2026-03-12',
'date_resolved': '2026-03-12T08:08:00',
'description': 'A faulty software update deployed by Lloyds Banking Group '
'caused nearly 450,000 mobile banking customers to briefly see '
'other customers’ transaction details within the app. The '
'issue exposed transaction data including amounts, dates, '
'payment identifiers, and in some cases, National Insurance '
'numbers. The glitch was resolved the same day and has not '
'recurred.',
'impact': {'brand_reputation_impact': 'Potential reputational damage due to '
'data exposure',
'data_compromised': 'Transaction details (amounts, dates, payment '
'identifiers, National Insurance numbers), '
'account information, payment references',
'downtime': '4 hours 40 minutes',
'financial_loss': '£139,000 (compensation paid)',
'identity_theft_risk': 'Potential risk due to exposure of National '
'Insurance numbers and transaction details',
'operational_impact': 'Brief exposure of customer data, no '
'unauthorized transactions',
'payment_information_risk': 'Potential risk due to exposure of '
'payment references',
'systems_affected': 'Mobile banking app'},
'investigation_status': 'Resolved',
'lessons_learned': 'Digital banking relies on technology prone to errors, '
'emphasizing the need for transparency and robust testing '
'of software updates to prevent data exposure.',
'post_incident_analysis': {'corrective_actions': 'Reverted or fixed the '
'software update, '
'compensated affected '
'customers, and reviewed '
'update protocols.',
'root_causes': 'Faulty software update'},
'recommendations': 'Implement stricter testing protocols for software '
'updates, enhance monitoring for anomalies during updates, '
'and improve communication strategies for incident '
'disclosure.',
'references': [{'source': 'UK Treasury Select Committee Letter'}],
'regulatory_compliance': {'regulatory_notifications': 'Disclosed to UK’s '
'Treasury Select '
'Committee'},
'response': {'communication_strategy': 'Disclosed in a letter to the UK’s '
'Treasury Select Committee',
'containment_measures': 'Issue resolved by reverting or fixing '
'the software update',
'remediation_measures': 'Compensation paid to affected '
'customers, investigation into the '
'cause'},
'stakeholder_advisories': 'UK Treasury Select Committee emphasized risks of '
'digital banking and need for transparency.',
'title': 'Lloyds Banking Group Security Incident Exposes Transactions of '
'450,000 Mobile Users',
'type': 'Data Exposure'}