Carolina Arthritis
bd_afad31b5e423fe58 · schema v1 · pii pii-v1
Full breach record for Carolina Arthritis →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Threeam 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
Welcome to Carolina Arthritis Since its founding in 1991, Carolina Arthritis has been leading the way in the diagnosis and treatment of arthritis, musculoskeletal disorders, connective tissue diseases, autoimmune illnesses and osteoporosis. At...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 24, 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 (8) · sorted by filing gap
- New Hampshire State AGbd_25b183630cee60062025-02-27 · +125dVerified
- Maine State AGbd_3e3faec2dc9622c02025-02-27 · +125dVerified
- HHS OCRbd_47d1979d018b1d022025-02-27 · +125dVerified
- Vermont State AGbd_5c4c73fe342044712025-02-27 · +125dVerified
Show 4 more filings ↓Show fewer ↑up to 126d gap
- Massachusetts State AGbd_7da192a3e413a7502025-02-27 · +125dVerified by operator
- Indiana State AGbd_7f5415b879da33172025-02-27 · +125dVerified
- Maryland State AGbd_8076b43f1a07995d2025-02-27 · +125dVerified
- South Carolina State AGbd_52246c1ac05955052025-02-28 · +126dVerified
Filing propagation · 9 filings · 8 states
View merged incident ↗Pattern: first filing Oct 24, last Feb 28 (SC) — a 126-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.
threeam
According to ransomware.live, A new Ransomware family identified by the name '3AM' or 'ThreeAM' in September 2023. The ransomware operation was observed by the Symantec team, in which a ransomware affiliate attempted to deploy another ransomware, LockBit, on the target network and then switched to 3AM when LockBit was reportedly blocked. > > The ransomware operation, according to the publication on its Tor-based website, has been operating since mid-August 2023, according to the publication from its first victim. Source: https://github.com/crocodyli/ThreatActors-TTPs