Skip to the stories
Microsoft 365 & SharePoint

Flaw in CU Online exposes payee records at around 40 Irish credit unions

A flaw in the CU Online banking platform let attackers pull payee records from around 40 Irish credit unions, with exposure possibly reaching hundreds of thousands of accounts.

Flaw in CU Online exposes payee records at around 40 Irish credit unions
A cartoon of a hackers hand reaching out of a computer towards a bank card.

The scale is what makes this one stand out. Around 40 credit unions in Ireland have been hit by a cybersecurity breach that could touch hundreds of thousands of member accounts. The data at risk isn't balances or login credentials. It's the payee records: who members pay, and the details attached to those relationships. For anyone running member-facing banking software, that's a more uncomfortable category of data than it first sounds.

How the flaw was exploited

The trail starts with Wellington IT, which supplies banking solutions to 43 credit unions across the country. On Monday 16 November, the company emailed credit unions to warn them of a potential breach. The problem sat in CU Online, the digital and mobile banking platform that some of those credit unions provide to their members.

13 SuperValu stores hit in suspected cyberattack

According to Wellington IT, a flaw in that platform allowed a malicious request for data as far back as 6 October. A hacker was able to exploit weaknesses in the system and successfully access payee records linked to credit union member accounts. The window between that first malicious request and the warning email is the detail I'd focus on. Five-plus weeks is a long time for an attacker to work inside a member-facing system before the supplier raises the alarm.

Hackers used fake job interviews to stage $6.3bn Binance heist

The company has been careful about what it can and can't say. Wellington IT said it couldn't confirm which individual records had been compromised. Its approach so far has been to treat every saved payee record on the platform during that period as potentially affected. That's a conservative stance, and it's the right one while forensics are still running. It also means the affected population is defined by time and platform rather than by a confirmed list of victims.

PwC: Irish organisations ‘underprepared’ as AI reshapes cyberthreats

Reports also say there were as many as 1.4m requests to see into credit union accounts during the incident. The source material doesn't break down how many of those requests succeeded, so treat that figure as a measure of attack activity rather than a count of exposed records.

ASOS customers receive threatening message claiming hack

What could be exposed

Based on the information released so far, hackers may have obtained account numbers, addresses, and the names of people and organisations that members make payments to. That combination is worth pausing on. A payee list is a map of a person's financial relationships: rent, utilities, insurers, family members, subscriptions. Put that next to an account number and an address, and you have material that's well suited to targeted phishing. A message that references a real payee by name and an amount that looks familiar is far more convincing than a generic scam text.

Three in four in EU faced cyberthreats at work, survey finds

This is why the member-facing advice matters. Credit union members who hear about this are likely to get unsolicited messages in the weeks ahead, and some of them will look legitimate. Teams in this position typically find that the most useful thing they can do is give members a clear, single channel to verify anything that seems to come from their credit union, and to repeat that message often.

12 in Ireland affected as Revolut leak exposes passport, bank data

The response so far

The Data Protection Commission has confirmed it knows about the incident. In its words, it has "been made aware of this incident and have received a number of breach notifications from affected credit unions." The regulator's role here is to receive those notifications from the controllers, which in this case means the individual credit unions rather than the software supplier. For IT managers at credit unions, that distinction matters: the notification obligations sit with the organisation holding the member data, even when the fault lies in a third-party platform.

Ireland's Tánaiste and Minister for Finance, Simon Harris TD, said "any suspected breach of members' data is deeply concerning." He added: "Credit unions are the lifeblood of our communities, so any suspected breach of members' data is deeply concerning. My officials will continue to liaise with the Central Bank of Ireland and other relevant stakeholders to support the affected credit unions in resolution of this issue." He also said he had "no doubt in the meantime credit unions will engage with individual members who will naturally be concerned by this suspected breach."

Robert Troy TD, Minister of State with responsibility for credit unions, linked the incident to a wider trend. "This comes at a time when cybersecurity incidents are an increasing challenge for financial institutions globally," he said. He encouraged members with concerns to engage directly with their credit union. The joint statement from the two ministers, published on the Department of Finance's site, urged account holders to contact their credit union directly.

Why this matters beyond Ireland

Some context from the same news cycle helps frame the risk. At the start of November, French bank Crédit Mutuel Arkéa revealed that hackers had stolen €100m in a cyberattack. Reportedly, cybercriminals used the lender's own account to send transactions to other banking institutions and may have converted the stolen money into cryptocurrency using a specialised platform. The two incidents differ. The French case involved direct movement of funds, while the Irish one, as currently described, involves data access. Still, both point at the same pressure point: the banking software that sits between members and their money.

For MSPs and IT service providers, the lesson is about supplier concentration. A single platform supplier serving dozens of member organisations means a single flaw can propagate across the whole customer base at once. Teams in this position typically review how quickly they'd learn about a vulnerability in a shared platform, how they'd identify which records a time window touched, and whether their logging could answer that question without the supplier's help. Those are the questions the Wellington IT incident makes concrete.

What to watch next

Three things will shape how this story develops. First, whether Wellington IT can narrow the set of potentially affected payee records beyond its current "all saved records during this period" position. Second, how many individual credit unions file their own breach notifications, and whether the count rises as the review continues. Third, what the supplier says about the flaw itself and the fix once the platform is confirmed secure.

If you run or support a credit union, or any member-facing banking platform, the practical question is simple: if a supplier told you tomorrow that a request-handling flaw had exposed saved payee data for the past six weeks, could you answer your members' questions quickly? This incident suggests that most organisations will find out the hard way how much they depend on a supplier's timelines.

Source: Laura Varley · www.siliconrepublic.com

Same flag