Data breaches → mSpy (2024)
Was your data in the mSpy (2024) breach?
2024 · mspy.com · ~2,394,179 accounts exposedModerate severity · 4/10
mSpy (2024) (mspy.com) suffered a data breach in 2024 that exposed around 2,394,179 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 June 2024, a huge trove of data from spyware maker mSpy was obtained by hacktivists and published online. Comprising of 142GB of user data and support tickets along with 176GB of more than half a million attachments, the data contained 2.4M unique email addresses, IP addresses names and photos. The data was predominantly support tickets seeking help to install the spyware on target devices, whilst the attachments contained various data including screen grans of financial transactions, photos of credit cards and nude selfies.
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 mSpy (2024) breach exposed and what each item actually enables:
Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
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.
Reveals your approximate location and internet provider, which adds credibility to targeted scams.
Also listed in this breach: Email addresses, IP addresses, Names, Photos.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Names and usernames: Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts.
- Email addresses: Treat any message referencing this service with suspicion, and never act on links in unexpected emails.
- IP addresses: No direct action needed, but be wary of anyone quoting your location as “proof” of identity.
- 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 data has been circulating for around 2 years, which means it has been copied, combined with other leaks and indexed by search tools many times over.
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.
Frequently asked questions
What data was exposed in the mSpy (2024) breach?
The mSpy (2024) breach exposed names and usernames, email addresses, ip addresses. Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
How many people were affected by the mSpy (2024) breach?
Around 2,394,179 accounts were exposed, making it a large breach.
What should I do if I had a mSpy (2024) account?
Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts. 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 mSpy (2024) breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the SpyFone breach? (2018, ~44,109 accounts)
- Was your data in the Pandabuy breach? (2024, ~1,348,407 accounts)
- Was your data in the SurveyLama breach? (2024, ~4,426,879 accounts)
- Was your data in the Central Tickets breach? (2024, ~722,860 accounts)
- Was your data in the Zacks (2024) breach? (2024, ~11,994,223 accounts)
- Was your data in the Hathway breach? (2023, ~4,670,080 accounts)