The letter went out on Monday. Credit unions using Wellington IT's CU Online platform were told that saved payee data linked to their members may have been retrieved in a cyberattack earlier in the autumn. The Belfast-based vendor supplies banking software and services to 50 credit unions, 43 of them in Ireland. Around 40 were affected, according to Minister of State for Credit Unions Robert Troy.

The disclosure landed a month after the attack and two days after the vendor concluded that data may have been taken. For members, the delay is the part that stings. For the wider market, the incident is a case study in concentration risk: a single authorisation flaw in a shared platform reached dozens of small institutions at once, and the vendor's records could not say whose data was fetched.

What Wellington IT found

Wellington IT's platform is called CU Online. It handles member accounts and payments for credit unions that do not run their own core banking systems. The vendor said an authorisation flaw in the platform was exploited by an automated script that came through a valid member login in the first week of October. The Irish Examiner reported that the script made millions of requests and that the intruder could access saved payee records.

The vendor's initial conclusion was that there was no exposure. That changed after a credit union contacted Wellington IT on Friday, November 13, about extortion emails sent to it and several other credit unions. The messages had been filtered into junk mail. Two days later, on Sunday morning, November 15, the vendor concluded that saved payee data linked to a member may have been retrieved. It wrote to credit unions the next day.

Because Wellington IT did not have logs showing which records were requested or returned, it could not narrow the exposure to specific members. Silicon Republic reported that the vendor is "treating all saved payee records on the platform during this period as potentially affected." The company said the vulnerability has been closed.

What was exposed and what was not

The data in question is the saved payee list that members build when they set up transfers. It can include the name of the person or organization being paid, the IBAN, the BIC, the bank account number, the sort code, the member's address, and payment references.

Wellington IT said member account and balance details were not retrieved. The Irish League of Credit Unions said member accounts and balances have not been compromised, and no financial loss to members has been reported. That distinction matters, and it is also where reassurance should stop. A payee record does not contain a password or a card number, but it contains exactly the details a convincing payment fraud needs: who a member pays, where the money goes, and what the member's address is.

The Data Protection Commission said it received a number of breach notifications and is reaching out to the relevant parties as a matter of priority. The Central Bank of Ireland urged credit unions to communicate clearly with members and to inform potentially affected members without undue delay. The Department of Finance said it was liaising with the Central Bank and awaiting further information.

Members who want to reduce their own exposure can review the saved payee list in their online banking and remove any payee they do not recognize. That will not undo a disclosure that has already happened, but it narrows the list that a future message could reference. A member who sees an unfamiliar payee should report it to the credit union rather than delete it quietly, because the record may help the institution understand the scope of the incident.

The month between the attack and the letter

The timeline is the uncomfortable part. The attack occurred in the first week of October. The first warning to the vendor appears to have come from a credit union on November 13, after extortion emails reached members. The vendor's conclusion came on November 15. The letters went out on November 16. Public statements and reporting followed on November 17 and 18.

Minister Troy criticised the delay in the disclosure. Tánaiste and Minister for Finance Simon Harris said in a government statement that "any suspected breach of members' data is deeply concerning." He said officials would support the affected credit unions in resolving the issue. The statement framed the incident around the members rather than the technology, which is the right frame and also the one that raises the next question: what were members told, and when.

A month is a long time in a phishing cycle. Payee data does not expire. An attacker who holds a member's name, address, and payee IBAN can use it in a call or an email months from now, when the news has moved on and the member has forgotten the letter. The delay does not prove that anyone used the data. It does extend the window in which a member needs to be careful.

Why payee data is sensitive

Most fraud warnings focus on passwords, card numbers, and one-time codes. Payee data is quieter. It supports a different kind of attack: the message that appears to know exactly who the member banks with and who they pay.

An attacker with a saved payee list can send an email that looks like it comes from a known supplier, with the correct bank details and a plausible change of account. The member is not asked for a password. The member is asked to update a payment instruction. That is the invoice redirection pattern, and it works because the details in the message are real.

The extortion emails that surfaced on November 13 are a cruder version of the same leverage. Credit unions and members should treat any unexpected message that references their account or their payees as suspect, particularly if it asks them to call a number, click a link, or move money. A credit union will not ask a member for a full password or a one-time code over email or text.

Members who are concerned should contact their credit union directly, using the number on the credit union's own website or statement, not a number in an unexpected message. The Central Bank's advice was the same: start with the credit union.

The concentration problem

Ireland has around 160 credit unions. Wellington IT serves 43 of them in the Republic. That is a normal arrangement for a sector built on small, local institutions. A credit union with a few thousand members cannot build and run its own core banking platform, and shared software is how it gets modern payments and online services at a manageable cost.

The same arrangement concentrates risk. One authorisation flaw in one platform reached dozens of institutions at once. The vendor detected the anomalous requests, but its initial read was that nothing had been exposed, and its logging could not reconstruct which records had been fetched. The institutions that relied on the vendor had no independent view of their own members' data.

That is the governance question the incident leaves open. Outsourcing the platform does not outsource the duty to protect members' data. Each credit union remains the data controller for its members, and each board has to be able to say what happened, who was affected, and what it is doing about it. The Data Protection Commission's investigation will test whether the notifications and the vendor's arrangements met the legal standard. The Central Bank's supervision will test whether the credit unions' operational resilience rules covered this kind of dependency.

The sector's structure makes that test harder than it looks. Many credit unions are small enough that their entire technology function is a contract and a support line. Their boards are made up of volunteers and part-time officers, not security engineers. They can demand assurances from a vendor, but they cannot audit the vendor's code or reconstruct its logs. When the platform fails, the institution that members trust has to explain a failure that happened somewhere else.

What members and boards should ask

Members can ask three questions. Was my data in the affected set? If so, will I be told individually, and when? What should I watch for in the next few months? A credit union that cannot answer the second question should say so and give a date when it can.

Boards should ask more. Does the vendor's contract require logging that can identify which records were accessed? What was the escalation path when the anomalous requests were detected, and why did the initial conclusion change only after a credit union reported extortion emails? Has the credit union told its members directly, or only published a notice? Has it tested whether its own contact details are the ones members will trust when a fraudster calls?

Those are unglamorous questions, and they are the ones that determine whether the next incident is caught in hours rather than weeks. The sector's regulator has already said that members should be informed without undue delay. The test is whether the vendor and the credit unions can meet that standard when the next flaw appears.

The trust that pays for the system

Credit unions sell themselves on proximity. Members know the staff, the branch, and the person who answers the phone. That proximity is also why a data breach feels personal: the institution that knows a member's name is the one that lost the list of people the member pays.

The technical fix is already in place. The vulnerability is closed, and the regulator is investigating. The repair that takes longer is the one between the credit unions and their members, and it depends on plain information: who was affected, what was taken, what members should do, and what the institutions will change.

The letter did not arrive in the first week of October. It arrived on November 16. The members who read it will remember that gap longer than they remember the flaw. The institutions can still earn back some of that trust, but only by telling members plainly what happened and what they intend to do next.

Primary sources

  1. Irish Examiner, for Wellington IT's account of the authorisation flaw, the October attack window, the November 13 extortion emails, the November 15 conclusion, and the November 16 notification.
  2. Silicon Republic, for the number of credit unions affected, the platform's role, the data categories, and the vendor's statement that it was treating all saved payee records as potentially affected.
  3. Department of Finance statement on gov.ie, for the Tánaiste's comments and the government's response.
  4. TheJournal.ie, for the minister's confirmation that customer data was obtained by a bad actor.