GLOBALMalwareManufacturingManufacturingRansomwareCl0pRansom DemandedActor NamedData Leak ThreatenedMedium

DANAHER CORPORATION

bd_2e27364d113a6525 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Dec 22, 2022

To disclose

—

Affected

Not disclosed

Linked

6 filings

Confidence

50%

Full breach record for DANAHER CORPORATION →

Threat-actor claim — not a regulatory filing

This row is a claim by the ransomware group Cl0p on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.

Group activity: ManufacturingDiscovered: 2022-12-22

View aggregator listing on ransomware.live View merged incident timeline

Source: Ransomware.live

J jump to incidentP pin to compareR raw source

Incident timeline — mostly unverified

? — ?

Breach window unknown

Dec 22, 2022

Claim posted

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

Claim → filing

—

Compliance clock

Not assessable

This filing is one of 6 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitestormousbd_3495efb65792b9f12022-04-25 · +241dVerified by operator

Regulatory filings (4) · sorted by filing gap

Indiana State AGbd_02d1306fe0ae286a2022-06-13 · +192dVerified by operator
Massachusetts State AGbd_37142d6b7e3cca672022-06-11 · +194dVerified by operator
Maine State AGbd_60b74d8c994ca6e72022-06-10 · +195dVerified by operator
California State AGbd_aa81bd74d37b02242022-06-10 · +195dVerified

Name: clop
norm: cl0p

Name: DANAHER CORPORATION
norm: danaher
Domain: danaher.com
Industry: Manufacturingaggregator

Attack vector: Ransomware· cl0p
Threat actor: Cl0pExternalFinancial

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.
Confidence context: Single unverified source — the attacker's own description. When a regulatory filing corroborates the claim, it appears in the linked-filings card.

Filing propagation · 5 filings · 4 states

View merged incident ↗

Maine State AGJun 10 · first

California State AGJun 10 · first

Massachusetts State AG+1d

Indiana State AG+3d

Leak Site+195d · this page

Pattern: first filing Jun 10 (ME), last Dec 22 — a 195-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claimThis record

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

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source ceiling

actor name
victim claim
ransom/leak status
discovery date
materiality
notification
affected count
confirmed data types
compliance clock

The ✕ fields stay blank until a regulatory filing or victim disclosure lands.

Source URL: https://www.ransomware.live/id/REFOQUhFUi5DT01AY2xvcA==
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Dec 22, 2022
Raw hash: b248117ba4566ebe0bd85bf91248a8f1ec2144079c22bccdd9662473917922c0

Linked disclosures

Ransomware claims (1)

Regulatory filings (4) · sorted by filing gap

Reporting entityclop

Victim entityDANAHER CORPORATION

What this source establishesRansomware

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.ransomware.live