Writing Exchange

Dissent Doe :cupofcoffee:UnitedHealth's Change Healthcare got a ton of what some might consider well-deserved bad press last year after a ransomware attack by AlphV/BlackCat. Now they're getting more bad press. UnitedHealth is demanding that some struggling doctors immediately repay loans issued after last year’s cyberattack. That wasn't the way the providers were told repayment would work in terms of when and how. <a href="https://infosec.exchange/tags/CNBC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CNBC</a> has the story:<a href="https://www.cnbc.com/2025/04/11/unitedhealth-makes-doctors-repay-loans-issued-after-change-cyberattack.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.cnbc.com/2025/04/11/unitedhealth-makes-doctors-repay-loans-issued-after-change-cyberattack.html</a><a href="https://infosec.exchange/tags/IncidentResponse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IncidentResponse</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a>

Dissent Doe :cupofcoffee:From the We-Wish-This-Was-An-April-Fools-Joke-But-It’s-Not department:Vitenas Cosmetic Surgery patient data hacked and leaked<a href="https://databreaches.net/2025/04/01/vitenas-cosmetic-surgery-patient-data-hacked-and-leaked/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2025/04/01/vitenas-cosmetic-surgery-patient-data-hacked-and-leaked/</a><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/extortion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#extortion</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a>

Dissent Doe :cupofcoffee:Oracle Health is becoming the poster child for how NOT to respond to a breach:<a href="https://www.bleepingcomputer.com/news/security/oracle-health-breach-compromises-patient-data-at-us-hospitals/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.bleepingcomputer.com/news/security/oracle-health-breach-compromises-patient-data-at-us-hospitals/</a><a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidentresponse</a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HIPAA</a> <a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a>

Dissent Doe :cupofcoffee:Four months after learning of a vendor's breach, Concord Orthopaedics in NH notifies almost 68,000 patients. At the same time that they were mailing notifications, <a href="https://infosec.exchange/tags/EverestTeam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EverestTeam</a> was leaking 2.9 GB of files with patient info from 2018-2024. <a href="https://databreaches.net/2025/03/27/four-months-after-learning-of-a-vendors-breach-concord-orthopaedics-notifies-almost-68000-patients/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2025/03/27/four-months-after-learning-of-a-vendors-breach-concord-orthopaedics-notifies-almost-68000-patients/</a><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/ThirdParty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ThirdParty</a> <a href="https://infosec.exchange/tags/vendor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vendor</a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HIPAA</a>

Dissent Doe :cupofcoffee:Health-care billing company Medical Billing Specialists Inc. (MBS Select) has been hit with a potential class action lawsuit over their 2024 breach.Notifications first went out a year after the attack by Akira ransomware group. <a href="https://databreaches.net/2025/02/26/medical-billing-vendor-sued-over-health-data-leak-gold-mine/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2025/02/26/medical-billing-vendor-sued-over-health-data-leak-gold-mine/</a>h/t, Bloomberg Law.Direct link to complaint: <a href="https://www.bloomberglaw.com/public/desktop/document/MarianoGuerravMedicalBillingSpecialistsIncDocketNo125cv10453DMass?doc_id=X7V6GF8O0QV9EOAVLKEKKSJCO87" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.bloomberglaw.com/public/desktop/document/MarianoGuerravMedicalBillingSpecialistsIncDocketNo125cv10453DMass?doc_id=X7V6GF8O0QV9EOAVLKEKKSJCO87</a><a href="https://infosec.exchange/tags/BAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BAA</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a> <a href="https://infosec.exchange/tags/notification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#notification</a>

