Return to Threats

ShinyHunters Claims Ernst & Young Hack

securityweek.com 2026-07-29 fintech AI risk High

What Happened

Ernst & Young previously confirmed that personal and financial information was stolen from a third-party management platform. The post ShinyHunters Claims Ernst & Young Hack appeared first on SecurityWeek .

Why It Matters

According to Ernst & Young’s breach notification, attackers accessed a third-party IT service management platform used for tax-related support, exfiltrating documents that included client personal and financial information between March 28 and April 12.[1][3] ShinyHunters now claims responsibility, alleging a broader supply-chain compromise that yielded EY credentials and access to Jira, GitHub, and Azure, though these claims have not been independently verified and EY has not publicly confirmed the group’s involvement.[1][3][5] From a RealGround perspective, this incident highlights fintech-sector exposure through third-party platforms and developer/cloud environments that may underpin AI-enabled analytics, tax automation tools, or support agents; compromised credentials in such ecosystems could enable data leakage from AI workflows and their training datasets, particularly if tickets or repositories contain client financial datasets or AI model code. Organizations using AI in financial services should treat third-party ITSM and DevOps platforms as part of their AI supply chain, enforcing strict identity management, segmented access to AI-related data and code, and continuous moni

Healthcare Fintech SaaS SMB AI startups

RealGround Analysis

This signal maps to fintech AI risk. Organizations using AI agents, LLM APIs, SaaS integrations, or sensitive data workflows should review whether this class of issue could create unauthorized tool execution, data leakage, weak approval gates, or unmanaged supply-chain exposure.

Recommended Actions

  • Restrict AI agent tool permissions and production write paths.
  • Review sensitive data access across prompts, logs, embeddings, memory, and SaaS integrations.
  • Add human approval workflows for high-impact or state-changing actions.
  • Run prompt injection and indirect prompt injection tests against affected workflows.
  • Document the owner, control gap, and remediation deadline for this risk class.

Source

https://www.securityweek.com/shinyhunters-claims-ernst-young-hack/

Talk to AI CISO