Skip to content

Response, New York. Noah Park: Check Point Patches Actively Exploited Management Server Path Traversal. Detection, Dallas. Ava Okello: Report Finds Nearly Half of Deployed Detections Need Attention Before SOCs Can Trust Them.

SOCtember

Always First. Fast SOC News.

Screenshot of the Phoenix Credit Union website notice titled Important Update, Cybersecurity Incident, dated November 18, 2026, saying the credit union was informed on Monday, November 16 of an incident affecting a technology service provided by an external IT supplier and that about 50 credit unions are affected.
Image: Phoenix Credit Union (fair use). One of the member notices credit unions in Ireland posted this week.

Response

A Script Made Five Million Requests Through One Valid Login to Pull Irish Credit Union Payee Data, and the Supplier Says the Logs That Would Show Whose Records Were Taken Are Not Available

Wellington IT, which runs online banking technology for about 50 credit unions, told customers six weeks after the October attack that an authorization flaw let an automated client harvest saved payee details. Extortion emails had landed in junk mail, and an early investigation had found "no exposure."

Noah Park, ResponseNew York5 min read

NEW YORK - An attacker used a single valid member login and an automated script to send five million requests to the online banking platform that serves dozens of Irish credit unions, exploiting what the supplier called an "authorisation flaw" to pull members' saved payee records, according to correspondence from the supplier reported by the Irish Examiner.

The supplier, Wellington IT, a Belfast company that provides software and services to about 50 credit unions, 43 of them in Ireland, told its customers on Monday that the requests ran between Oct. 2 and Oct. 4. It also told them that it could not say whose records had been taken.

"The logs that would identify which members were requested or what each response contained are not available," the company wrote, according to the Irish Examiner. "We cannot therefore, at this stage, confirm which individual records were retrieved and are treating all saved payee records on the platform during this period as potentially affected."

What was taken, and what was not

The exposed records are the payees that members had saved in online banking to send money. Notices posted by affected credit unions list the payee's name and the nickname under which it was saved, the IBAN, BIC, account number and sort code, the payee's address where recorded, and payment reference information. Because each saved payee is linked to the member who created it, Phoenix Credit Union told members, "the information could also be linked to that member."

Screenshot of the Phoenix Credit Union notice section What information was affected, listing the payee's bank account name and nickname, IBAN, BIC, bank account number and sort code, the payee's address and payment reference information, and stating the incident did not compromise online banking passwords or PINs.
Image: Phoenix Credit Union (fair use).The categories of saved payee data listed in a member notice.

The credit unions said online banking passwords, PINs, payment card details and login credentials were not compromised, and that the information taken cannot be used to log in to a member's account. Wellington IT's correspondence said members' account and balance details "were not retrieved," the Irish Examiner reported. Malahide Credit Union said its core banking system was not accessed and that the vulnerability had been fixed.

Robert Troy, Ireland's minister of state with responsibility for credit unions, told the broadcaster RTE on Wednesday that roughly a quarter of the country's credit unions, about 40, were affected, and that no financial loss had been recorded by any credit union or member. He said details including IBAN and BIC numbers had been obtained by "an unauthorised bad actor through a third-party ID provider."

Screenshot of the Malahide Credit Union notice titled Important Information for Members, Cybersecurity Incident, saying an online banking technology service provided to 43 credit unions by an external IT provider was affected and that core banking systems, balances, passwords and PINs were not compromised.
Image: Malahide Credit Union (fair use).Malahide Credit Union's notice to members.

Six weeks, a junk folder and an early all-clear

The timeline is what makes the case instructive for security teams. According to the Irish Examiner, Wellington IT said an initial investigation into the October activity concluded there was "no exposure." The picture changed only after a credit union told the company on Friday, Nov. 13, that extortion emails had been sent to it and to several credit unions. "These had been filtered to junk mail and had not been seen by WIT before then," the company wrote. On the morning of Sunday, Nov. 15, its engineering team concluded that "saved payee data linked to a member may have been retrieved," and the company notified credit unions the next day.

Mr. Troy said the incident "happened sometime in October" and that "the third party provider delayed in passing on this information." He added, "That simply is not acceptable." He has written to Wellington IT to seek a meeting, RTE reported. The Department of Finance said in a statement on Tuesday that it was awaiting information on the nature and extent of the incident, and the Irish Examiner reported that the Data Protection Commission had received "a number of breach notifications."

Screenshot of the Government of Ireland press release from the Department of Finance, published November 17, 2026, titled Tanaiste and Minister Troy comment on suspected cybersecurity incident involving credit unions.
Image: Government of Ireland (fair use).The Department of Finance statement of Nov. 17.

Wellington IT's chief executive, Colin Mitchell, said in a statement that the company alerted customers "as soon as we confirmed the potential risk to customer data," had "engaged external cybersecurity experts to assist with our investigation and response," and was working with the Data Protection Commission, the National Cyber Security Centre and the Garda National Cyber Crime Bureau.

The lessons for defenders

Several of the failures described in the correspondence are ones security operations teams can test for in their own environments. Five million requests from one authenticated session over three days is a volume that per-user rate limits and anomaly alerts on member-facing APIs are designed to catch. An authorization flaw that let one member's session return other members' data is the kind of object-level access bug that application logs should make reconstructable, which only works if the application records which object each request asked for and retains that record long enough for an investigation.

The junk-folder detail is a reminder that extortion and breach-claim emails often arrive at shared or vendor-facing inboxes where no one triages spam, and that a quarantine review belongs in the playbook for any suspected incident. And the early "no exposure" finding shows the cost of closing an investigation before the data access logs needed to support that conclusion have been confirmed to exist.

For credit union members, the immediate risk the credit unions describe is targeted fraud. Criminals who know whom a member pays, and where that payee banks, can send convincing requests to change payment details or move money. Phoenix Credit Union told members it will never ask them to transfer money to another account to keep it safe.

About the Author

Noah Park

Noah Park covers incident response, identity compromise, and blue-team operations for SOCtember from New York.

Related stories

Response desk