FEDERALItem 8.01 · voluntaryHackingManufacturingManufacturingDelayed DiscoveryLowActive

TEMPUR SEALY INTERNATIONAL, INC.

bd_c04cead0fe469013 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jul 23, 2023

Filed

Jul 31, 2023

To disclose

8 days

Affected

Not disclosed

Linked

4 records

Confidence

67%

Tempur Sealy International, Inc. disclosed a cybersecurity event on July 23, 2023, involving its IT systems. The company activated incident response plans, shut down systems, and engaged forensic investigators and law enforcement. The investigation was ongoing as of the filing date, with materiality and data impact undetermined.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 8 days

Jul 23, 2023

Discovered

Jul 31, 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 · +2dVerified by operator

Regulatory filings (2) · sorted by filing gap

SEC 8-Kbd_b7c4fe35ced66f2d2023-08-03 · +3dVerified by operator
SEC 8-Kbd_5540de9ae9bf6a1a2023-11-02 · +94dCandidate

Name: TEMPUR SEALY INTERNATIONAL, INC.
norm: tempur sealy international
SEC CIK: 0001206264

Name: TEMPUR SEALY INTERNATIONAL, INC.
norm: tempur sealy international
SEC CIK: 0001206264
Industry: Manufacturingnaics map

Discovered: Jul 23, 2023
Materiality determined: Jul 23, 2023
Notification sent: —
Affected individuals: Not disclosed
Data types: —
Attack vector: Unknown
MITRE ATT&CK: T1078 Valid Accounts
Regulator citations: Notified law enforcement authorities

During the incident: Activated its incident response and business continuity plans
Proactively shutting down certain of the Company's IT systems
Engaged legal counsel, a cybersecurity forensic firm and other incident response professionals
Notified law enforcement authorities
Changes made: Bringing certain of its critical IT systems back online
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 8 days(8 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 · this page

SEC 8-K+3d

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/000120626423000158/
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Jul 31, 2023
Raw hash: ed82033fea3273b29e89f96b391f34a65420a6488005d0f02796ef38e09e06e0

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/html28.8 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 responseActivated its incident response and business continuity plans

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing