DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Lutheran Social Services of Illinois notifies 184,183 of ransomware attack one year ago

Posted on January 27, 2023 by Dissent

On March 25, 2022, Lutheran Social Services of Illinois (LSSI) notified HHS of a breach affecting 1,000 people. The incident, still under investigation by HHS, was coded as a “Hacking/IT Incident”  involving data on the network server.

On January 25, 2023, LSSI notified the Maine Attorney Genera’s Office a breach affecting a total of 184,183 people.

In its newest report, LSSI reports that on January 27, 2022, they discovered they had been hit with a ransomware attack. Almost one year later, on December 28, 2022, they discovered that “certain personal information maintained on our systems was potentially accessed by an unauthorized party from December 31, 2021 to January 27, 2022.”

Based on the timeframe and the fact that this was a ransomware attack, the March 2022 report to HHS was probably just a first report on the incident, although that is somewhat speculative on DataBreaches’ part.

But is the newest report to Maine of 184,183 affected only about patients/clients, or does it include others who would not be reportable under HIPAA? It’s unclear because Maine requires entities report the total number of people affected, whereas HHS only reports the number of patients affected.

LSSI’s notification does not explain why it took them a year from initial event/discovery to figure out who was affected and whom to notify.

 

 


Related:

  • TX: Kaufman County Faces Cybersecurity Attack: Courthouse Computer Operations Disrupted
  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
Category: Breach IncidentsHealth DataMalwareU.S.

Post navigation

← Indianapolis Housing Authority breach was worse than originally estimated
Stratford University discloses ransomware attack — but which ransomware attack? →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.