DataBreaches.Net

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

Wise Health updates its breach notification of last summer

Posted on February 17, 2020 by Dissent

In July 2019, this site noted that Wise Health in Texas had notified HHS about a HIPAA breach impacting 35,899 patients. The report concerned a phishing incident in March, 2019 that was discovered in April, 2019.

Last week, Wise Health issued another press release, reproduced below. At first blush, it might sound like a new incident, but it appears to be the same incident, although the provider does not explain why it took so long to identify the additional 31,000 patients who required notification.


DECATUR, Texas, Feb. 13, 2020 /PRNewswire/ — Wise Health System in Decatur, TX, has started sending notifications to patients to inform them that some of their protected health information (PHI) has been exposed as a result of a phishing attack. 66,934 patients have potentially been affected.

The attack occurred on March 14, 2019. Several employees received phishing emails and some responded and disclosed their account credentials. The credentials were then used to gain access to the Employee Kiosk, where the attacker(s) attempted to reroute payroll direct deposits. Attempts were made to redirect approximately 100 direct deposit payments.

Wise Health had policies in place that require a paper check to be printed for two successive payrolls following a change to direct deposit information. The checks were printed in the payroll on April 5, 2019 and the unusually high number of checks raised the alarm, thanks to the two-check policy.  A system-wide password change was immediately performed to lock out the attackers and two third-party forensic firms were hired to investigate the breach. The breach was also reported to the FBI.

The sole purpose of the attack appears to have been to reroute direct deposits, although the stolen credentials would have allowed access to be gained to employee email accounts. Those accounts contained patients’ names, medical record numbers, diagnostic information, treatment information, and health insurance information.

Wise Health System does not believe PHI was accessed by the attackers and there have been no confirmed reports that patient information has been misused. Both forensics firms and the FBI share that point of view. The investigators all agreed they have never seen a direct deposit attack such as this where the attackers have stolen patient data. These gangs specialize in direct deposit fraud. The attackers in this case were traced to Africa by the FBI, which has now closed its investigation.

A data audit was completed to determine the scope and nature of the information potentially compromised, which began in June 2019 and was recently completed. Since unauthorized PHI access and data theft could not be ruled out, to ensure patients are protected, notification letters were sent on February 13, 2020, and affected patients have been offered between twelve and twenty four (12-24) months of complimentary membership to ID Experts MyIDCare service, which includes credit monitoring, identity theft recovery, and insurance coverage.

Wise Health System has reviewed its security policies and procedures and has taken numerous steps to reinforce security. Additionally, Wise Health System has established an informational line for potentially impacted individuals to call at (940) 539-3500 or (940) 627-5921 ext. 9088.

SOURCE Wise Health System


While it is probably the case that the attack was targeting employee payroll, how will HHS view the fact that some patients were not notified for 10 months following discovery of an incident?

And once again, how much of this incident could have been reduced if there wasn’t so much PHI in employee email accounts? Was all of it current and necessary or could it have been moved out of the employees’ email accounts already?


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 DataPhishingU.S.

Post navigation

← TX: Port Lavaca City Hall won’t pay $200k ransom demand; working to recover from Ryuk attack
UK: Redcar cyber-attack: Council using pen and paper →

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

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • 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

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

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • 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

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.