FEDERALUnknownManufacturingManufacturingDelayed DiscoveryLowActive

Tempur Sealy International, Inc.

bd_b7c4fe35ced66f2d · schema v1 · pii pii-v1

Severity

Low

Discovered

Jul 23, 2023

Filed

Aug 3, 2023

To disclose

11 days

Affected

Not disclosed

Linked

4 records

Confidence

60%

Tempur Sealy International, Inc. disclosed a cybersecurity event identified on July 23, 2023, affecting certain IT systems. The company resumed operations but the forensic investigation is ongoing. No specific data types or affected individual counts were disclosed in this press release.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 11 days

Jul 23, 2023

Discovered

Aug 3, 2023

Filed

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

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitealphvbd_51d01d568048635b2023-08-02 · +1dVerified by operator

Regulatory filings (2) · sorted by filing gap

SEC 8-Kbd_c04cead0fe4690132023-07-31 · +3dVerified by operator
SEC 8-Kbd_5540de9ae9bf6a1a2023-11-02 · +91dCandidate

Name: Tempur Sealy International, Inc.
norm: tempur sealy international

Name: Tempur Sealy International, Inc.
norm: tempur sealy international
Industry: Manufacturingnaics map

Discovered: Jul 23, 2023
Materiality determined: —
Notification sent: —
Affected individuals: Not disclosed
Data types: —
Attack vector: Unknown

During the incident: Began the process to bring certain of its critical IT systems back online and has resumed operations
Forensic investigation remains ongoing
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 11 days(11 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 3 filings

View merged incident ↗

SEC 8-KJul 31 · first

SEC 8-K+3d · this page

SEC 8-K+94d

Pattern: first filing Jul 31, last Nov 2 — a 94-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

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 statementThis record

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

Source URL: https://www.sec.gov/Archives/edgar/data/1206264/000120626423000164/
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Aug 3, 2023
Raw hash: 6df28d0dcd57bf45e2e0ec974873e15dad8403d61c12359e90b11e69e8503200

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html366.9 KB

Download View at source

Linked disclosures

Ransomware claims (1)

Regulatory filings (2) · sorted by filing gap

Reporting entityTempur Sealy International, Inc.

Victim entityTempur Sealy International, Inc.

Incidentdiscovered Jul 23, 2023

Stated responseBegan the process to bring certain of its critical IT systems back online and has resumed operations

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing