Central Carolina Insurance Agency
bd_2bcbfaea9f93c203 · schema v1 · pii pii-v1
Full breach record for Central Carolina Insurance Agency →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group BianLian on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Central Carolina Insurance Agency is an independent insurance firm that began operations in Rowan County in 1931, and the organization grew in the 1980’s with an expansion into Mooresville. In 2017 we added R3; Risk, Reduction Resources to our firm to diversify Central Carolina’s tenure and clout in the insurance industry and to promote a more holistic approach to risk management.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Apr 9, 2024
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (5) · sorted by filing gap
- Vermont State AGbd_0c4fbe9be2c1778a2024-11-21 · +225dVerified
- Massachusetts State AGbd_7b621deb402273332024-11-21 · +225dVerified by operator
- Indiana State AGbd_e97365ae56e4d7822024-11-21 · +225dVerified
- Maine State AGbd_ecb4c0429af064742024-11-21 · +225dCandidate
Show 1 more filing ↓Show fewer ↑up to 237d gap
- New Hampshire State AGbd_a9edb2493a65ebea2024-12-03 · +237dVerified
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Apr 9, last Dec 3 (NH) — a 237-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
bianlian
According to ransomware.live, BianLian ransomware operations began in late 2021. The group practices multi-pronged extortion, demanding payment for a decryptor, as well as the non-release of stolen data. The ransomware group hosts a public, TOR-based, blog to post victim identities and stolen data. Somewhat unique to BianLian at the time of their launch was their inclusion of an I2P mirror for their blog.