Social EngineeringFinancial ServicesFinancePhishingStolen CredentialsData ExfiltratedEmployee Data InvolvedIdentity (basic)PIILowResolved

CRC Insurance Services, LLC

bd_609f8e75669d9e57 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jan 18, 2023

Filed

Jul 26, 2023

To disclose

27 weeks

Affected

Not disclosed

Linked

5 filings

Confidence

65%

Full breach record for CRC Insurance Services, LLC →5 incidents on file

CRC Insurance Services, LLC reported that on January 18, 2023, it determined an unknown third-party gained unauthorized access to a small number of employee email accounts via phishing emails. The actor exfiltrated a small percentage of emails. The breach occurred on January 13, 2023. Affected data may include names, addresses, and other personal information. CRC engaged forensic firms, contained the incident, and offered credit monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 5 days

discovery → filing · 27 weeks / 189 days

Jan 13, 2023

Begins

Jan 18, 2023

Discovered

Jul 26, 2023

Filed

vs. sector median

+19 wks slower

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Massachusetts State AGbd_5faa258d18d7138f2023-07-26Verified
Montana State AGbd_684512eb7188bc5d2023-07-26Verified
Idaho State AGbd_ef08d8fabbad4f622023-07-26Verified
Vermont State AGbd_97f391745ea166b72023-07-19 · +7dVerified

Name: CRC Insurance Services, LLC
norm: crc insurance

Name: CRC Insurance Services, LLC
norm: crc insurance
Industry: Financial Servicesllm

Discovered: Jan 18, 2023
Breach occurred: Jan 13, 2023
Undetected for: 5 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: Identity (basic)PII
Attack vector: Phishing
MITRE ATT&CK: T1566.002 Spearphishing LinkT1114 Email CollectionT1041 Exfiltration Over C2 Channel
Threat actor: External
Initial access: phishing_link

During the incident: Activated its incident response team to secure the affected accounts and contain the incident
Conducted a legal and technical investigation of the incident, including engagements with leading forensic and data analytics firms
Sent timely alert communications to all its employees
Provided additional training to CRC employees impacted by the phishing attack
Changes made: Offering complementary credit monitoring services from Equifax
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Vermont State AGJul 19 · first

Massachusetts State AG+7d

Montana State AG+7d

Idaho State AG+7d

California State AG+7d · this page

Pattern: first filing Jul 19 (VT), last Jul 26 (CA) — a 7-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://oag.ca.gov/ecrime/databreach/reports/sb24-570861
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jul 26, 2023
Raw hash: 9c8a4b160a32b12b5872fc7ff74ec438f9a1d37c9e1820fb08d8898a69f33aa2

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityCRC Insurance Services, LLC

Victim entityCRC Insurance Services, LLC

Incidentdiscovered Jan 18, 2023

Stated responseActivated its incident response team to secure the affected accounts and contain the incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov