UnknownHigh

Orbitz Worldwide, LLC

bd_167ffa75ae444821 · schema v1 · pii pii-v1

Severity

High

Discovered

Mar 1, 2018

Filed

Mar 21, 2018

To disclose

20 days

Affected

328,612

Linked

10 filings

Confidence

95%

Full breach record for Orbitz Worldwide, LLC →4 incidents on file

Orbitz reported a data breach to the Oregon Attorney General. The breach was reported on 2018-03-21. The breach occurred during 10/1/2017 - 12/22/2017. The breach was discovered on 3/1/2018. 328,612 individuals were affected. Notice was sent on 3/22/20183/23/2018.

J jump to incidentP pin to compareR raw source

Oregon clock✓ OR AG ≤45d20 days discovery → filing

⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 151 days

discovery → filing · 20 days

Oct 1, 2017

Begins

Mar 1, 2018

Discovered

Mar 21, 2018

Filed

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

Linked disclosures

Why this link?

Regulatory filings (9) · sorted by filing gap

Massachusetts State AGbd_15c161a571fbde6f2018-03-21Verified
California State AGbd_b9294a8e6ae14d2c2018-03-21Candidate
Washington State AGbd_2883e555dee90b7f2018-03-20 · +1dCandidate
New Hampshire State AGbd_d6326efbc0efb26d2018-03-20 · +1dVerified

Show 5 more filings ↓up to 63d gap

New Hampshire State AGbd_427c39753007cdda2018-03-26 · +5dVerified
South Carolina State AGbd_1f812697f46781f02018-03-28 · +7dVerified
Hawaii State AGbd_f5b7e344d02ff77d2018-04-04 · +14dVerified
Montana State AGbd_6754a3719ce3b5af2018-05-04 · +44dVerified
New Hampshire State AGbd_fd5fd3bbfed87fd12018-05-23 · +63dVerified

Name: Orbitz Worldwide, LLC
norm: orbitz worldwide

Name: Orbitz Worldwide, LLC
norm: orbitz worldwide

Discovered: Mar 1, 2018
Breach occurred: Oct 1, 2017 – Dec 22, 2017
Undetected for: 151 daysoccurrence → discovery
Materiality determined: —
Notification sent: —
Affected individuals: 328,612nationwide
Data types: —
Attack vector: Unknown

Time to disclose: 20 days(20 days from discovery to filing)
Compliance flags: OR AG ≤45d
Discovery-date grounding: AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 10 filings · 8 states

View merged incident ↗

Washington State AGMar 20 · first

New Hampshire State AGMar 20 · first

Massachusetts State AG+1d

California State AG+1d

Oregon State AG+1d · this page

New Hampshire State AG+6d

South Carolina State AG+8d

Hawaii State AG+15d

Montana State AG+45d

New Hampshire State AG+64d

Pattern: first filing Mar 20 (WA), last May 23 (NH) — a 64-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 filingThis record

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

SEC 8-K / victim statement

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

Source URL: https://justice.oregon.gov/consumer/DataBreach/
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 21, 2018
Raw hash: 67940bbdcf3b44faedf4ce78ef973508318e199c2e466df3eb876916b0bcc380

Linked disclosures

Regulatory filings (9) · sorted by filing gap

Reporting entityOrbitz Worldwide, LLC

Victim entityOrbitz Worldwide, LLC

Incidentdiscovered Mar 1, 2018

ComplianceOR AG ≤45d

Extraction provenanceno artifact recorded

Source provenancejustice.oregon.gov