DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed6 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedalphvhigh sensitivity
Merged incident · 6 filings

Swissport North America, Inc. — February 2022 breach

Clustered 6 filings across 6 jurisdictions · filing window Feb 15, 2022 → Oct 3, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

1,733

First → last filing

Feb 15, 2022 → Oct 3, 2022

Merge confidence

100%

incident inc_aaa8015d7f6a48f2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe malware. Intrusion Feb 1, 2022–Feb 3, 2022, discovered Feb 3, 2022 — the first regulatory filing landed 238 days later (flagged late). 1,733 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 230-day schedule across 5 filings beginning Feb 15, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
238days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
226days before filing

Days between the first leak-site claim and the first regulatory filing. 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
230days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 1, 2022breach begins
Feb 3, 2022discovered
notification delay · 238 days
Sep 29, 2022first filing
Oct 3, 2022most 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. FEB 15Leak sitealphv postfirst filing · attacker claim · unverifiedday 0
  2. SEP 29WA AGWA AG notice1,131 WA residents+226d
  3. SEP 29MT AGMT AG notice1 MT residents+226d
  4. SEP 29IN AGIN AG noticestates nationwide total 1,733+226d
  5. SEP 29MA AGMA AG notice6 MA residents+226d
  6. OCT 3NH AGNH AG noticemost recent · 1 NH residents+230d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 1, 2022 – Feb 3, 2022
WA AG
Discovered
Feb 3, 2022· 2d undetected
WA AG + MT AG + NH AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + MT AG + NH AG +1
Attack vector
Ransomware
WA 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)

1,733

Sum of filed state slices

1,141· 65.8% of stated

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

US1,733
WA1,131
MA6
IN2
MT1
NH1

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 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 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

230 days

Cadence

~1 / 46d

vs. multi-state median

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