AssetMark Data Breach
The 2026 AssetMark data breach involved the unauthorized use of certain employee login credentials and the download of files containing customer information. A Texas regulator record shows that at least 29,802 people were affected; the nationwide total has not been disclosed.
This classification is based on a reviewed lower bound; the actual impact and severity may be higher.
Exposed Data Types
2- Names
- Social security numbers
About This Breach
AssetMark is a U.S. wealth management platform serving financial advisors. The company said the incident was isolated to AssetMark's systems and was not connected to customers' financial advisors.
How Did the Incident Occur?
AssetMark detected suspicious activity associated with certain employee login credentials on May 15, 2026. The company determined that an unauthorized user accessed its systems and downloaded files containing customer information that same day. A review confirmed around May 18 that personal information was involved.
What Information Was Affected?
According to the Texas Attorney General record, the affected information included names and Social Security numbers. Because this information can be used in identity theft and targeted fraud, notice recipients should be cautious about unusual requests for personal or financial details.
How Did AssetMark Respond?
The company terminated the unauthorized access, reset the affected employee credentials, and conducted a forensic investigation with internal and external security professionals. It increased system monitoring, implemented additional safeguards, and offered notice recipients 24 months of free credit monitoring and identity-theft protection.
What Should Affected People Do?
Notice recipients should regularly review credit reports and financial accounts for unfamiliar activity. People whose Social Security numbers were involved may consider a credit freeze or fraud alert. Unexpected links or requests sent in the name of AssetMark or a financial advisor should be verified through a known official channel.
Verification and editorial method
LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.
Report missing or incorrect information
