DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
SEC 8-KConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Merged incident · 2 filings

STRYKER CORPORATION

Clustered 2 filings across 1 jurisdiction · filing window Mar 12, 2026 → Mar 23, 2026. View entity profile → Other incidents for this victim →

Agreement not assessableMerge100%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

—

First → last filing

Mar 12, 2026 → Mar 23, 2026

Merge confidence

100%

incident inc_dc4cc11d0a404ec5 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes unauthorized access. Discovered Mar 11, 2026 — the first regulatory filing landed 1 days later. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
1days

Discovered → first regulatory filing

Materiality delta
1days

Discovery to SEC materiality determination

SEC filing delay
0days

Materiality determination to SEC 8-K filing

Filing span
11days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence — no leak-site claim in this cluster; needs two dated filings.

Incident timeline

? — ?breach window unknown
Mar 11, 2026discovered
notification delay · 1 days
Mar 12, 2026first filing
Mar 23, 2026most 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. MAR 12SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. MAR 23SEC 8-KSEC 8-K noticemost recent · no count stated+11d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
—
Discovered
Mar 11, 2026
SEC 8-K
Attack vector
Unauthorized Access
SEC 8-K

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

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 filing

No regulator filing linked yet.

SEC 8-K / victim statement2 members

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 Jul 26, 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

11 days

vs. multi-state median

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