Dissent Doe :cupofcoffee:From Bluesight's press release for the 2025 Breach Barometer, some of the key findings:<ul><li>More than 300 million patient records breached in 2024, a 26% increase over 2023. This included the largest healthcare breach ever recorded, affecting 1 in 2 Americans.</li><li>Insider threats, hackers and third-party relationships drove breach impact in 2024, with business associates accounting for the majority of breached records (77%) in the 2025 Breach Barometer dataset.</li><li>Breach notifications took an average of 205 days after an incident in 2024, compared to 177 days in the previous year.</li></ul>I'll have more details on some of these issues on my blog in the near future, but encourage you to download the full report now: <a href="https://bluesight.com/wp-content/uploads/2025/02/2025-Breach-Barometer-Annual-Report.pdf" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://bluesight.com/wp-content/uploads/2025/02/2025-Breach-Barometer-Annual-Report.pdf</a>For those of you that read the Protenus Breach Barometer report I produced with Protenus every year beginning in 2016, Bluesight recently acquired Protenus and is continuing to produce the report in collaboration with my work. <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/statistics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#statistics</a> <a href="https://infosec.exchange/tags/analysis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#analysis</a> <a href="https://infosec.exchange/tags/BAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BAA</a>

Dissent Doe :cupofcoffee:Update: On February 24, 2025, the Termite ransomware group claimed responsibility for the attack on Genea, a network of fertility (IVF) clinics in Australia.On their dark web leak site, Termite claims to have ~700 GB of data from Genea's servers,, including patient data. They posted a number of screenshots with patient records as proof of claims. <a href="https://infosec.exchange/tags/Genea" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Genea</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/IVF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IVF</a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/Termite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Termite</a><a href="https://mastodon.social/@David_Hollingworth" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@David_Hollingworth</a>

Dissent Doe :cupofcoffee:Beverly Hills Plastic Surgeon Jaime Schwartz M.D. Sued for Not Timely Notifying Patients of Two Hacks: <a href="https://databreaches.net/2025/02/22/beverly-hills-plastic-surgeon-jaime-schwartz-m-d-sued-for-not-timely-notifying-patients-of-two-hacks/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2025/02/22/beverly-hills-plastic-surgeon-jaime-schwartz-m-d-sued-for-not-timely-notifying-patients-of-two-hacks/</a>h/t, <a href="https://infosec.exchange/tags/404media" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#404media</a> <a href="https://infosec.exchange/tags/Courtwatch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Courtwatch</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/extortion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#extortion</a> <a href="https://infosec.exchange/tags/incident_response" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incident_response</a> <a href="https://infosec.exchange/tags/notification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#notification</a> <a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a> <a href="https://infosec.exchange/tags/hack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hack</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a>

Dissent Doe :cupofcoffee:So remember the ransomware attack discovered last July by Columbus, Ohio -- who raced to court to chill the speech of a researcher (David Ross, aka "Goodwolf") who disputed their claims about the breach? Well, now it comes out that there was also some medical info from emergency services involved in the breach: <a href="https://spectrumnews1.com/oh/columbus/news/2025/02/04/health-information-columbus-cyberattack" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://spectrumnews1.com/oh/columbus/news/2025/02/04/health-information-columbus-cyberattack</a>They discovered the medical stuff in December and are first sending out letters to those affected now. <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/govsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#govsec</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a> <a href="https://infosec.exchange/tags/Rhysida" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rhysida</a>

Dissent Doe :cupofcoffee:Delta County Memorial Hospital District reveals more about 2024 cyberattack that affected 148,363 people: <a href="https://databreaches.net/2025/02/03/delta-county-memorial-hospital-district-reveals-more-about-2024-cyberattack-that-affected-148363-people/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2025/02/03/delta-county-memorial-hospital-district-reveals-more-about-2024-cyberattack-that-affected-148363-people/</a><a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/cyberattack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cyberattack</a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HIPAA</a>

Dissent Doe :cupofcoffee:Cover-up Follow-up: Westend Dental starts notifying patients of October 2020 ransomware attack: <a href="https://databreaches.net/2025/02/02/cover-up-follow-up-westend-dental-starts-notifiying-patients-of-october-2020-ransomware-attack/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2025/02/02/cover-up-follow-up-westend-dental-starts-notifiying-patients-of-october-2020-ransomware-attack/</a><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidentresponse</a> <a href="https://infosec.exchange/tags/coverup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coverup</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HIPAA</a>

