
Top-Secured cyber watch: independent analysis based on the official statement of Wellington IT and on the press. Top-Secured is not affiliated with this company and will never ask you for your bank details or passwords.
A security flaw at Wellington IT, a software supplier to Irish credit unions, exposed payee details of members using its mobile app. The sector says the flaw is fixed and that there is no evidence member funds were accessed; the number of people affected is not yet known.
What happened
Irish credit unions are dealing with a data incident at one of their software suppliers, Wellington IT, which runs the mobile app used by members of a number of them. On 17 November 2026, the Irish League of Credit Unions (ILCU) and two other sector bodies said they were aware of an IT security incident at a service provider to certain credit unions, that the flaw involved had been closed and that, as far as they understood, member accounts and balances had not been compromised. On 19 November, after a meeting organised by a Minister of State with the supplier, the ILCU reported what Wellington IT had told participants: the vulnerability has been identified and fixed, the incident concerns users of the Wellington IT mobile app and is limited to payee details, there is no evidence of access to member funds or of fraudulent account activity, and external cybersecurity specialists have been brought in to review the incident, its systems and its controls.
Who is affected, and the timeline
No figure for affected members has been published: the ILCU says establishing the exact number of accounts and users is a priority. According to The Record, the Irish Data Protection Commission has received more than 40 breach notifications from credit unions that use Wellington IT as a processor, and the UK Information Commissioner’s Office has started to receive reports from credit unions too. The same outlet reports that, according to the ILCU’s chief executive speaking to RTÉ, the attack took place in early October, that Wellington says it closed the vulnerability on 6 October, and that credit unions were first notified on 16 November. Wellington IT did not answer The Record’s request for comment. The technical cause has not been made public.
What to do now
- If you are a member: never give a PIN, password or one-time code to anyone, even someone who says they are calling from your credit union; hang up and call back on a number you have checked yourself.
- List the suppliers that hold your customers’ data and check that each contract sets a short deadline to tell you about an incident, so you can meet your own 72-hour GDPR deadline.
- Ask the supplier for the scope in writing: which data, which period, which access logs, and what was fixed.
- Warn your customers quickly when contact or payment data leak: exposed payee details make convincing payment scams easy.
- On your own APIs, check that each request only returns data belonging to the logged-in user, and alert on clients sending unusual volumes of requests.
Our take
Going by the timeline reported in the press, several weeks passed between the attack and the first notice to customers. When a supplier processes your customers’ data, its detection and notification speed becomes yours: write it into the contract and test it.
Sources
- Irish League of Credit Unions — Credit union representatives welcome meeting with Wellington IT
- Irish League of Credit Unions — Cyber incident update
- The Record — Dozens of credit unions hit by supplier breach that went unnoticed for six weeks
How we choose, verify and write our analyses →
The way in was a third party. Check what your suppliers expose publicly — no intrusion, public information only:
Worried your servers are exposed? Our team audits, patches and monitors Linux and cloud infrastructure 24/7.
Talk to an expert Our managed server services →

