Stram Center for Integrative Medicine — January 2025 breach

Clustered 3 filings across 3 jurisdictions · filed Feb 28, 2025 (dated filings only). View entity profile → Other incidents for this victim →

✓ affected count, discovery date agreeMerge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

15,263

First → last dated filing

Feb 28, 2025

Merge confidence

100%

incident inc_2c525fd48ed54fc9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filing describes unauthorized access. Intrusion Jan 2, 2025, discovered Jan 2, 2025. 15,263 individuals reported across the linked filings. Data reported: PHI, Health (basic), and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance

0days

Range of discovered_at dates across filings

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Incident timeline

Jan 2, 2025breach begins

Jan 2, 2025discovered

Feb 28, 2025first dated filing

—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

FEB 1IL AGIL AG noticefiling day not on record · no count stated—
FEB 28NE AGNE AG noticefiling day not on record · no count statedauto-linked—
FEB 28HHS OCRHHS OCR noticefirst filing · states nationwide total 15,263day 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jan 2, 2025
Discovered: Jan 2, 2025
Data types: PHI · Health (basic) · Identity (basic)
Attack vector: Unauthorized Access

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing3 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method: deterministic
Confidence: 1.00 · above the 0.85 auto-merge floor
Audit: Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.