DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 10 filings

American Armed Forces Mutual Aid Association — January 2021 breach

Clustered 10 filings across 10 jurisdictions · filing window Jan 1, 2021 → Mar 12, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

161,621

First → last filing

Jan 1, 2021 → Mar 12, 2021

Merge confidence

100%

incident inc_b40fcbbca14546ae · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Jan 28, 2021–Jan 31, 2021, discovered Jan 29, 2021. 161,621 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 3 more. Notifications rolled out on a 70-day schedule across 10 filings beginning Jan 1, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
22days

Range of discovered_at dates across filings

Filing span
70days

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.

Regulatory clocksWashington⏱ WA AG >30dOregon✓ OR AG ≤45dMaine✓ ME AG ≤30d · 13dMassachusetts✓ MA credit monitoring dueCalifornia✓ CA 60-day OK · 35dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_governmentminor

Incident timeline

Jan 28, 2021breach begins
Jan 29, 2021discovered · members disagree
Jan 1, 2021first filing
Mar 12, 2021most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAR 5MT AGMT AG notice470 MT residents+63d
  3. MAR 5OR AGOR AG noticestates nationwide total 161,621+63d
  4. MAR 5WA AGWA AG notice4,318 WA residents+63d
  5. MAR 5ME AGME AG noticestates nationwide total 161,621+63d
  6. MAR 5IN AGIN AG noticestates nationwide total 161,621+63d
  7. MAR 5MA AGMA AG notice1,058 MA residents+63d
  8. MAR 5SC AGSC AG noticeno count stated+63d
  9. MAR 5CA AGCA AG noticeno count stated+63d
  10. MAR 12NH AGNH AG noticemost recent · 511 NH residents+70d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 28, 2021 – Jan 31, 2021
MT AG
Discovered
Jan 29, 2021IL AG + MT AG + WA AG +3Feb 20, 2021OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · Government ID · Minor · PII
MT AG + WA AG + ME AG +4
Attack vector
Unauthorized Access
MT AG

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)

161,621

Sum of filed state slices

8,404· 5.2% of stated

95% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US161,621
WA4,318
IN1,657
MA1,058
NH511
MT470
ME390

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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 filing10 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.

Filing velocity

Spread

70 days

Cadence

~1 / 7.8d

vs. multi-state median

8.8× 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.