HomeTech NewsCybersecurityIrish Credit Unions Warn After Saved-Payee Data Exposure

Irish Credit Unions Warn After Saved-Payee Data Exposure

Irish ministers and at least one credit union have warned of a cybersecurity incident involving saved-payee data in online banking. The Department of Finance has described a possible incident impacting a limited number of credit unions, and is still waiting for a fuller account of its extent. Phoenix Credit Union, which says it is one of the credit unions caught up in the same supplier issue, has given a more specific description of what was accessed, and a warning about the scams that can follow.

In a press release published on 17 November 2026, the Department of Finance said the Tánaiste and Minister for Finance, Simon Harris, and the Minister of State with responsibility for Credit Unions, Robert Troy, “have been made aware of a possible cybersecurity incident impacting a limited number of credit unions.” Officials “have liaised with the Central Bank of Ireland, which has also been made aware of the potential issue.” The Department “is engaging with the relevant parties and is awaiting further information regarding the nature and extent of the incident, including any potential impact on credit unions and their members.” The ministers, the release said, understand that any affected credit unions will communicate directly with their members where necessary.

“Credit Unions are the lifeblood of our communities – so any suspected breach of members’ data is deeply concerning,” Harris said. Troy said he was “concerned by reports of a suspected cybersecurity incident affecting a number of credit unions,” and added: “I would encourage any members who have concerns to engage directly with their credit union.”

Phoenix Credit Union’s notice, also dated 17 November, is more definite about what happened on its side of the incident. It said it “was informed on Monday, 16 November of a cybersecurity incident affecting a technology service provided by one of our external IT suppliers.” “This is a wider incident affecting approximately 50 credit unions that use services provided by the same technology supplier.” It added that the incident “is not an incident originating within Phoenix Credit Union’s own systems,” and that “the extent of the impact may differ between individual credit unions.”

Those two figures should be kept apart. The Department of Finance’s “limited number” is its description of the credit unions that may have been impacted, given while it is still waiting for further information on the nature and extent of the incident. Phoenix’s “approximately 50” is a count of credit unions that, it says, use services from the same technology supplier. It is not, in the official texts, a confirmed headcount of every credit union whose members’ data was accessed, and it is not a member count. Phoenix is one of the credit unions that use that supplier, not the supplier itself. No official source has published how many members are involved.

Phoenix said the incident “involved unauthorised access to information associated with saved payment beneficiaries/payees within the online banking service,” and that “the vulnerability that allowed this unauthorised access has been fixed.” It is still “working with our technology provider to establish precisely which Phoenix Credit Union members and saved payees are affected.” The information, it said, can include the name of the payee’s bank account and the nickname under which the payee was saved; “IBAN, BIC, bank account number and sort code”; “the payee’s address, where recorded”; and payment reference information entered when the payee was saved. “Because saved payees are associated with the member who created them, the information could also be linked to that member.”

Phoenix said the incident did not compromise online banking passwords, PINs, payment card details or login credentials, and that “the information affected cannot be used to log in to your Phoenix Credit Union account or access the money you hold with us.” “Your money in Phoenix Credit Union is safe,” it said. Members, it added, do not need to take action in relation to their accounts or move their money.

It also published a direct scam warning, which is the practical point for readers. “If anyone contacts you and tells you that you need to move or transfer your money because of this incident, do not do so. Phoenix Credit Union will never ask you to transfer your money to another account in order to keep it safe.” It said it will never ask for a full online banking password or PIN, or for a complete set of security credentials, and will never ask members to transfer money to a “safe account.” It advised members not to give a security code to someone who has contacted them unexpectedly, not to click links in unexpected messages claiming to relate to the incident, and to be cautious if a caller already seems to know details about them or a payee. “Knowing information about you does not prove that the person contacting you is from Phoenix Credit Union.” Anyone who is unsure should end the call and contact the credit union themselves, using a number or address they already have, not one supplied in the unexpected message.

Payee data of this kind is useful to fraudsters even when it cannot unlock an account. TSN has recently covered other cases in which saved payment details or IBANs were at issue, including Revolve’s warning that hackers may have taken saved payment card details and the AllUnited breach, which the organisation said exposed member data including IBANs. A cyberattack confirmed by Crédit Mutuel Arkéa is a reminder that incidents at financial institutions are often followed by a period of uncertainty about what, exactly, was reached. In this Irish case, the official picture is still split between the Department’s cautious “possible” incident and Phoenix’s account of a fixed online-banking flaw affecting saved payees.

Two official measures, and a scam risk that does not need a member count

The Department of Finance is still waiting for further information on the nature and extent of the incident. That is why its language remains “possible,” “suspected” and “a limited number of credit unions.” Phoenix, informed on 16 November, has already described unauthorised access to saved-payee information, named the categories of data involved, and said the vulnerability has been fixed. Both accounts can be true at once. They should not be flattened into a single official total.

In particular, “approximately 50 credit unions that use services provided by the same technology supplier” is not a synonym for the Department’s “limited number.” One describes the supplier’s customer base, as Phoenix presents it. The other describes the credit unions the ministers have been told may be impacted, while the extent is still being established. Until an official source publishes a member count, or a complete list of affected credit unions, neither figure should be read as that. The next facts to watch are narrower: which credit unions notify their members, what those notices say was actually reached, and whether anyone is later told that their own saved payees were involved.

The scam warning does not have to wait for those totals. Saved payee names, IBANs and payment references are exactly the sort of detail that can make a fraudulent call sound genuine. The instruction from Phoenix is unambiguous, and it applies whether or not a given member has yet been told they are affected: do not move money to a so-called safe account, do not hand over passwords, PINs or security codes to someone who called you, and contact the credit union on a channel you already trust.

Sources

Related stories

AllUnited Breach Exposes Member Data, Including IBANs is the closest recent TSN account of member records and IBANs being exposed in a way that can feed later phishing, and is the next read.

Follow @tsnmediahub on X for breaking AI news as it happens.

Follow on X

Share this story

Latest stories

More in this category

Latest stories

Explore the TSN Atlas: Every topic we cover, mapped. Click a bubble to dive in.