News and insights

Wellington IT: one supplier, about 40 credit unions, and a month before they knew

When much of a sector runs on one supplier, one breach reaches many organisations at once. In Ireland this month, the warning took weeks to arrive.

What happened

Belfast-based Wellington IT provides banking software to credit unions, including CU Online, their online and app banking platform. The Irish Examiner reports it supports 43 of Ireland’s largest credit unions, with 51% of the market.

Attackers exploited a vulnerability in Wellington IT’s systems in October 2026. According to Silicon Republic, it was being used to request data by 6 October, with up to 1.4 million requests in all.

Wellington IT then told its credit union customers. Silicon Republic says it emailed them on 16 November; the BBC reports 17 November. About 40 credit unions in Ireland are affected, roughly a quarter of the country’s 172. According to the BBC, a few credit unions in Northern Ireland use the system too.

What was reached is information about saved payees: the people and businesses that members pay. According to RTÉ, this may include payee names, IBANs, BICs, account numbers, sort codes, addresses and payment references. Only members who use online or app banking are affected.

The Irish League of Credit Unions says “the relevant vulnerability has been closed” and that member accounts and balances have not been compromised. Robert Troy, the minister of state responsible for credit unions, said no financial loss has been experienced so far.

Silicon Republic says Wellington IT can’t yet tell which records were taken. So it is treating every payee saved on the platform in that period as possibly affected. Its chief executive, Colin Mitchell, said: “As soon as we confirmed the potential risk to customer data, we alerted our customers.”

Mr Troy called the delay in telling the credit unions “not acceptable”, and has asked Wellington IT to explain it. Ireland’s Data Protection Commission has received breach notifications from affected credit unions. The Central Bank of Ireland expects credit unions to tell potentially affected members “without undue delay”.

What to do now

Many organisations share a sector supplier with their peers, such as a core system, a payroll bureau or a booking platform.

  • Know which suppliers hold data about your customers, including the people they pay.
  • Check the breach notice time in each contract. A supplier that takes weeks leaves you little time for your own reporting.
  • Agree how you’ll work together in an incident. Know who to call, and what logs and facts the supplier must give you.
  • Warn customers about follow-up fraud. Stolen payee details make fake payment requests more convincing.

These Blueprint requirements cover the same ground:

  • RW-SUP-07 Supplier risks in your risk register (Established). Treat a shared sector supplier’s risk like your other risks.
  • RW-SUP-03 Contracts that bind suppliers to security (Foundation). Contracts should cover “how quickly they must tell you about a breach”.
  • RW-SUP-15 Critical suppliers in your incident plans (Advanced). Agree with each critical supplier how you’ll work together during an incident.
  • RW-DET-05 Incidents reported on time (Foundation). Notify within the time allowed, even when the news comes late.
  • RW-RES-18 Critical services and what they rely on (Foundation). Record which suppliers your most important services depend on.
  • RW-GOV-07 Unexpected requests confirmed another way (Foundation). Confirm unexpected payment requests through a channel you already know.

How RiskWitness helps

“Which of our services depend on this supplier?” Suppliers and Assets. Record the supplier with an owner, what it provides and the personal data it handles. RiskWitness works out how critical it is. Link it to the systems that rely on it.

“What does the contract say?” Suppliers. Record the security clauses, including how many hours the supplier has to tell you about an incident. Keep assurance evidence, send questionnaires and schedule reviews.

“What does it mean for us?” Risks. Record the risk of a breach at a shared sector supplier, linked to the supplier, with an owner. Score it before and after controls, and choose a treatment.

“Who do we tell, and by when?” Incidents. Record the incident, linked to the supplier, the risk and the affected assets, and when you became aware. RiskWitness shows which regulators may need telling, with their deadlines.

“What will we change?” Actions and Reports. Turn follow-ups into actions with owners and due dates. Map your controls to the RiskWitness Blueprint requirements above. Then produce a PDF report or slide deck for leadership.

Every step is kept in a history that shows who did what, when, and the old and new values. Nobody can edit or delete it. When leadership, an auditor, a customer or a regulator asks how you responded, the answer is already written down.

Sources