Kaye Lifestyle Homes was listed on 17 April 2025 by the sarcoma ransomware group (the group's claim; Ransomware Tracker by ExposureDrift has not confirmed a breach). sarcoma listed 14 organizations that month and 144 in total.
- Listed 581 days ago.
- 536 organizations were listed by all groups in April 2025, see the month.
- 46 in Retail & E-Commerce that month.
- 228 in US that month.
Updated 2026-11-19 06:12 UTC. Data: public leak-site listings. How we work.
Kaye Lifestyle Homes
Threat Group Post & Evidence
- Listed by
- Sarcoma 144 listings in total
The listing states no data size and no ransom demand.
No capture of the original post
We only show a screenshot when we captured the group's own page ourselves. For this listing we have not, so none is shown.
What the group says it holds
Taken from the group's own post. Ransomware Tracker by ExposureDrift has not seen the data and cannot confirm any of this.
Kaye Lifestyle Homes Since its establishment in 1985, Kaye Lifestyle Homes has built a vast number of homes for families, bringing happiness and satisfaction to thousands of homeowners. With more than 4,000 unique homes under our belt, we take pride in being the leading family-owned home builder in Southwest Florida. Our homes are tailored to fit the lifestyle of each family, and we are delighted to hear how our clients’ homes have exceeded their expectations.Geo: USA - Leak size: 521 GB Archive - Contains: Files, SQL, Exchange
Amounts as written
- 521 GB
Kinds of data mentioned
-
Email and communications
“…expectations.Geo: USA - Leak size: 521 GB Archive - Contains: Files, SQL, Exchange”
-
Customer or client data
“…fit the lifestyle of each family, and we are delighted to hear how our clients’ homes have exceeded their expectations.Geo: USA - Leak size: 521 GB Archive - Contains: Files,…”
-
Databases and backups
“…their expectations.Geo: USA - Leak size: 521 GB Archive - Contains: Files, SQL, Exchange”
Plain-English summary AI-written
The group says it holds a 521 GB archive containing files, SQL data, and Exchange data.
Written by an AI model (openai/gpt-6-luna) from the post above. It can contain mistakes: rely on the quote, not the summary.
What to do about this listing
Choose who you are. Each step shows why it appears and, where we have one, its source. General guidance, not legal or incident-response advice.
If you work with Kaye Lifestyle Homes (customer, supplier or partner)
Within 3 days
- Do not open the group's page or download the data Do not visit the leak site or download files from a listing. Holding stolen data can be unlawful, and the files can carry malware. Wait for the company's own notice. Why: A safety rule for any leak listing.
- Ask Kaye Lifestyle Homes directly Write to your contact and ask whether your data, or your access to their systems, is in scope, and ask for a written statement. Your contract or data-protection law may oblige them to tell you if your data is affected: check the notification clause. Why: A listing is only the group's claim; the company is the one who can confirm what was taken.
- Review what Kaye Lifestyle Homes can reach of yours List the accounts, API keys, VPN or SSO connections and shared mailboxes this company has with you. Rotate the keys you gave them and remove access they do not need. Why: Access a supplier holds is how a listing about them can become a problem for you.
- Expect convincing phishing Messages that quote real orders, invoices or names are more likely after a leak. Tell finance and the help desk to treat any request from, or about, this company with extra care. Why: The post names: customer or client data, email and communications.
- Check software and integrations you take from them If you run their software or call their API, check that updates come through the usual channel and rotate the keys and tokens you hold for it. Why: The post names: databases and backups.
Within 30 days
- Keep watching Kaye Lifestyle Homes A supplier's listing can change after the first sighting: the group can add data, change the status or publish. Add the company to your supplier list to be told, and check your own domain too. Why: A listing is a moving claim, not a single event. Add to your supplier list Check your own domain
If you are Kaye Lifestyle Homes
First 24 hours
- Reset credentials and sessions Force password, API-key and session-token resets for the accounts the post suggests were exposed, enforce phishing-resistant MFA, and revoke OAuth/SSO grants issued before the listing date. Why: The post names: email and communications, customer or client data.
Within 3 days
- Rotate database and cloud access Rotate database and cloud-storage keys, review public bucket and snapshot sharing, turn on object-level audit logging and keep backup encryption keys separate. Why: The post names: databases and backups.
- Check for mailbox compromise Audit mailbox rules, forwarding and delegated access, rotate mail-admin credentials and move DMARC to p=reject to limit follow-on phishing. Why: The post names: email and communications.
- Size the exposure against your own systems Inventory which systems hold data of the kind and volume claimed, so notification and legal decisions rest on your records rather than the group's figures. Why: The post claims: 521 GB. Treat group figures as unverified.
- Lock down exposed admin, VPN and SSO panels Restrict by IP allow-list or a zero-trust proxy and require MFA. Why: A passive scan found 1 critical panel(s) reachable from the internet.
- Check regulatory and stakeholder notification duties United States: state breach-notification laws apply; listed companies may also have SEC Form 8-K Item 1.05 duties for material incidents, and HIPAA applies to health data. This is general guidance, not legal advice: confirm current rules with counsel. Why: Listing country: United States.
Within 30 days
- Check shared suppliers and software List the suppliers and software you share with other Retail & E-Commerce organizations and ask them whether they were affected. Why: sarcoma listed 1 other Retail & E-Commerce organization(s) in the last 90 days.
General readiness for any ransomware claim (not about this listing)
- Offline, immutable backups and a restore drill Keep backups outside domain-admin reach and practise a restore; a leak does not remove the risk of re-encryption. Why: General practice for any ransomware claim; not specific to this listing.
- Look for mass file access and unusual outbound transfers Review EDR, proxy and identity logs for bulk reads, archive creation and large uploads to file-sharing services. Why: General practice for any ransomware claim; not specific to this listing.
- Phishing-resistant MFA on remote access Enforce MFA on VPN, SSO and admin panels, and retire password-only or SMS-based remote access. Why: General practice for any ransomware claim; not specific to this listing.
Listing details
Listing severity score (heuristic)
48/100 • GUARDEDA heuristic built from sector, group, data volume and claim details. It is not evidence that a breach occurred or a measure of harm.
External Attack Surface Profile
ASM IntelligenceRun a free passive scan on your own domain to see what an attacker can see from the outside.