MERKLE INC
bd_9962c200c3462649 · schema v1 · pii pii-v1
Full breach record for MERKLE INC →Press / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage — verify against the source.
Merkle data hit as Dentsu is rocked by 'security incident' - DecisionMarketing. Merkle: Dentsu suffered a cyberattack, resulting in the leak of sensitive data from its Merkle network, including information about current and former clients, suppliers, and employees. The company has engaged specialized cybersecurity incident response firms and notified authorities. Dentsu's systems are now back online, and the company is offering identity monitoring services to affected employees.
P pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 28, 2025
Press report
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
If an SEC 8-K, state-AG notice or victim statement lands, DisclosureLens merges it into an incident and links it here.
Source ceiling
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.