Disclosures Claims Reports Entities Incidents Pulse

Feed live

DisclosureLens

Structured extracts of public breach disclosures — regulator filings (SEC, HHS, state AGs, EU DPAs) alongside threat-actor leak-site claims and press reports. SEC and HHS filings render inline from the originating regulator’s public record under the fair report privilege; other sources link out to the source URL. AI-extracted with full per-record audit trail (model, prompt version, confidence).

ai_assisted: true · Article 50 disclosure on every record

Product

Disclosures feed
Pulse · analytics
Entities
Breach notifications by state

Methodology

How extraction works
Confidence & review
About the bot

Trust

Security
Self-disclosure commitment
API documentation
API keys

v0.1.0 · coverage growing weekly

Cameron & Mittleman data breach (2025) · DisclosureLens

All incidents View linkage analytics →

Merged incident · 2 filings

Cameron & Mittleman

Clustered 2 filings across 2 jurisdictions · filed Feb 10, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Confirmed breach. Intrusion Dec 13, 2024, discovered Dec 13, 2024 — the first regulatory filing landed 59 days later. 4 individuals reported across the linked filings.

incident inc_ed5a9593a4084ea3 · merge_method deterministic · confidence 100%

Litigation Timing

Notification delay

59days

Discovered → first regulatory filing

Discovery variance

47days

Range of discovered_at dates across filings

Filing span

Regulatory clocksMaine✓ ME AG ≤30d · 12dFull clock table in Litigation Timeline

State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity

Affected (total reported)

Data types

Identity (basic)

0days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Jurisdictions

ME NH

Linked filings

all State AG

Timeline

Earliest sighting first · deep chronology in Litigation Timeline

Breach window
Dec 13, 2024
When the intrusion reportedly occurred, per the linked filings
Breach discoveredletter-grounded
Dec 13, 2024
Reported by NEW HAMPSHIRE AG filing
47 days
Breach discoveredconflicts with Dec 13, 2024
Jan 29, 2025
Reported by MAINE AG filing
⛰️New Hampshire State AGFirst filinglinked via multistate filing link · 100%
Filed Feb 10, 2025bd_566f41b06d3b9e4c
Cameron & Mittleman LLP reported a security incident to the NH AG on Feb 10, 2025. Unusual activity detected on Dec 13, 2024. Personal info of 3 NH residents affected. Law enforcement notified; credit monitoring offered.
Affected (this filing): 3
🦞Maine State AGMost recent
Filed Feb 10, 2025bd_bc691ec7f66fb77f
Cameron & Mittleman LLP, a law firm, experienced an external system breach (hacking) on December 13, 2024, which was discovered on January 29, 2025. The breach affected one resident of Maine. In response, the firm offered 24 months of credit monitoring and identity theft remediation services through CyberScout.
Affected (this filing): 1
ME AG ≤30d · 12d

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.