DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed6 records · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedinc_ransomhigh sensitivity
Merged incident · 6 records

INTERNATIONAL AIDS VACCINE INITIATIVE, INC. — December 2024 breach

Clustered 6 records across 4 jurisdictions: 5 filings and 1 leak-site claim · filing window Jan 17, 2025 → Jan 27, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 records

States

4

Affected · reported

49

First → last dated filing

Jan 17, 2025 → Jan 27, 2025

Merge confidence

100%

incident inc_4d7b491baeda4bcb · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Dec 18, 2024–Dec 22, 2024, discovered Dec 22, 2024 — the first regulatory filing landed 26 days later. 49 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 10-day schedule across 3 dated filings beginning Jan 17, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
26days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 10d

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
10days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont⏱ VT AG >14 bdayMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 18, 2024breach begins
Dec 22, 2024discovered
notification delay · 26 days
Jan 17, 2025first dated filing
Jan 27, 2025most recent dated filing

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 and leak-site claim in this incident

  1. JAN 17VT AGVT AG noticefirst filing · no count statedday 0
  2. JAN 22MA AGMA AG notice9 MA residents+5d
  3. JAN 27NH AGNH AG notice5 NH residents+10d
  4. JAN 27Leak siteinc_ransom postmost recent · attacker claim · unverified+10d
  5. NOV 13MD AGMD AG noticefiling day not on record · 35 MD residents—
  6. NOV 13MD AGMD AG noticefiling day not on record · 35 MD residents—
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 18, 2024 – Dec 22, 2024
VT AG
Discovered
Dec 22, 2024· 4d undetected
VT AG + NH AG + MD AG
Data types
Employment · Identity (basic) · Government ID · PII
VT AG + NH AG + MD AG +1
Attack vector
Unauthorized Access
VT AG

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

Affected residents by state

per-state reported counts

MD35
MA9
NH5

State AGs report only their own residents; teal bars show each state's reported slice.

Evidence ladder — rungs this incident occupies

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing5 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 23, 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

10 days

Cadence

~1 / 5d

vs. multi-state median

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