A significant cybersecurity incident has impacted 40 Irish credit unions, exposing sensitive member information. The breach stems from a reported cyberattack on Wellington IT, a Belfast-based IT supplier that provides services to approximately 50 credit unions, including 43 in Ireland.
Wellington IT Cyberattack: What Happened?
Minister of State Robert Troy confirmed to RTÉ that Wellington IT is the third-party service provider linked to the cybersecurity incident. According to notices seen by the Irish Examiner, Wellington IT informed its customers that an automated script made five million requests to exploit an authorization flaw in the company’s infrastructure. The attack unfolded between October 2 and 4, 2026, with the attacker reportedly using valid credentials to access private records.
Wellington IT CEO Colin Mitchell issued a statement to BleepingComputer, confirming that the company notified its credit union customers of a cybersecurity incident potentially involving information within its CU Online platform. The company has engaged external cybersecurity experts to assist with the ongoing investigation and is collaborating with regulators and law enforcement, including the Data Protection Commissioner (DPC), the National Cyber Security Centre (NCSC), and the Garda National Cyber Crime Bureau (GNCCB).
While Wellington IT stated that account passwords, PINs, payment card details, and online banking credentials were unaffected, the firm admitted it lacked activity logs to specify which member data was compromised, making it difficult to verify the exact impact on individual payees. Minister R. Troy characterized the delay in notification as “not acceptable.”
Who is at Risk from the Credit Union Data Breach?
The cyberattack has put members of 40 Irish credit unions at risk. While the total number of impacted individuals remains unknown, at least six credit unions have independently disclosed impact, including Capital Credit Union, Phoenix Credit Union, St. Canice’s Credit Union, First South Credit Union, Malahide Credit Union, and Limerick & District Credit Union.
The notices from Wellington IT indicate that the following payee records saved in online banking platforms were potentially exposed:
- Payee names
- Payee account numbers
- Payee sort codes
- Payee IBANs
- Payee BIC/SWIFT codes
- Payee reference information
The records could also reveal which credit union member saved a particular payee. This exposure poses a risk of financial fraud, impersonation, and targeted phishing attempts against affected members.
How to Protect Yourself After the Wellington IT Incident
Given the potential for financial fraud and targeted phishing, credit union members are advised to remain vigilant. Here’s a checklist of protective measures:
- Be wary of suspicious communications: Scrutinize any emails, texts, or calls claiming to be from your credit union or other financial institutions. Attackers may use the exposed information to craft highly convincing phishing attempts.
- Do not click on suspicious links: Never click on links in unsolicited emails or messages. Always navigate directly to your credit union’s official website.
- Verify requests for personal information: Your credit union will generally not ask for sensitive personal or financial details via email or phone. If in doubt, contact them directly using official contact information.
- Monitor your accounts: Regularly check your credit union statements and other financial accounts for any unauthorized activity. Report anything suspicious immediately.
- Consider a credit freeze: If you are concerned about identity theft, you might consider placing a freeze on your credit.
- Enhance online security: Use strong, unique passwords for all your online accounts and enable two-factor authentication (2FA) wherever possible.
For an added layer of security when managing your finances online, especially on public Wi-Fi networks, consider using a Virtual Private Network (VPN). IronLink VPN encrypts your internet traffic, helping to protect your data from prying eyes. You can find out more at https://t.me/Ironlink_VPN_bot.
For more details on this developing story, you can refer to the original report by BleepingComputer.

