![\"\"\/](\"https:\/\/securityaffairs.com\/wp-content\/themes\/security_affairs\/images\/user-icon.svg\"){kind=icon}
Pierluigi Paganini<\/a>\n\t\t\t\t\t\t\t
![\"\"\/](\"https:\/\/securityaffairs.com\/wp-content\/themes\/security_affairs\/images\/clock-icon.svg\"){kind=icon}
March 31, 2026<\/p>\n\t\t\t\t\t\t![\"\"\/](\"https:\/\/www.europesays.com\/britain\/wp-content\/uploads\/2026\/05\/image-96.png\")
<\/p>\n
Lloyds Banking Group data incident exposed transactions of ~450,000 mobile banking users due to a faulty update.<\/p>\n
A faulty software update at Lloyds Banking Group exposed transaction details of nearly 450,000 mobile banking users on March 12. The issue caused some customers to see other users\u2019 account activity within the app, prompting the bank to disclose a data security incident affecting current account information.<\/p>\n
According to Lloyds Banking Group, transactions were exposed only if users accessed their transaction lists at nearly the same time. A customer would need to view their own transactions within fractions of a second of another user to see or be seen. The faulty update, rolled out on March 12 at 03:28, was fixed by 08:08 and has not recurred. Exposed data could include amounts, dates, payment identifiers, and potentially National Insurance numbers.<\/p>\n
\u201cUp to 447,936 Lloyds, Halifax and Bank of Scotland customers saw other people\u2019s transactions or had their data shared with other users during an IT glitch on 12 March, according to a letter published by the Treasury Select Committee.\u201d Lloyds\u00a0told<\/a>\u00a0the UK\u2019s Treasury Committee. \u201c114,182 people clicked on other people\u2019s transactions when they became visible and then may have been shown more detailed information such as account details, national insurance numbers and payment references.\u201d<\/p>\n The banking group reported that some exposed transactions involved payments to non-Lloyds customers. The company pointed out that the account balances remained unaffected, and no unauthorized actions were possible. Customers only saw other users\u2019 data briefly, and the information alone was insufficient to commit fraud. During the incident, 1.67 million of 21.5 million mobile users logged in, with 447,936 experiencing transaction exposure or having their own transactions briefly visible to others.<\/p>\n \u201cIn total, \u00a3139,000 of compensation has been paid out to 3,625 customers for distress and inconvenience. No customers have, so far, been identified as suffering financial loss.\u201d concludes Lloyds.<\/p>\n \u201cModern banking methods mean we can now perform a variety of tasks on our phones in a matter of seconds, and almost anywhere.\u201d said Chair of the Treasury Committee, Dame Meg Hillier. \u201cWhat this incident brings into focus is the fact that there is a trade-off. By moving more interactions with our bank online, we place our faith in technology which can suffer unpredictable errors. It\u2019s critical that consumers understand this, and that\u2019s why my Committee continues to push banks to be transparent when things go wrong.\u201d<\/p>\n Follow me on Twitter:\u00a0@securityaffairs<\/a>\u00a0and\u00a0Facebook<\/a>\u00a0and\u00a0Mastodon<\/a><\/p>\n Pierluigi\u00a0Paganini<\/a><\/p>\n (SecurityAffairs<\/a>\u00a0\u2013\u00a0hacking,\u00a0Lloyds)<\/p>\n \t\t\t\t\t\t\t\t\t\t\t