240 data breach
Incident readout
- Company
- 240
- Reported to
- Indiana Attorney General
- Filed
- February 18, 2026
- People affected
- Not stated in the filing
- Incident type in filing
- Not stated
- Our review
- Monitoring
Was this a ransomware attack?
The filing does not say ransomware was involved. We do not label an incident ransomware unless the company’s report says so. Whatever the cause, the steps to protect yourself and the legal question are the same.
Information listed in the filing
- Full Name
- Date of Birth
- Social Security Number
- Medical Record Number
- Health Insurance ID Number
- Diagnosis and Treatment Information
- Prescription Information
- Provider and Treatment Dates
What we know
Operating within the digital health and wellness sector, 240 functions as a specialized provider of software solutions, telemedicine platforms, and comprehensive patient management systems. In the course of delivering its services, the company routinely collects, processes, and stores an extensive volume of protected health information and sensitive consumer records. Because 240 integrates deeply with healthcare providers and wellness networks to streamline care delivery, it maintains centralized digital repositories containing some of the most intimate details of individual lives. This vast accumulation of high-value data makes 240 an attractive target for malicious cyber actors seeking to monetize stolen digital assets on the dark web.
In 2026, 240 formally reported a major cybersecurity incident to the Indiana Attorney General, alerting affected individuals and regulatory authorities to a significant compromise of its network infrastructure. While investigations into sophisticated digital intrusions of health-tech platforms typically reveal unauthorized access points—such as compromised employee credentials, exploited software vulnerabilities, or third-party vendor weaknesses—the incident underscores the persistent dangers associated with digital health data management. Such breaches often involve threat actors infiltrating core databases, exfiltrating vast archives of unencrypted or inadequately secured information before deploying ransomware or other disruptive payloads to cover their tracks.
The data compromised in the 240 security incident encompasses a dangerous combination of personally identifiable information and protected health records, exposing victims to severe, long-term risks. The exposure of sensitive data types—including full names, dates of birth, Social Security numbers, medical record numbers, health insurance identifiers, and detailed treatment history—creates an immediate platform for identity theft, medical fraud, and targeted financial scams. Unlike traditional credit card breaches, healthcare and wellness data cannot be easily canceled or replaced. When medical histories and identification numbers are exposed, bad actors can fraudulently bill insurance providers, obtain prescription drugs under false pretenses, or compromise individuals' broader financial and credit profiles for years to come.
As an entity handling sensitive personal and health-related data, 240 was bound by rigorous legal obligations under federal and state frameworks, including the Health Insurance Portability and Accountability Act (HIPAA), the Indiana Disclosure of Security Breach Law, and Section 5 of the Federal Trade Commission Act. These statutes mandate that companies implement robust administrative, physical, and technical safeguards—such as multi-factor authentication, regular vulnerability assessments, and strong encryption standards—to protect digital assets from unauthorized access. The occurrence of a data breach of this magnitude serves as a strong indicator that 240 may have failed to maintain adequate security controls, leaving its digital perimeter vulnerable to exploitation and breaching its duty of care to the public.
For residents of Indiana and other affected individuals who received a formal data notification letter from 240, this correspondence serves as legal confirmation that their private information was compromised due to corporate negligence. Legally, the receipt of this notice establishes the standing necessary to participate in a class action lawsuit against the company, allowing victims to seek accountability and financial compensation for the stress, time, and risks incurred. Crucially, affected individuals do not need to prove that actual financial loss or identity theft has already occurred to join the legal fight; the mere exposure of private data is sufficient. Our law firm is actively investigating this breach and handles all class action claims on a contingency fee basis, meaning there are never any out-of-pocket costs or legal fees unless we successfully recover compensation on your behalf.
See every breach reported in Indiana or read what to do after a ransomware attack.
After the 240 incident: what to do and your options
- What should I do after getting the 240 data breach notice?
- Keep the letter and the envelope, and note the date it arrived. Freeze your credit with Equifax, Experian and TransUnion, change any passwords the notice mentions, and sign up for any free credit monitoring the letter offers. Then check whether you may have a claim.
- How many people were affected by the 240 data breach, and what was exposed?
- The filing does not give a count of affected people and lists the following information as involved: Full Name, Date of Birth, Social Security Number, Medical Record Number, Health Insurance ID Number, Diagnosis and Treatment Information, Prescription Information, Provider and Treatment Dates. Your own letter is the best guide to what was exposed about you, since notices are usually tailored to each person.
- Did 240 offer free credit monitoring?
- Look for an enrollment code in your 240 notice. Companies that offer free credit monitoring after a breach usually include it there, with a deadline to activate. Because Social Security numbers are listed in this filing, identity monitoring and a credit freeze matter more than usual. Using the free service won't stop you from joining a lawsuit or settlement later.
- Where can I see the official 240 breach notice?
- 240's report is published by the Indiana Attorney General: https://www.in.gov/attorneygeneral/consumer-protection-division/id-theft-prevention/security-breaches/#240-2026 Compare it with the letter you received to confirm the dates and details match.
- Can I sue 240 over the data breach?
- It depends on what was exposed, the law in Indiana and your own state, and whether you've been harmed. Most people take part through a class action rather than suing alone. Keep your notification letter — it's the proof that connects you to the breach.
- Do I need a 240 data breach lawyer or attorney?
- Whether the company's systems were encrypted by ransomware or data was simply taken, the legal question is the same: did it protect your information the way the law requires? An attorney can review your notice for free, and these cases are usually handled on contingency.
- Is there a 240 data breach class action lawsuit?
- Law firms often open an investigation after a breach notice like this one, and a class action lawsuit may follow. This page doesn't confirm that a lawsuit has been filed against 240. You usually don't have to join a class action to be included — if a settlement is reached, class members are notified and can file a claim.
- Is the 240 data breach letter legit or a scam?
- A notice from 240 in the mail matches the breach 240 reported to the Indiana Attorney General on February 18, 2026. Check that the company name and dates in your letter match that filing. A real notice of data security incident won't ask for your password, Social Security number or a payment — if it does, contact 240 through a phone number or website you find yourself.
- How much could a 240 data breach settlement or claim be worth?
- There is no set amount, and no 240 settlement is confirmed here. In past data breach settlements, payments depended on what data was exposed and on documented losses — fraud, out-of-pocket costs and time spent dealing with the breach. The filing lists Full Name, Date of Birth, Social Security Number as involved. Keep receipts and records; they're what damages claims are built on.
Other breaches reported in Indiana
- Bozeman School DistrictIndiana Attorney General · Filed date pendingCount not stated
- Bozeman School DistrictIN Attorney General · Filed date pendingCount not stated
- Teamsters Local 17Indiana Attorney General · Filed date pendingCount not stated
- Teamsters Local 17IN Attorney General · Filed date pendingCount not stated
- BankIndiana Attorney General · Filed date pendingCount not stated
- BankIN Attorney General · Filed date pendingCount not stated
Attorney advertising. This page reflects a public regulator filing; it does not mean a lawsuit has been filed or that the company did anything unlawful. Submitting a review request does not create an attorney-client relationship.