Data breachesZenBusiness

Was your data in the ZenBusiness breach?

2026 · zenbusiness.com · ~5,118,184 accounts exposedHigh severity · 7/10

ZenBusiness (zenbusiness.com) suffered a data breach in 2026 that exposed around 5,118,184 accounts. If you had an account, some of your personal data may be circulating in leaked databases. The fastest way to know is to check your own email — free, in about 30 seconds, no password required.

What happened

In March 2026, the hacker and extortion group "ShinyHunters" claimed to have obtained a substantial corpus of data from ZenBusiness, a business formation and compliance platform. The group claimed the data had been exfiltrated from platforms including Snowflake, Mixpanel and Salesforce, and threatened to publish it if a ransom was not paid. The following month, after claiming payment had not been made, ShinyHunters publicly released the data. The collection amounted to many terabytes across thousands of files that appeared to originate from multiple systems and business functions, including leads, support records and other CRM-related data. The data contained approximately 5M unique email addresses, often accompanied by name and phone number depending on the source file.

Breach details sourced from Have I Been Pwned, the industry-standard breach database. Risk analysis by Nullivo.

What was exposed, and why it matters

Not all breaches carry the same risk — what matters is which fields leaked. Here is what the ZenBusiness breach exposed and what each item actually enables:

Phone numbers

Enables SIM-swap attacks (hijacking your number to intercept SMS codes), smishing, and voice scams that appear to come from your bank.

Names and usernames

Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.

Email addresses

Puts you on spam and phishing lists, and confirms to attackers that you hold an account with this service — which makes impersonation emails more believable.

What to do if you were affected

These steps are ordered for this specific breach — the most urgent action given what leaked comes first.

  1. Phone numbers: Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider.
  2. Names and usernames: Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts.
  3. Email addresses: Treat any message referencing this service with suspicion, and never act on links in unexpected emails.
  4. Check whether your own email appears in this breach — run a free scan to confirm before you spend time on the steps above.

How urgent is this now?

This breach is recent, so the data is actively traded and the risk is at its highest right now.

Remember: a breach can't be "un-leaked" — once a database is out, it exists in countless copies. The goal is to make the leaked data useless: change what can be changed, lock down what can't, and remove what has been republished.

Check if your email was exposed.Nullivo's free scan checks your own verified email against known breaches — including ZenBusiness — in 30 seconds. No password, no signup, and we only ever scan your own email. Run your free scan →

Frequently asked questions

What data was exposed in the ZenBusiness breach?

The ZenBusiness breach exposed phone numbers, names and usernames, email addresses. Enables SIM-swap attacks (hijacking your number to intercept SMS codes), smishing, and voice scams that appear to come from your bank.

How many people were affected by the ZenBusiness breach?

Around 5,118,184 accounts were exposed, making it a large breach.

What should I do if I had a ZenBusiness account?

Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider. You can check whether your own email appears in this breach with a free Nullivo scan — no password required.

Breaches that exposed similar data

If the ZenBusiness breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.

See all breaches we cover →