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

5.11, Inc — July 2024 breach

Clustered 10 filings across 10 jurisdictions · filing window Oct 4, 2024 → Oct 10, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

27,742

First → last dated filing

Oct 4, 2024 → Oct 10, 2024

Merge confidence

100%

incident inc_7d579ab2af6d4dbc · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Jul 12, 2024–Aug 22, 2024, discovered Jul 12, 2024. 27,742 individuals reported across the linked filings. Data reported: PII, PCI, Identity (basic), and 2 more. Notifications rolled out on a 6-day schedule across 9 dated filings beginning Oct 4, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
62days

Range of discovered_at dates across filings

Filing span
6days

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 clocksCalifornia✗ CA 60-day late · 63dVermont⏱ VT AG >14 bdayWashington⏱ WA AG >30dDate basis✓ Clock withheld · confirmation dateFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Jul 12, 2024breach begins
Jul 12, 2024discovered · members disagree
Oct 4, 2024first dated filing
Oct 10, 2024most 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 about this breach

  1. OCT 1IL AGIL AG noticefiling day not on record · no count stated—
  2. OCT 4MT AGMT AG noticefirst filing · 150 MT residentsday 0
  3. OCT 4IN AGIN AG noticestates nationwide total 27,742day 0
  4. OCT 4VT AGVT AG noticeno count statedday 0
  5. OCT 5CA AGCA AG noticeno count stated+1d
  6. OCT 5MA AGMA AG notice488 MA residents+1d
  7. OCT 5OR AGOR AG noticestates nationwide total 27,742+1d
  8. OCT 5ME AGME AG noticestates nationwide total 27,742+1d
  9. OCT 5WA AGWA AG notice699 WA residents+1d
  10. OCT 10NH AGNH AG noticemost recent · 170 NH residents+6d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 12, 2024 – Aug 22, 2024
MT AG
Discovered
Jul 12, 2024IL AGAug 1, 2024MT AG + VT AG + CA AGAug 5, 2024WA AG + NH AGSep 12, 2024OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
MT AG + WA AG + NH 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)

27,742

Sum of filed state slices

2,144· 7.7% of stated

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

US27,742
WA699
IN510
MA488
NH170
MT150
ME127

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

6 days

Cadence

~1 / 0.8d

vs. multi-state median

1.0× faster

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.