An automated script made five million requests to exploit an authorization flaw in Wellington IT’s infrastructure, according to notices seen by the Irish Examiner — and those requests appear to have exposed payee information for members of roughly 40 Irish credit unions.
Wellington IT and its customer base
Wellington IT is a Belfast-based supplier whose services are used by about 50 credit unions, including 43 in Ireland. The company has not publicly disclosed a security incident, but Minister of State Robert Troy confirmed to RTÉ that Wellington IT is the third‑party service provider linked to the cybersecurity incident affecting credit unions. Wellington IT reportedly notified affected organisations of a data breach that posed a risk of financial fraud, impersonation, and targeted phishing to their members.
Attack timeline and exploitation method, October 2–4, 2026
According to the notices reviewed by the Irish Examiner, the incident unfolded between October 2 and October 4, 2026. The notices describe an automated script that performed five million requests to exploit an authorization flaw in Wellington IT’s infrastructure. The attacker accessed private records using valid credentials. Wellington IT has told customers it lacks activity logs that would specify which member data were accessed and therefore cannot verify the impact on individual payees.

Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleWhat was exposed — the payee records at risk
At least six credit unions have independently disclosed impacts linked to the incident: Capital Credit Union, Phoenix Credit Union, St. Canice's Credit Union, First South Credit Union, Malahide Credit Union, and Limerick & District Credit Union. Those credit unions’ notices confirm unauthorized access to payee information saved in online banking platforms. The notices list the following fields as potentially exposed:
- Payee name or the name associated with the payee's bank account
- Nickname the member used to save the payee, if provided
- International Bank Account Number (IBAN)
- Bank Identifier Code (BIC)
- Bank account number
- Bank sort code
- Payee address information
- Payment reference information entered for the saved payee
The notices also state the records could reveal which credit union member saved a particular payee. At the same time, organisations say account passwords, PINs, payment card details, and online banking credentials were unaffected. Members have been advised to remain vigilant for phishing and impersonation attempts.
Public disclosures and official reaction
While Wellington IT has reportedly notified customers, it has not made a public disclosure of the incident. Minister Robert Troy described the company's delay in notifying credit unions as "not acceptable" in comments to RTÉ. BleepingComputer has contacted Wellington IT for further information and said it will update reporting if and when the company responds. The total number of impacted individuals is currently unknown.
What this means for credit unions, members, and security teams
Credit unions named in notices are grappling with confirming exactly what fields were accessed and communicating risk to their memberships; several have already issued statements confirming unauthorized access to payee information while clarifying that login credentials and funds were not affected. Members are being warned to expect increased impersonation and phishing attempts that could exploit exposed payee details. Security teams at affected credit unions face the immediate challenge of working with Wellington IT to obtain usable logs — a need made urgent by Wellington IT’s statement that it lacks activity logs sufficient to verify the scope of access to individual payee records.
The most concrete public facts in this case are narrow but consequential: an automated, high-volume exploitation attempt between October 2 and 4, 2026; the use of valid credentials to retrieve private payee records; and uncertainty about the full scale of impact because of missing activity logs. That combination leaves credit unions and their members with confirmed exposure of payee data but without a complete map of who, precisely, was affected. Wellington IT’s next public steps — whether to publish a detailed incident report, produce access logs, or provide direct notice to affected members — are the immediate items to watch.




