{
  "id": "credit-union-payee-exposure",
  "url": "https://ohshit.app/incidents/credit-union-payee-exposure/",
  "title": "Irish credit unions confirm saved-payee data exposure at a shared provider",
  "level": 4,
  "level_name": "septic-tank-blew",
  "date": "2026-11-17",
  "date_is_approximate": false,
  "updated": null,
  "tags": [
    "data breach",
    "credit unions",
    "SaaS"
  ],
  "ecosystems": [],
  "summary": "Irish credit unions confirm unauthorized access to saved-payee information at an external online-services provider. Exposed fields can include names, bank account details, payment references and some addresses. The number of affected people remains unknown.",
  "splash": "Members and saved payees at credit unions whose online-services provider confirms exposure",
  "wipe": "Read your credit union’s notice, verify unexpected financial messages independently and follow individual notifications.",
  "in_the_wild": "yes",
  "source_exception": null,
  "cves": [],
  "fixed": [],
  "checklist": [
    {
      "title": "Check your own credit union’s exposure notice",
      "hint": "Use its official website or established support channel. Confirm which saved payees and fields were affected; a provider-wide customer count is not an affected-person count."
    },
    {
      "title": "Verify unexpected financial communications independently",
      "hint": "Phoenix and St. Canice’s warn that known personal details can make calls, texts or emails convincing. Contact your credit union through an established channel before acting."
    },
    {
      "title": "Do not transfer money in response to a “safe account” request",
      "hint": "Phoenix says no account action or movement of money is required because of this notice and it will never ask you to transfer funds to keep them safe. Follow any later individualized guidance through official channels."
    },
    {
      "title": "Protect credentials and report any response to a suspected scam",
      "hint": "Do not disclose passwords, PINs or security codes to unexpected contacts, or follow unexpected incident-related links. If you have already shared information or transferred money, Phoenix and St. Canice’s say to contact your credit union immediately through its established channel."
    }
  ],
  "sources": [
    {
      "name": "St. Canice’s member notice",
      "url": "https://stcanicescu.ie/important-information-for-members-cybersecurity-incident/",
      "says": "Published November 17; identifies saved-payee fields, exclusions, ongoing scope assessment and member precautions.",
      "primary": true
    },
    {
      "name": "Capital Credit Union member notice",
      "url": "https://capitalcu.ie/important-information-for-members-cybersecurity-incident/",
      "says": "November 18 update gives the October exploitation and closure dates, retrieved fields and conservative payee scope.",
      "primary": true
    },
    {
      "name": "Phoenix Credit Union member notice",
      "url": "https://www.phoenixcu.ie/important-update-cybersecurity-incident/",
      "says": "Confirms provider-side unauthorized access, excluded credentials and precautions against financial impersonation.",
      "primary": true
    }
  ],
  "headline": null,
  "one_liner": null,
  "in_the_wild_note": "Credit unions confirm unauthorized access to saved-payee information.",
  "mitigation": null,
  "timeline": [
    {
      "date": "Oct 2–4, 2026",
      "title": "Provider flaw is exploited",
      "body": "Capital Credit Union reports this exploitation window; it says the flaw was closed on October 6."
    },
    {
      "date": "Nov 16, 2026",
      "title": "Provider informs credit unions",
      "body": "Capital, Phoenix and St. Canice’s say they were notified on this day."
    },
    {
      "date": "Nov 17, 2026",
      "title": "St. Canice’s publishes its member notice",
      "body": "The exact members and payees affected are still being established."
    },
    {
      "date": "Nov 18, 2026",
      "title": "Capital and Phoenix publish further scope and guidance",
      "body": "Capital treats all its saved payees as potentially affected because the precise retrieved subset is unknown."
    }
  ],
  "body_markdown": "The incident concerns a shared external provider’s online-services platform. The credit unions’ notices say the compromise did not originate in their own systems. Capital reports successful retrieval of saved-payee information after exploitation on October 2–4, with the flaw closed on October 6. The November 16 notification date is distinct from the November 17 public notice cited here.\n\nSaved payees can be linked to the member who created them. Potential fields include the payee’s bank account name and nickname, IBAN/BIC or account number and sort code, free-form payment references, and addresses where recorded. Capital also lists internal reference codes that it says contain no identifiable personal data. Payment references may themselves contain names or other identifying information. The precise retrieved subset and affected-person total remain unknown. Capital therefore treats all its saved payees as potentially affected; this is a precautionary scope, not a confirmed count of stolen records.\n\nCapital says members’ linked accounts, balances, transaction counts and amounts, and online-banking credentials were not accessed. Phoenix and St. Canice’s exclude passwords, PINs, card details and login credentials, and say exposed payee data cannot itself provide account access. These statements do not establish a financial-loss total.\n\nCapital assesses the limited data as not posing a high risk of fraud, phishing or identity theft. Phoenix and St. Canice’s nevertheless recommend vigilance for financial impersonation. These are the institutions’ assessments, not a guarantee that unexpected messages are genuine. Phoenix and St. Canice’s describe a wider incident affecting approximately 50 credit unions using the supplier. That is their reported institutional scope, not an independently established list or an affected-person count. Confirmed unauthorized disclosure of financial contact information across institutions supports L4."
}