Dissent Doe :cupofcoffee:As an update to previous reporting: 0mid16B leaked Apex Custom Software's Controlled Substance management software code... and employee login info from one of their healthcare clients. Background here: <a href="https://databreaches.net/2025/01/30/exclusive-apex-custom-software-hacked-threat-actors-threaten-to-leak-the-software/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2025/01/30/exclusive-apex-custom-software-hacked-threat-actors-threaten-to-leak-the-software/</a><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/business_associate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#business_associate</a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HIPAA</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a>

Dissent Doe :cupofcoffee:So... apart from the fact that I don't think they should have dropped charges against this doctor, is HHS going to investigate why the hospital gave access to patient data to a former employee/resident who no longer worked there and was never these patients' doctor? US Justice Department drops case against Texas doctor charged with leaking transgender care data: <a href="https://www.wfaa.com/article/news/local/us-justice-department-drops-case-against-doctor-charged-with-leaking-transgender-care-data/287-3e8a394d-41fb-41bf-bf72-fd012b87851b" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.wfaa.com/article/news/local/us-justice-department-drops-case-against-doctor-charged-with-leaking-transgender-care-data/287-3e8a394d-41fb-41bf-bf72-fd012b87851b</a><a href="https://infosec.exchange/tags/HealthSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HealthSec</a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HIPAA</a> <a href="https://infosec.exchange/tags/SecurityRule" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecurityRule</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> <a href="https://infosec.exchange/tags/confidentiality" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#confidentiality</a> <a href="https://infosec.exchange/tags/insiderthreat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#insiderthreat</a> <a href="https://infosec.exchange/tags/HHS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HHS</a> <a href="https://infosec.exchange/tags/HHSOCR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HHSOCR</a>

Dissent Doe :cupofcoffee:HCF Management healthcare facilities hit by ransomware attack; more than 70,000 patients affected:<a href="https://databreaches.net/2025/01/24/hcf-management-healthcare-facilities-hit-by-ransomware-attack-more-than-70000-patients-affected/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2025/01/24/hcf-management-healthcare-facilities-hit-by-ransomware-attack-more-than-70000-patients-affected/</a><a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a> <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/businessassociate" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#businessassociate</a> <a href="https://infosec.exchange/tags/disclosure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#disclosure</a> <a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a> <a href="https://infosec.exchange/tags/notification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#notification</a> <a href="https://infosec.exchange/tags/RansomHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RansomHub</a>

Dissent Doe :cupofcoffee:NEW: MedSave Health Insurance TPA hacked; firm has yet to comment or respond<a href="https://databreaches.net/2025/01/17/medsave-health-insurance-tpa-hacked-firm-has-yet-to-comment-or-respond/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2025/01/17/medsave-health-insurance-tpa-hacked-firm-has-yet-to-comment-or-respond/</a><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/TPA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TPA</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/hack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hack</a> <a href="https://infosec.exchange/tags/MedSave" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MedSave</a>

Dissent Doe :cupofcoffee:Nine months after discovering a ransomware attack, Teton Orthopaedics notifies patients: <a href="https://databreaches.net/2025/01/12/nine-months-after-discovering-a-ransomware-attack-teton-orthopaedics-notifies-patients/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2025/01/12/nine-months-after-discovering-a-ransomware-attack-teton-orthopaedics-notifies-patients/</a><a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HIPAA</a> <a href="https://infosec.exchange/tags/incidentresponse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#incidentresponse</a> <a href="https://infosec.exchange/tags/DragonForce" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DragonForce</a>

