Wellington IT Breach: Credit Union Payee Data Exposed
About 40 Irish credit unions say saved payee details were accessed through their shared technology supplier, Wellington IT. Passwords and card details were not affected. What MSPs serving financial clients should do now.
About 40 Irish credit unions have been told that saved payee details in their online banking were accessed without authorization through a shared technology supplier, Wellington IT [2]. One affected credit union says the incident involved "unauthorised access to information associated with saved payment beneficiaries/payees", that the vulnerability has been fixed, and that passwords, PINs, card details and login credentials were not affected [1]. Ireland's minister of state with responsibility for credit unions said the breach happened in October and called the delay in telling the credit unions "not acceptable" [2]. If you run IT for a financial-services client, or provide a shared platform to several clients yourself, this is the case to learn from.
What has been confirmed
- St. Canice's Credit Union (17 November): It was told on 16 November of a potential cybersecurity incident at an external IT supplier, affecting approximately 50 credit unions that use the same supplier. The exposed data relates to payees members had saved: the payee's account name and nickname, IBAN, BIC, account number and sort code, address where recorded, and payment references. Because saved payees belong to the member who created them, the information can be linked to that member [1].
- Minister Robert Troy (18 November): About 40 credit unions, roughly a quarter of the country's total, are affected. The breach happened "sometime in October", Wellington IT only told the credit unions in recent days, and no financial loss had been reported to date [2].
- Wellington IT (18 November): Its chief executive said the company alerted customers once it confirmed the potential risk to customer data, has brought in external cybersecurity experts, and is working with the Data Protection Commission, the National Cyber Security Centre and the Garda National Cyber Crime Bureau [2].
- Affected credit unions, as reported: Attackers exploited a vulnerability in the provider's online banking platform between 2 and 4 October, and it was closed on 6 October [3].
Reports put the number of affected credit unions at about 40 [2] or approximately 50 [1]; neither figure is final. Nobody has named an attacker.
Why this matters to MSPs
This is a supplier breach. One provider's platform served dozens of financial institutions, so one vulnerability reached all of them at once, and most of the delay that drew criticism was between the provider finding the problem and its customers hearing about it [2][3]. An MSP is in the same position as that provider. The data taken also matters: payee names, account numbers and payment references are exactly what a fraudster needs to make a fake "your bank" call or a payment-redirection email sound genuine [1].
What to do now
- Warn financial-services clients about follow-on fraud. Tell staff and, where relevant, their members or customers to expect calls and messages that quote real account details, and to verify through a known number. A genuine institution will never ask anyone to move money to a "safe account" [1].
- Map shared platforms. List every system you or a supplier run for more than one client, and check how a single flaw in it would reach each of them.
- Check your own notification clock. Write down how quickly you would tell a client about a suspected incident on a platform you run for them, who decides, and who in each client gets the call. Then make it faster.
- Review supplier contracts. For clients in regulated sectors, confirm their suppliers are obliged to report suspected incidents within a set time.
- Watch for payment-change requests. Tighten checks on any request to change a supplier's or payee's bank details, using a call-back to a known contact.
Frequently asked questions
What data was exposed?
Information about saved payees: account names and nicknames, IBAN, BIC, account number, sort code, address where recorded, and payment references, which can be linked to the member who saved them [1].
Were passwords or card details taken?
No. The affected credit union says online banking passwords, PINs, payment card details and login credentials were not affected, and that the data cannot be used to log in or reach members' money [1].
How many credit unions are affected?
The minister said about 40 [2]; one affected credit union's notice said approximately 50 use the same supplier [1].
When did it happen?
The minister said October [2]. Affected credit unions have reported that the vulnerability was exploited between 2 and 4 October and closed on 6 October [3].
Who is investigating?
Wellington IT says it is working with the Data Protection Commission, the National Cyber Security Centre and the Garda National Cyber Crime Bureau [2].
Is money at risk?
No financial loss had been reported as of 18 November [2]. The bigger risk is fraud that uses the exposed details to sound convincing [1].
How Vijilan helps
Vijilan's SOC watches the identity, endpoint and cloud activity of the platforms MSPs run for their clients, around the clock, with machine speed where speed wins and a human approving the actions that carry real risk. ThreatDefend™ runs that on CrowdStrike Falcon with Vijilan's analysts behind it. Talk to us.
Sources
Threat notes, once a week
What our SOC actually saw this week: new attack patterns, the detections we shipped against them, and what it means if you run an MSP. Written by the analysts, not by marketing.
See what 24/7 looks like when the SOC actually acts.
Book a 20-minute platform walkthrough: no slide deck, just the console.
Book a walkthrough →