BRANDYWINE REALTY TRUST — March 2024 breach
Clustered 4 filings across 3 jurisdictions · filing window May 7, 2024 → Aug 6, 2024. View entity profile → Other incidents for this victim →
incident inc_6e1112ba9d0c4382 · merged by human · confidence 100%
Litigation Timing
Discovered → first regulatory filing
Range of discovered_at dates across filings
Discovery to SEC materiality determination
Materiality determination to SEC 8-K filing
Time between earliest and latest filing
Not recorded for this incident
Leak precedence — no leak-site claim in this cluster.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- MAY 7SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
- MAY 28SEC 8-KSEC 8-K noticeno count statedauto-linked+21d
- AUG 6ME AGME AG noticestates nationwide total 2,934operator-confirmed+91d
- AUG 6NH AGNH AG noticemost recent · 1 NH residentsoperator-confirmed+91d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Mar 18, 2024 – May 1, 2024 ME AG
- Discovered
- May 1, 2024· 44d undetected SEC 8-K + ME AG + NH AG
- Data types
- Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII SEC 8-K + ME AG + NH AG
- Attack vector
- Ransomware SEC 8-K
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Count reconciliation
per-state reported counts
Nationwide (stated in a filing)
2,934
Sum of filed state slices
7· 0.2% of stated
100% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Merge provenance
- Method
- human
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Aug 9, 2026 · at least one link edge was human-adjudicated
- 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.
Filing velocity
Spread
91 days
Cadence
~1 / 30.3d
vs. multi-state median
10.1× slower
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.