whogothacked

Crimson Wine Group data breach record

Is there a breach on record for Crimson Wine Group?

Yes. There is one breach incident on record for Crimson Wine Group, disclosed to the SEC on July 25, 2024.

Reported to the Washington Attorney General; disclosed to the SEC on Form 8-K.

How many
3,436 Washington residents, per the Washington Attorney General.
Data listed
Names; social security numbers; driver's license or state id numbers; financial and banking information; dates of birth; and 4 more.
Source record
Open this record at sec.gov
What to do
Consider a credit freeze; check your statements; 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.

Also filed as
Crimson Wine Group, Ltd
Sector
Beverages
State
California
Ticker
CWGL as of its latest SEC filing on record (shown to identify the company; nothing on this page is investment advice)

Was Crimson Wine Group hacked?

A source record describes a cyberattack. For the incident disclosed to the SEC on July 25, 2024, the record from the Washington Attorney General gives the cause as “Cyberattack: Ransomware”.

The company's Form 8-K filing 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 SEC

Official record

2 source records

Crimson Wine Group reported a data breach to the Washington Attorney General in a notice filed on December 13, 2024. Crimson Wine Group also filed a Form 8-K under Item 1.05 (Material Cybersecurity Incidents) disclosing a cybersecurity incident to the US Securities and Exchange Commission on July 25, 2024. Breach dates in the filings run from June 26, 2024 to June 30, 2024. The Washington filing says the organization became aware of it on June 30, 2024. The Washington filing puts the number of Washington residents affected at 3,436. The Washington filing lists the cause as "Cyberattack: Ransomware". The Washington filing lists the information involved as: names, social security numbers, driver's license or state id numbers, financial and banking information, dates of birth, military id numbers, passport numbers, health insurance policy or id numbers, medical information.

Breach dated
June 26, 2024 to June 30, 2024
Discovered
June 30, 2024
Latest filing
December 13, 2024

Figures on record

  • 3,436Washington residentsper the Washington Attorney General

This figure counts only the group named beside it.

Cause on record

Ransomware.

Data exposed, as the sources list it

  • names
  • social security numbers
  • driver's license or state id numbers
  • financial and banking information
  • dates of birth
  • military id numbers
  • passport numbers
  • health insurance policy or id numbers
  • medical information

The records behind this entry

  1. First record

    Form 8-K Item 1.05 filed with the SEC under the name Crimson Wine Group, Ltd.

    In the company's own words, from its Form 8-K under Item 1.05 (Material Cybersecurity Incidents)

    As previously disclosed on the Current Report on Form 8-K filed by Crimson Wine Group, Ltd. (the “Company”) on July 5, 2024 (the “Initial Report”), on June 30, 2024, the Company detected a cybersecurity incident in which an unauthorized third party gained access to certain information systems of the Company.

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

    Upon detection, the Company promptly initiated response protocols and began taking steps to contain, assess and remediate the cybersecurity incident, including launching an investigation with external cybersecurity experts. As the Company was in early stages of its investigation and assessment of the incident, it was unable to determine at the time of the Initial Report whether the incident had or will have a material impact on the Company.

    On July 25, 2024, the Company determined that the cybersecurity incident has likely had a material impact on the Company’s business operations. The incident consisted of the third party’s unauthorized access to a portion of the Company’s internal information systems and the exfiltration of certain files, including files potentially containing sensitive personal information. The Company is still investigating the extent of any personal or otherwise sensitive information contained in the files acquired by the unauthorized third party, including if any personal information of customers was impacted. The Company intends to provide required notifications to affected and potentially affected parties and to applicable regulatory agencies. As part of its process to contain, assess and remediate the incident, the Company took measures, including shutting down certain of its systems, to isolate its operations from the Internet, which resulted in disruption to the Company’s business operations, despite the implementation of workarounds for certain offline operations, and limitation of access to portions of the Company’s business applications supporting aspects of the Company’s operations and corporate functions, including financial and operating reporting systems. Although the Company has substantially restored its information systems and data that were impacted by the cybersecurity incident and has resumed normal business operations, it continues to assess operational impacts and evaluate additional measures to strengthen its surveillance of cybersecurity threats and to prevent unauthorized cybersecurity incidents on or conducted through its information systems and to strengthen its information backup protocols.

    Although the Company has determined that the cybersecurity incident has likely had a material impact on the Company’s business operations, as of the date of this Current Report on Form 8-K, the Company believes that the cybersecurity incident has not had a material impact on the Company’s overall financial condition or results of operations. and the Company does not believe the cybersecurity incident is reasonably likely to materially impact the Company’s overall financial condition or results of operations. The Company believes it holds adequate cybersecurity insurance to offset a substantial portion of the costs of the cybersecurity incident; however, the Company may incur expenses and losses related to this incident that are not covered by insurance. To the extent the Company incurs future, material direct expenses or other losses as result of this cybersecurity incident, and those costs are not covered by insurance, the Company will report such material losses in the appropriate period.

    The Company remains subject to various risks due to the cybersecurity incident, including potential litigation, changes in customer behavior, additional regulatory scrutiny, and the

    subsequent availability of, or increase in cost to the Company of, its insurance policy covering cybersecurity incidents.

  2. Update

    Breach notice filed with the Washington Attorney General under the name Crimson Wine Group.

    On this record: 3,436 Washington residents; cause given as “Cyberattack: Ransomware”; breach dated Jun 26, 2024 to Jun 30, 2024; discovered Jun 30, 2024.

    This record lists these kinds of data: names; social security numbers; driver's license or state id numbers; financial and banking information; dates of birth; military id numbers; passport numbers; health insurance policy or id numbers; medical information.

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

  • Check your statements

    Look through recent card and bank statements for charges you do not recognize, and report any to your bank or card issuer. If your full card number was involved, ask for a replacement card.

  • 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 Crimson Wine Group 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/crimson-wine-group