- SMB/SME
- Enterprise
· ASC Editorial Team
Your Supplier Held Your Customers' Payees: Lessons From the Irish Credit Union Breach
In early October 2026, attackers exploited a flaw in the online banking platform that Wellington IT, a Belfast-based supplier, runs for credit unions in Ireland. According to affected credit unions, the attack ran from 2 to 4 October and the flaw was closed on 6 October. It became public on 17 November. Ireland's Minister of State Robert Troy says about 40 credit unions, roughly a quarter of those in Ireland, are affected.
What was taken is members' saved payees: the people and businesses that members pay. The records include payee names, IBANs, BICs, account numbers, sort codes, addresses and payment references, and they can be linked to the members who created them. Passwords, PINs and balances are reported as not affected, and the minister said no credit union or member had lost money.
The sharpest criticism is of the delay. Many credit unions were told only in recent days, and the minister called that "not acceptable". Wellington IT says it told its customers "as soon as we confirmed the potential risk to customer data". It hasn't said what the flaw was or how the attack was found, and we won't guess. Reports so far concern credit unions in the Republic of Ireland.
Two lessons apply to any firm whose online service runs on a supplier's platform, not only to credit unions.
The first is the fraud risk. Payee data is a fraudster's script. Someone who knows who you pay, the reference you use and the payee's bank can make a call or email sound genuine: a payment has failed, please send it again to this account. The advice to members has been direct: never move money because of an unexpected call, text or email, even when the caller knows your details. When customers' data is exposed, they need that warning early and plainly.
The second is the delay. Under the GDPR, which applies in Ireland and in the UK as UK GDPR, a supplier processing data for you must tell you of a breach "without undue delay", and you then have 72 hours to report it to the regulator. But you can't warn customers or report anything until the supplier tells you. How quickly that happens is set in the contract, before an incident, not during one.
We wrote about a supplier's platform used as a route into a bank in the Arkéa attack. Here the supplier's platform was the target itself, and the customer data was already on it.
Three checks follow.
First, the contract. For each supplier that holds customer data, how quickly must it tell you of a suspected breach, in hours, and who does it tell? "Without undue delay" on its own leaves the timing to the supplier.
Second, the data. What does each platform hold about your customers beyond their accounts, such as payees, contacts or documents? Payee lists aren't login details, but they're exactly what payment fraud needs.
Third, the message. Draft a customer warning now about fraudulent calls and requests to change bank details, so you can send it the day a supplier tells you.
If a supplier found tomorrow that your customers' data had been taken a month ago, how soon would your contract make them tell you?
Source: RTÉ: Credit union data breach
Get Insights by email
A short round-up of new articles every Monday morning. Nothing else.