Kivorent News

Wednesday, November 18, 2026

Tech and AINews

Hack at IT supplier Wellington IT exposes payee data at 40 Irish credit unions

An October attack on Belfast-based Wellington IT exposed the saved payees, including names and IBANs, of members at about 40 Irish credit unions, BleepingComputer reports. A government minister called the delay in telling the credit unions not acceptable.

Warden, covering security, outages and the rules for tech
, 2 min read

~40Irish credit unions whose members' data was exposed

What to know

  • An attacker used an automated script making about five million requests to exploit an authorization flaw at Wellington IT between October 2 and 4, according to notices reported by BleepingComputer.
  • Exposed records are payees saved in online banking: names, addresses, IBANs, BICs, account numbers, sort codes and payment references.
  • Passwords, PINs, card details and online banking logins were not affected, the notices say; Wellington IT has not made a public statement.

Members of about 40 Irish credit unions have had banking details exposed in a cyberattack on Wellington IT, a Belfast-based technology supplier, according to BleepingComputer. The company serves about 50 credit unions, 43 of them in Ireland.

The attack ran from October 2 to October 4, according to notices sent to affected credit unions and seen by the Irish Examiner, which BleepingComputer cites. Wellington IT has not publicly disclosed an incident. Ireland's Minister of State Robert Troy confirmed to the broadcaster RTÉ that Wellington IT is the third-party provider involved, and called the long delay in notifying the credit unions "not acceptable," BleepingComputer reported.

Everything below comes from BleepingComputer's report, which draws on those notices and statements. We could not reach a second independent account, so we attribute the details to it. BleepingComputer said it had asked Wellington IT for comment.

What was exposed

The data is the list of payees members had saved in their credit union's online banking. According to the notices, the records include each payee's name and nickname, address, IBAN, BIC, bank account number, sort code and payment reference. Because each record is tied to the member who saved it, the data can also show who pays whom.

The notices say account passwords, PINs, payment card details and online banking credentials were not affected, and some say members' money and logins are safe. Others say the credit union is still working out what was exposed.

Wellington IT warned the credit unions that the breach carries risks of financial fraud, impersonation and targeted phishing, according to the notices. In practice that means emails, texts or calls that quote real payee details to make a fake payment request look genuine.

At least six credit unions have published their own notices: Capital, Phoenix, St. Canice's, First South, Malahide, and Limerick & District. The total number of members affected is not known.

How it happened

According to the notices, an automated script sent about five million requests to exploit an authorization flaw in Wellington IT's systems, and the attacker reached private records using valid credentials. The company told credit unions it did not have the activity logs that would show exactly which members' data was taken, so it cannot confirm the impact person by person.

That pattern, one supplier breached and many customers exposed, is the core of a software supply chain attack. It echoes other third-party incidents we have covered this week, including the Visa provider breach claimed by the n0n group and Rakuten Securities' leak through a test environment.

Why it matters

Credit unions are small and often rely on a shared IT supplier, so a single flaw at one company exposed members of dozens of them at once. The missing logs mean many members may never know for sure whether their payee list was taken, while the notices warn that the details could be used for fraud and targeted phishing.

Sources

Internet, outages and security

Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.