whogothacked

TRUEbenefits LLC data breach record

Is there a breach on record for TRUEbenefits LLC?

Yes. There is one breach incident on record for TRUEbenefits LLC, first reported on August 14, 2017.

Reported to the California Attorney General, the Washington Attorney General and the HHS Office for Civil Rights.

How many
17,309 individuals, per the HHS Office for Civil Rights; 12,327 Washington residents, per the Washington Attorney General. Each figure counts a different group, so they are not added together.
Data listed
Names; social security numbers; health insurance policy or id numbers; medical information.
Source record
Open this record at atg.wa.gov
What to do
Consider a credit freeze; review medical and insurance statements. If you received a notice letter, start with the letter.

Get a daily email of new incidents

Email alerts

We use your address only for these alerts and to run and test the service (privacy). Want only SEC filings? Sign up on the alerts page.

Sector
Human Resources
State
Washington

Was TRUEbenefits LLC hacked?

A source record describes a cyberattack. For the incident first reported on August 14, 2017, the record from the Washington Attorney General gives the cause as “Cyberattack: Phishing”.

The HHS Office for Civil Rights describes what happened in its own words. That description is quoted with the incident below.

A filing shows who notified the regulator. The filer is sometimes a vendor or a customer of the firm whose systems were affected, so a filing on its own does not establish whose systems were broken into.

The incident on record

First on recordper the HHS Office for Civil Rights and the Washington Attorney General

Official record

3 source records

TRUEbenefits LLC reported a data breach to the US Department of Health and Human Services Office for Civil Rights, the Washington Attorney General and the California Attorney General. The first of 3 notices was filed on August 14, 2017 and the latest on September 18, 2017. The filings give May 18, 2017 and May 19, 2017 as dates of the breach. The Washington filing says the organization became aware of it on June 26, 2017. The HHS filing puts the number of individuals affected at 17,309. The Washington filing puts the number of Washington residents affected at 12,327. These figures count different groups and are not added together. The HHS filing lists the type of breach as "Hacking/IT Incident (location of breached information: Email)". The Washington filing lists the cause as "Cyberattack: Phishing". The Washington filing lists the information involved as: names, social security numbers, health insurance policy or id numbers, medical information.

Breach dated
May 18, 2017 and May 19, 2017
Discovered
June 26, 2017
Latest filing
September 18, 2017

Figures on record

  • 17,309individualsper the HHS Office for Civil Rights
  • 12,327Washington residentsper the Washington Attorney General

Each figure counts a different group, so they are not added together.

Cause on record

Listed by HHS as “Hacking/IT Incident”. Phishing.

Data exposed, as the sources list it

  • names
  • social security numbers
  • health insurance policy or id numbers
  • medical information

The records behind this entry

  1. First record

    Listed on the HHS Office for Civil Rights breach portal under the name TRUEbenefits LLC.

    On this record: 17,309 individuals; cause given as “Hacking/IT Incident (location of breached information: Email)”.

    In the words of the HHS Office for Civil Rights

    An unauthorized person accessed an employee’s email account after it was compromised by a phishing incident and some of the emails accessible through the account contained electronic protected health information (ePHI). The breach affected approximately 17,309 individuals who were members of employer health plans administered by TRUEBenefits, LLC (TB). The PHI involved in the breach included demographic, financial, and clinical information.

    Show the rest of this text (96 more words)Hide the rest of this text

    TB provided breach notification to HHS, covered entities, affected individuals, and the media in all 50 states and Puerto Rico, and also provided substitute notice. Upon discovery of the breach, TB immediately reset the employee’s password, disabled the loaner laptop the employee was using, and removed remote email access capabilities from the employee’s phone. In response to the breach, TB offered potentially affected individuals with two years of credit monitoring and made improvements to its ePHI systems’ data loss prevention and access rights management features. OCR obtained assurances that TB implemented the corrective actions noted above.

    • Open the HHS list of HIPAA breach reports at ocrportal.hhs.govThe HHS breach portal has no page for each report. On its list, look for “TRUEbenefits LLC” (WA) with the breach submission date 08/14/2017. Reports older than 24 months are on its Archive tab. Show Advanced Options can search the list by name (CE / BA Name Search) and by submission date.
  2. Update

    Breach notice filed with the Washington Attorney General under the name TRUEbenefits LLC.

    On this record: 12,327 Washington residents; cause given as “Cyberattack: Phishing”; discovered Jun 26, 2017.

    This record lists these kinds of data: names; social security numbers; health insurance policy or id numbers; medical information.

  3. Update

    Breach notice filed with the California Attorney General under the name TRUEbenefits LLC.

    On this record: breach dated May 18, 2017 and May 19, 2017.

What to do if this involved you

  • Consider a credit freeze

    A freeze stops new credit being opened in your name. It is free, and you place it yourself with each of the three US credit bureaus: Equifax, Experian and TransUnion. You can check your credit reports for free as well.

    Free credit reports at AnnualCreditReport.com

  • Review medical and insurance statements

    Check statements from your insurer and providers for care you did not receive, and tell your insurer about anything that is not yours.

These steps follow from the kinds of data the sources list. If you have a notice letter, start with the letter.

If you received a notice letter

  • Keep the letter

    It names the incident and lists which of your details were involved. The letter, not this page, is the authority on what happened to your data.

  • Use any free monitoring it offers

    Many notices include free credit monitoring with an enrollment code and a deadline. Enroll using the instructions printed in the letter, not a link from an email or text.

  • Check that the letter is real

    Compare it with the source records linked on this page. If you are unsure, contact the organization using a phone number or address from its own website, not one printed in a message you were sent.

  • If your identity is misused, report it

    The Federal Trade Commission's IdentityTheft.gov gives you a recovery plan and the forms to send.

    Report identity theft at IdentityTheft.gov

About this record

Official record: A regulator filing or the organization's own disclosure exists.

Being on record here is not a finding that TRUEbenefits LLC did anything wrong or broke any law. This page reports what the source records say, and no more.

Every fact on this page comes from the source records linked above. The steps for people who received a letter are general guidance, not part of the record. How records are verified

Something wrong here? See how to dispute an entry, or write to corrections@whogothacked.com.

The same record for software: /api/v1/orgs/truebenefits-llc