47,876
Ameriprise Financial, a leading U.S. financial services company, has disclosed a data breach affecting 47,876 individuals. The breach, which occurred in March 2026, involved unauthorized access to stored files containing sensitive customer information, including names, addresses, financial account details, and potentially Social Security numbers. This marks the company's second security incident in less than six months. Although Ameriprise has not formally attributed the attack, subsequent legal filings (since dropped) alleged that the ShinyHunters group claimed responsibility. The company has engaged external experts and is providing credit monitoring services to those affected.
The data breach began on March 2, 2026, when an unauthorized party gained access to Ameriprise Financial's stored data. The intrusion was not detected until March 18, 2026, allowing the threat actor a 16-day window of access. The company filed a breach notification with the Maine attorney general's office, detailing the scope of the incident.
The compromised data includes a range of Personally Identifiable Information (PII) and financial data:
Court filings from lawsuits that were later dropped without prejudice alleged that ShinyHunters was behind the attack and had threatened to release over 200 gigabytes of internal data. This incident follows a previous breach in December 2025, raising significant concerns about the company's data security posture.
The specific method of initial access and lateral movement has not been disclosed by Ameriprise Financial. The description of "unauthorized access to the company's stored data and files" suggests a compromise of either a file server, a cloud storage instance (e.g., S3 bucket, SharePoint), or a database. The 16-day dwell time before detection indicates a potential gap in monitoring and detection capabilities.
T1567 - Exfiltration Over Web Service: Consistent with ShinyHunters' TTPs, who often exfiltrate large volumes of data to sell.T1213 - Data from Information Repositories: The core of the attack was accessing and stealing data from company storage.T1078 - Valid Accounts: The initial access could have been achieved through compromised credentials, a common vector.T1552.001 - Credentials in Files: Attackers may have found credentials in configuration files or other documents to move laterally and access the data stores.The breach poses a significant risk of identity theft, financial fraud, and targeted phishing attacks for the nearly 48,000 affected customers. The exposure of financial account details and Social Security numbers is particularly damaging. For Ameriprise Financial, the incident results in substantial costs related to incident response, regulatory fines (potentially from the SEC), customer notifications, and credit monitoring services. The second breach in six months severely damages the company's reputation and customer trust, which is paramount in the financial services industry.
No specific Indicators of Compromise were provided in the source articles.
Security teams may want to hunt for the following patterns to identify similar threats:
log_sourceCloud Storage Access Logs (e.g., S3, Azure Blob)GetObject calls from an unfamiliar IP or user agent.network_traffic_patternLarge egress traffic from file serverslog_sourceSIEM alerts for data accessD3-UBA - User Behavior Analysis.D3-UAP - User Account Permissions.D3-MFA - Multi-factor Authentication.Implement robust logging and auditing for all access to sensitive data stores, and use UEBA to detect anomalous activity.
Strictly enforce the principle of least privilege for all user and service accounts to limit the blast radius of a compromised account.
Require MFA for all access to systems containing sensitive customer data, especially for remote and administrative access.
Continuously train employees to recognize and report phishing attempts, which was the vector for a previous breach.
Ameriprise Financial reports its previous data breach.
Unauthorized access to Ameriprise's stored data begins.
The data breach is detected by Ameriprise, 16 days after it began.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.