The short version
- The breach. Wellington IT, a Belfast supplier whose services are used by about 50 credit unions, was attacked between 2 and 4 October 2026. Notices it sent to customers, seen by the Irish Examiner, describe an automated script that made five million requests exploiting an authorisation flaw, with private records reached using valid credentials.
- Scale. Minister of State Robert Troy told RTÉ that about 40 credit unions in Ireland are affected; the supplier serves roughly 50. At least six credit unions have independently disclosed impact. The number of individual members involved is unknown.
- What was exposed. Saved payee records: payee name, the member's nickname for the payee, IBAN, BIC, account number, sort code, payee address, and payment references; the records could also reveal which member saved that payee. Passwords, PINs, card details and online banking credentials were not affected.
- Notification delay. Troy described the time Wellington IT took to tell credit unions as not acceptable. The company said it lacks activity logs that would show which member data was compromised.
Timeline
| Date | Event |
|---|---|
| 2-4 Oct | Attack on Wellington IT infrastructure; an automated script makes five million requests exploiting an authorisation flaw, and private records are accessed with valid credentials. |
| 18 Nov | BleepingComputer reports the breach, the notices Wellington IT sent to customers, and the minister's confirmation of Wellington IT's role. |
What happened
Wellington IT is a Belfast-based IT provider used by about 50 credit unions, 43 of them in Ireland. The company has not publicly disclosed a security incident. According to the Irish Examiner, which saw the breach notices sent to customers, an automated script made five million requests to exploit an authorisation flaw in the company's infrastructure between 2 and 4 October 2026, and the attacker reached private records using valid credentials.
The company said it lacked activity logs that would identify which member data was compromised, so it cannot verify the impact on individual payees. Minister of State Robert Troy confirmed to RTÉ that Wellington IT is the third-party provider behind the incident. BleepingComputer said it had contacted the company and would update its article with any response.
Who is affected and what was exposed
Troy put the number of affected credit unions in Ireland at about 40. Six have described the impact themselves: Capital Credit Union, Phoenix Credit Union, St. Canice's Credit Union, First South Credit Union, Malahide Credit Union and Limerick & District Credit Union. Some said members' login credentials and funds were untouched; others said they were still working out what had been exposed.
The records listed as potentially exposed are the payees members saved in online banking: the payee's name, the member's own nickname for them, IBAN, BIC, account number, sort code, payee address, and the payment references entered; the records could also reveal which member saved that payee. The data could support impersonation, targeted phishing and payment fraud, and members were urged to stay alert. Passwords, PINs, card details and online banking credentials were not affected, and the total number of individuals affected is not known.
Why the supplier matters
Wellington IT, an IT provider used by dozens of credit unions, was attacked, exposing members' data across multiple credit unions. The delay in notification drew criticism from a government minister, and the company said missing logs meant it could not verify the impact on individual payees.
What is not known yet
- Who carried out the attack, and whether they were an outside party or someone with existing access.
- How many individual members' payee records were exposed.
- How the attacker obtained the valid credentials used to reach private records.
- When Wellington IT detected the intrusion, and why notification to credit unions did not happen sooner.
- Whether the authorisation flaw has been fixed, and whether anything beyond payee records was accessed.
What to do
If you are a member of a credit union served by Wellington IT
- Review the payees saved in your online banking and report any entry you do not recognise to your credit union.
- Treat unexpected calls, emails or texts that mention your payee details as suspicious, and call the credit union back on a number you already hold.
- Do not treat your password, PIN or card as compromised because of these notices; the credit unions say those were not affected.
If you run a credit union or buy IT from a shared provider
- Ask the provider which payee records were accessed and for the log evidence behind that answer.
- Put contractual requirements in place for activity logging detailed enough to show which customer records an authenticated session read, and for notification deadlines.
- Verify changes to member payee details through a separate channel before payments go out.
- Monitor for floods of automated requests against authorisation endpoints.
For everyone else
- Ask your suppliers what access logs they keep and how quickly they would tell you about an intrusion, because records you never stored yourself can still be exposed through them.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.