Dissent Doe :cupofcoffee:Westend Dental agrees to pay Indiana $350K and to implement a corrective action plan to settle charges of multiple HIPAA violations.This is one of THE WORST incident responses I have ever read and I've read a lot of bad ones over the years. But it's not just an incident response disaster. They were routinely violating HIPAA privacy and security rules.Kudos to the state of Indiana for going after the dental practice and investigating to find out all the problems. Don't ask me what HHS OCR did, because I don't think they were ever even told about this 2020 ransomware attack.Read more here, where you will also find the court filings I've uploaded so you can read how bad this one was:<a href="https://databreaches.net/2024/12/31/westend-dental-agrees-to-pay-indiana-350k-and-to-implement-corrective-action-plan-to-settle-charges-of-multiple-hipaa-violations/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2024/12/31/westend-dental-agrees-to-pay-indiana-350k-and-to-implement-corrective-action-plan-to-settle-charges-of-multiple-hipaa-violations/</a><a href="https://infosec.exchange/tags/ransomware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransomware</a> <a href="https://infosec.exchange/tags/compliance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#compliance</a> <a href="https://infosec.exchange/tags/HIPAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HIPAA</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a> <a href="https://infosec.exchange/tags/backup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#backup</a> <a href="https://infosec.exchange/tags/PrivacyRule" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PrivacyRule</a> <a href="https://infosec.exchange/tags/SecurityRule" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SecurityRule</a> <a href="https://infosec.exchange/tags/ransparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransparency</a> <a href="https://infosec.exchange/tags/disclosure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#disclosure</a> <a href="https://infosec.exchange/tags/notification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#notification</a> <a href="https://mastodon.social/@zackwhittaker" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@zackwhittaker</a> <a href="https://ioc.exchange/@jgreig" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jgreig</a>

Dissent Doe :cupofcoffee:It appears Brain Cipher did leak the RIBridges data on their leak site, and it appears to be the same data they had provided to me pre-leak and that I described yesterday:<a href="https://databreaches.net/2024/12/30/more-details-emerge-about-ribridges-data-breach-deloitte-tells-state-threat-actors-have-leaked-data/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://databreaches.net/2024/12/30/more-details-emerge-about-ribridges-data-breach-deloitte-tells-state-threat-actors-have-leaked-data/</a>And no, none of the data I inspected was encrypted. The leak site is still iffy to connect to.<a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/ransom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransom</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/govsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#govsec</a> <a href="https://infosec.exchange/tags/Deloitte" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Deloitte</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a>

Dissent Doe :cupofcoffee:<a href="https://infosec.exchange/@chum1ng0" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@chum1ng0</a> The notice on FALP's website today seems to acknowledge they are having some problems, but they do not say it is even a cyberattack. But given their "problems" are occurring at the same time INC claims to have attacked them: heck no, I wouldn't fill out a form giving the entity my name, phone number, and rut. If we assume, for now, that INC did attack them, then we don't know if INC still has access. <a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/disclosure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#disclosure</a> <a href="https://infosec.exchange/tags/transparency" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#transparency</a> <a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://infosec.exchange/tags/FALP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FALP</a> <a href="https://infosec.exchange/tags/LATAM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LATAM</a>

Dissent Doe :cupofcoffee:<a href="https://infosec.exchange/@chum1ng0" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@chum1ng0</a> According to the icons they use for the incident, INC did not encrypt/lock FALP. I'm not sure I understand what the "Stocks" icon means in terms of what they have done, or why nothing is available on FALP's site unless they are just being very cautious and pulled everything down to investigate?<a href="https://infosec.exchange/tags/databreach" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#databreach</a> <a href="https://infosec.exchange/tags/ransom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ransom</a> <a href="https://infosec.exchange/tags/healthsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#healthsec</a> <a href="https://infosec.exchange/tags/Latam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Latam</a> <a href="https://infosec.exchange/tags/oncology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#oncology</a>

Recent searches

Search options

Administered by:

Server stats:

#healthsec