HackingManufacturingManufacturingEmployee Data InvolvedPIIIdentity (basic)Government IDEmploymentMediumContained

Craft Beer Company GP

bd_bcdcb5d9efc59a76 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Mar 5, 2024

Filed

May 13, 2024

To disclose

10 weeks

Affected

1state residents only

Linked

3 filings

Confidence

66%

Full breach record for Craft Beer Company GP →2 incidents on file

Craft Beer Company GP discovered unauthorized third-party access to its network on March 5, 2024. The incident affected current and former employees, spouses, and dependents. Data compromised may include names, addresses, SSNs, and passports. The company contained the incident by taking systems offline and engaged forensic experts. Notifications began May 8, 2024. 1 New Hampshire resident and 3 Rhode Island residents were explicitly noted as affected in the filing.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 10 weeks / 69 days

Mar 5, 2024

Discovered

May 13, 2024

Filed

vs. sector median

1 wks faster

This filing is one of 3 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (2) · sorted by filing gap

Maine State AGbd_150e1b9bf19ebf522024-05-08 · +5dCandidate
Maryland State AGbd_b059725b3401cc5e2025-11-13 · +549dVerified

Name: Craft Beer Company GP
norm: craft beer company gp

Name: Craft Beer Company GP
norm: craft beer company gp
Industry: Manufacturingllm

Discovered: Mar 5, 2024
Materiality determined: —
Notification sent: May 8, 2024
Affected individuals: 1state-resident count only
Data types: PIIIdentity (basic)Government IDEmployment
Attack vector: Unknown
Threat actor: External
Regulator citations: Notified New Hampshire Attorney General

During the incident: Taking its network offline
Retaining outside forensic firms to respond, investigate, and remediate the incident
Notifying law enforcement
Isolated all sites
Shut down servers
Disconnected our system from the internet
Launched an internal investigation
Engaged external cybersecurity forensic experts
Implemented the experts’ recommended actions to prevent the disclosure of data
Changes made: Re-training our staff to address how the incident occurred
Reviewing and updating our policies and procedures to further harden our cybersecurity program
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 10 weeks(69 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings · 3 states

View merged incident ↗

Maine State AGMay 8 · first

New Hampshire State AG+5d · this page

Maryland State AG+554d

Pattern: first filing May 8 (ME), last Nov 13 (MD) — a 554-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://mm.nh.gov/files/uploads/doj/remote-docs/craft-beer-gp-20240513.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 13, 2024
Raw hash: 38e646f50cbce67db00b251c5cf07039f206eb863c47f3058111cc9724c29e17

Linked disclosures

Regulatory filings (2) · sorted by filing gap

Reporting entityCraft Beer Company GP

Victim entityCraft Beer Company GP

Incidentdiscovered Mar 5, 2024

Stated responseTaking its network offline

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancemm.nh.gov