Identity protection firm Aura discloses breach of 900,000 records after voice phishing attack

Aura, a US company that sells identity theft and scam protection services, disclosed in March 2026 that attackers stole roughly 900,000 records after tricking an employee in a targeted voice phishing call. Have I Been Pwned added the dataset on 18 March, and the company’s disclosure was reported by SecurityWeek the following day.

What happened

According to Aura, the attacker gained access to a single employee’s account for about one hour before access was cut off. The company activated its incident response plan, engaged external security and legal specialists and notified law enforcement. Aura has not said exactly when the attack took place.

Impact

Most of the affected records are names and e-mail addresses held in a marketing tool used by a company Aura acquired in 2021. For roughly 20,000 current and 15,000 former customers, the data also includes postal addresses and phone numbers. Have I Been Pwned lists about 903,000 unique e-mail addresses and data classes including names, phone numbers, physical addresses, IP addresses and customer service records.

Aura stated that Social Security numbers, passwords and financial information were not compromised, as that data is kept encrypted in a restricted environment, and said affected customers do not face significantly elevated risk. It has begun notifying those affected.

Why it matters

The incident is part of a broader pattern in 2026 in which attackers phone employees, impersonate IT support and talk them into surrendering single sign-on credentials and MFA codes. Security vendors are not immune, and data inherited through acquisitions often sits in tools with weaker oversight than core platforms. Contact data from an identity protection provider is also attractive for follow-on scams that impersonate the provider itself.

Recommendations

  • Move privileged and SaaS-admin users to phishing-resistant MFA (FIDO2/passkeys) so that codes read out over the phone are useless.
  • Establish a call-back procedure for any IT support request and train staff that the help desk will never ask for MFA codes.
  • Inventory SaaS and marketing tools inherited through acquisitions; minimise retained data and bring them under central SSO and logging.
  • Alert on unusual export activity and new device registrations immediately after password or MFA resets.
  • Customers should be wary of messages claiming to come from Aura that request account details or payments.

Sources