A cyberattack targets a server, exposing personal data while threatening banks across the Netherlands.
Around 40 Irish credit unions are dealing with a breach at a company most of their members have never heard of. Wellington IT is a Belfast software supplier, and it sits behind the online banking that many members use. Minister of State Robert Troy confirmed to RTÉ that Wellington IT is the third-party provider linked to the incident, which exposed data from about 40 Irish credit unions. The case is a textbook example of supply-chain risk. The vendor's customers may have to notify regulators and members about an event they didn't see happen.

A cyberattack targets a server, exposing personal data while threatening banks across the Netherlands. What is confirmed, and what isn't​

The core facts are consistent across outlets:

  • Wellington IT said hackers gained unauthorised access to information about saved payees, or payment beneficiaries, within its system.
  • The company processes member account data on behalf of credit unions.
  • Wellington IT is one of two service providers to Ireland's credit unions.
  • The Data Protection Commission (DPC) told RTÉ it has received "numerous breach notifications" and is assessing them as a "matter of priority".

The exact scale is not settled. The "40" figure and the "43" figure measure different things. Around 40 breach notifications have reportedly been filed with the DPC. The 43 is a client count: Wellington IT supplies software to 43 Irish credit unions. No credit union or official body has said how many members are affected. Some reports say "hundreds of thousands" of members are affected. Treat that as an unverified estimate until an official source gives a number.

The timeline doesn't line up​

Reports disagree on when the attack happened and how large it was.

  • BleepingComputer, citing notices seen by the Irish Examiner, says an automated script made five million requests to exploit an authorization flaw between October 2 and 4. A local report repeats the October 2–4 window and the five-million figure.
  • Belfast News, quoting Wellington IT's email to credit unions, says hackers made 1.4 million requests. It puts the "malicious requests" on 6 October, and the company's email describes a flaw in its CU Online digital and mobile banking platform.
  • Another outlet likewise dates the malicious requests to October 6.

I can't tell which figures are correct without the original provider notice. The dates and request counts should be read as reported, not as established.

The BleepingComputer article also says the attacker used valid credentials. None of the other sources I reviewed corroborate that. What they do support is exploitation of a vulnerability on the CU Online platform.

Why the delay matters​

The notification gap is the other major thread. Troy said many credit unions were only informed in recent days, although the breach happened in October. He called the delay "not acceptable". BBC reporting says the affected credit unions were told on Tuesday by Wellington IT. A credit union's own notice, from Health Services Staffs Credit Union, says it was informed on Monday, 16 November. The dates differ by a day or so, so the "week of November 16" is the safest description.

Nobody has published a detection date. We can't say whether the weeks of silence came from slow discovery, slow disclosure, or both. Those are different failures, and they point to different fixes.

An Irish credit union chief executive, speaking anonymously, described the gap between the incident and its discovery as "a very, very long time". This was reported by Belfast News, which also reports that Wellington IT holds a 51% share of the Irish credit union banking software market. That concentration is why one vendor's problem became a sector-wide one.

What data may have been exposed​

This is a breach of payee data, not of account credentials or balances. The reported elements, drawn from credit union notices, are:

  • payee name, or the name on the payee's bank account;
  • the nickname the member saved the payee under, where one was given;
  • IBAN and BIC;
  • account number and sort code;
  • payee address;
  • payment reference information.

The lists vary between notices, so treat them as potentially exposed elements and not a confirmed inventory for every person. The records could also reveal which credit union member saved a particular payee.

Wellington IT reportedly cannot say exactly which records were taken. Its email to credit unions said it lacked the logs to confirm individual records, so it is treating all saved payee records on the platform during the period as potentially affected. That missing-logs problem is why no one can give a firm count.

The breach affects online users. RTÉ notes it relates only to members who use an online browser or a credit union's app. Not every member of every affected credit union necessarily had a record exposed.

Is my money safe?​

As of the November 18 reporting, there is no reported loss. Troy said no financial loss has been experienced by any credit union or its members. The Irish League of Credit Unions said its understanding is that the vulnerability has been closed and that member accounts and balances have not been compromised. Several credit union notices repeat this.

That wording is a statement of understanding, not an independently verified forensic finding. HSSCU's notice is careful about it, saying there was "currently no evidence" of compromise. It also says it is still working with Wellington IT to establish the full impact. "No reported loss yet" is also not the same as "no future loss".

Why payee data is still dangerous​

You can't rotate a payee list the way you rotate a password. Cyber security expert Ronan Murphy of Forcepoint told RTÉ that the good news is attackers don't have account access, but the worrying part is that they know who members pay. He said this is very effective for social engineering. RTÉ reports that information about a saved payee could be used to make a fraudulent call, text or email look more convincing.

Consider an example, offered as illustration and not as a reported case. A caller says they're from your credit union. They quote your landlord's name, the IBAN you pay and your usual reference. A common instinct is that fraudsters can't know those details, so the caller must be genuine. This breach weakens that instinct. It also suits fraud where the victim is persuaded to send the money themselves, as with a "your payee's details have changed" message.

Practical steps for credit union members​

This guidance follows the credit unions' advice and the Central Bank's:

  1. Contact your own credit union first if you're worried. The Central Bank expects credit unions to inform potentially affected members without undue delay.
  2. Never share your PIN, password, online banking credentials or one-time security codes with anyone who contacts you unexpectedly.
  3. Don't click links in unexpected emails or texts.
  4. End suspicious contacts and call back using the phone number published on your credit union's official website, not one the caller gives you.
  5. Verify payment changes independently. If a landlord, supplier or contractor suddenly "changes bank details", confirm with them using contact details you already trust.
  6. Never move money because of an unexpected call, text or email, even if the sender knows details about you or your payees.
  7. Report suspicious messages to your credit union.

Lessons for IT and security teams​

Even if you never touch banking software, this incident has a few lessons for IT administrators and developers.

  • Authorization flaws at scale. The reported cause is an authorization flaw hit by an automated script. If that's accurate, it fits a familiar pattern: an endpoint that returns data without properly checking whether the caller is entitled to it. The request volume in a case like this should have been a signal, which is a reason to alert on bulk, scripted access to sensitive objects. This is general industry knowledge, not a finding from this case.
  • Logging decides what you can say. Missing logs left the vendor unable to scope the breach, so it assumed the worst. Comprehensive, retained logs are the difference between a precise notification and a blanket one.
  • Vendor notification clauses matter. Outsourcing systems doesn't outsource accountability. Contracts should specify how fast a vendor must tell you about an incident, and customers should rehearse what they'd do on receipt.
  • Ask your vendors for their incident plans. Know in advance how each critical supplier will tell you about a breach.

What to watch next​

Several questions remain open:

  • the real attack dates and request volume;
  • when Wellington IT detected the problem and when it told customers;
  • how many members and records were involved;
  • who is carrying out the forensic investigation;
  • the outcome of the DPC's assessment of the notifications it has received.

BleepingComputer says it has asked Wellington IT for comment. The company has not publicly disclosed a security incident. Details may change as the credit unions and regulators publish more.

For members, the headline is reassuring on money but not on scams. The balances look safe on current reporting, and the exposed payee data is the kind that can make a scam call sound real.

 

References

  1. Data breach impacts 40 Irish credit unions in reported IT provider hack BleepingComputer 2026-11-18T14:39:33-05:00
  2. Important Information For Members: Cybersecurity Incident – HSSCU hsscu.ie
  3. Credit union breach: What is known and is my money safe? rte.ie