All Breaches
May 13, 2026 Verified Sensitive Record Technology

Redtail Technology Data Breach 2026: SSNs and Account Data

Redtail Technology reported that data was exfiltrated from systems containing some customer information after a social engineering attack targeted an employee on May 13, 2026. The official notice identifies risk involving names, Social Security numbers and financial account information.

At least 1
Affected People
3
Data Types
At least Low
Severity
Oct 9, 2026
Last updated

This classification is based on a reviewed lower bound; the actual impact and severity may be higher.

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

3
  • Names
  • Social security numbers
  • Financial account information

About This Breach

The incident occurred within technology systems Redtail uses to serve financial-services companies. The public New Hampshire filing was submitted on behalf of J.W. Cole Advisors, so its disclosed scope should not be interpreted as a confirmed nationwide total for every Redtail customer or user.

Incident Summary

According to Redtail's notice, an unauthorized party used social engineering against an employee on May 13 and temporarily accessed a limited subset of data and cloud platforms used to manage and support customer relationships. The intruder exfiltrated data from those systems.

Security controls detected and contained the event, and the intruder was removed early on May 14. Redtail investigated with an external cybersecurity firm, notified J.W. Cole Advisors on June 8 and sent consumer notice on July 6.

Who Was Affected?

The filing with the New Hampshire Attorney General confirms that information relating to one state resident may have been affected. No nationwide total or total across other Redtail business customers has been disclosed, so the verified figure is at least one person and is not a final total.

Redtail submitted the notice on behalf of J.W. Cole Advisors, the data owner. The filing does not establish that every Redtail customer or everyone associated with J.W. Cole Advisors was affected; recipients should rely on the scope stated in their individual notification.

What Information Was Involved?

The regulator letter identifies the New Hampshire resident's name and Social Security number. The enclosed sample consumer notice also states that Social Security and account numbers were affected by the incident.

The involved fields may differ from person to person. Data types not identified by the notice should not be assumed to have been exposed; check the official letter from Redtail or J.W. Cole Advisors for the scope that applies to you.

Potential Risks

A name combined with a Social Security number can increase the risk of identity theft, fraudulent credit applications, and tax or benefits fraud. Misuse can surface months after an incident, making continued credit monitoring important.

Account numbers and knowledge of a financial-advisory relationship can help criminals craft convincing investment, account-verification or transfer requests. A message or call that knows the institution's name should not be trusted on that fact alone.

What Should You Do?

People who received the official notice were offered 24 months of identity monitoring through Experian IdentityWorks. The offer is limited to recipients with a valid activation code, and the letter lists September 30, 2026 as the enrollment deadline.

Review reports from all three credit bureaus and notify the relevant financial institution if you find suspicious activity. Depending on your circumstances, a fraud alert or credit freeze can make it harder for someone to open new accounts in your name.

Do not use unexpected links that claim to come from Redtail, J.W. Cole Advisors or your financial adviser. Verify the request through a previously known telephone number or the official website, and use unique passwords and multifactor authentication for financial accounts.

Redtail Technology's Response

Redtail said it strengthened access controls on affected systems, added security alerts and expanded employee training. The company also investigated with outside specialists, notified the relevant data owner and regulators, and offered identity-protection support to people who received notices.

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