{"id":825,"date":"2018-03-23T21:19:30","date_gmt":"2018-03-23T21:19:30","guid":{"rendered":"https:\/\/fraud.flywheelsites.com\/orbitz_breach\/"},"modified":"2020-11-09T07:30:43","modified_gmt":"2020-11-09T07:30:43","slug":"orbitz_breach","status":"publish","type":"post","link":"https:\/\/fraud.org\/orbitz_breach\/","title":{"rendered":"Orbitz breach – Fraud.org"},"content":{"rendered":"

\"\"<\/p>\n

The travel booking website Orbitz announced that 880,000 payment cards were hacked in a breach that spanned almost two years. <\/span><\/p>\n

<\/p>\n

Announced:<\/strong> March 20, 2018<\/span><\/p>\n

Description of the breach:<\/strong> On March 20, 2018, the online travel booking site Orbitz warned customers that 880,000 credit and debit cards used on its website had been compromised. <\/span>In addition to the payment card information, the names, birth dates, phone numbers, and email and billing addresses of their customers are also believed to be compromised. Travel itinerary details, as well as passport and Social Security numbers, are not believed to have been subject to the breach.<\/span><\/p>\n

Customers who shopped at Orbitz between January 2016 and December 2017 should closely monitor their credit and debit card statements. It is important to report any unauthorized or suspicious charges to your financial institution immediately. In the coming days, Orbitz says it will notify those who were affected by the breach and will offer the, free credit monitoring services for one year. Customers that are unsure if they are victims, or if they are interested in the free credit monitoring offer, should contact Orbitz\u2019 data breach assistance line.<\/span><\/p>\n

Data breach period:<\/strong> Jan. 1, 2016 and Dec. 22, 2017<\/span><\/p>\n

Orbit\u2019s data breach assistance line phone number:<\/strong> (855) 828-3959<\/span><\/p>\n

More coverage of this breach: <\/strong>Wall Street Journal<\/span><\/a> and <\/span>Reuters<\/span><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

NULL<\/p>\n","protected":false},"author":2,"featured_media":607,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"categories":[122],"tags":[],"_links":{"self":[{"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/posts\/825"}],"collection":[{"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/comments?post=825"}],"version-history":[{"count":2,"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/posts\/825\/revisions"}],"predecessor-version":[{"id":2252,"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/posts\/825\/revisions\/2252"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/media\/607"}],"wp:attachment":[{"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/media?parent=825"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/categories?post=825"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/tags?post=825"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}