DataBreaches.Net

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

Talbert House issues press release about June security incident

Posted on September 11, 2021 by Dissent

In July, DataBreaches.net reported on a breach involving Talbert House that had been listed on the “Marketo” leak site, a site where hacked or leaked data is stolen (the site has no connection whatsoever to Adobe’s Marketo).  As reported at the time, Talbert House is an agency in Ohio with a network of services focusing on prevention, assessment, treatment and reintegration for clients with a variety of issues, including issues with alcohol and/or drug use and mental health.

At the time of the listing, DataBreaches.net could find no coverage anywhere of any breach and reached out to Talbert House to inquire. Talbert House then posted a notice on their site that day to say that they had become aware of a breach on June 11 after being alerted to suspicious activity by one of their vendors, and were still investigating to determine its scope.

Based on the data provided to this site by Marketo, there appeared to be personal and sensitive information involved.

Yesterday, Talbert House issued a press release saying that it has begun notifying individuals. They write, in part:

While the investigation is still ongoing, we have determined that the unauthorized third party accessed and acquired files containing information of clients, employees, partners, and some other third-parties. Those files included clients’ protected health information, such as: first and last name, full mailing address, medical information and health insurance information. For employees, partners and some other third-parties, Social Security Numbers, driver’s license numbers, and financial account information may have been accessed.

Talbert House is offering complimentary credit monitoring and identity theft protection services to individuals whose personal information has been impacted, even though there has been no indication of misuse at this time.

A copy of the full notice is available on their web site. It does not state that their files were ever encrypted — only that they were accessed and acquired. It does not indicate how much ransom was demanded or whether they paid any ransom. And significantly, perhaps, DataBreaches.net does not see Talbert House listed on Marketo’s site any more. Was ransom paid to get them to remove the listing or did someone buy the data, or….?

Talbert House’s press release also does not indicate how many people are being notified. This incident has not appeared on HHS’s breach tool and it’s not clear if that means that less than 500 patients were impacted or it just hasn’t shown up yet.

DataBreaches.net sent a follow-up email to Talbert House to put those questions to them, but no response has been received as yet. Neither has Marketo responded to an inquiry this site put to it about the removal of the listing from their site.

This post will be updated when this site gets some answers or clarification.

Update of September 24: This incident was reported to HHS as impacting 45,000 patients.

 


Related:

  • John Bolton Indictment Provides Interesting Details About Hack of His AOL Account and Extortion Attempt
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • No Kings. Not Today. Not Ever.
  • BreachForums Seized -- Again!
  • The Identity Theft Resource Center Remains Open to Victims Amid Government Shutdown
  • Legal Practice Board of Western Australia begins notifying data breach victims
Category: Miscellaneous

Post navigation

← NY: Rehabilitation Support Services notifies clients and employees of data breach
Anonymous hacks Texas GOP website, floods it with memes →

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.