Was your data in the LandAirSea breach?
Check whether your email address was in it
Check my exposureFree. No password — we email you a six-digit code. This breach and every other one your address appears in.
LandAirSea (landairsea.com) suffered a data breach in 2025 that exposed around 337,373 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 January 2025, the GPS tracking service LandAirSea suffered a data breach that exposed 337k unique customer email addresses alongside names, usernames and password hashes. The breach also exposed partial credit card data (card type, last 4 digits and expiration), and GPS device identifiers and locations. LandAirSea is aware of the breach and has remediated the underlying vulnerability.
Breach record from Have I Been Pwned, CC BY 4.0. 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 LandAirSea breach exposed and what each item actually enables:
Also listed in this breach: Email addresses, Names, Partial credit card data, Passwords, Physical addresses, Usernames.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Payment or bank details
Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions. - Passwords
Change this password everywhere you have reused it, starting with your email account — whoever controls your email can reset everything else. - Home addresses
Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating. - 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. - Confirm you were actually in it
Run a free scan before you spend time on the steps above.
This breach put your details on data-broker sites
Because LandAirSea exposed home addresses, this is one of the breaches that feeds people-search and data-broker sites. Those sites scrape leaked databases, combine them with public records, and republish the result as a searchable profile — which is how a single breach turns into a permanent public listing. Removal works, but brokers typically re-list within about four months, so it has to be repeated.
See our broker-by-broker removal guides →
How urgent is this now?
This breach is recent, so the data is actively traded and the risk is at its highest right now.
Passwords are the reason breach age matters less than people expect. Leaked credentials are compiled into wordlists that get tried against new services for years afterwards, so a password exposed here is unsafe to use anywhere, ever again.
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 LandAirSea breach?
The LandAirSea breach exposed payment or bank details, passwords, home addresses, names and usernames, email addresses. Direct financial fraud, plus convincing scam calls that quote your real card or account details to establish trust.
How many people were affected by the LandAirSea breach?
Around 337,373 accounts were exposed, making it a mid-sized breach.
What should I do if I had a LandAirSea account?
Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions. 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 LandAirSea breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.