{"id":843,"date":"2016-07-12T16:30:00","date_gmt":"2016-07-12T16:30:00","guid":{"rendered":"https:\/\/fraud.flywheelsites.com\/wendys_breach\/"},"modified":"2020-11-09T07:31:49","modified_gmt":"2020-11-09T07:31:49","slug":"wendys_breach","status":"publish","type":"post","link":"https:\/\/fraud.org\/wendys_breach\/","title":{"rendered":"Wendy’s breach – Fraud.org"},"content":{"rendered":"

\"wendys-crop.jpg\"<\/p>\n

Wendy’s, the Ohio-based fast-food chain, announced a point-of-sale terminal breach in late January 2016. In July 2016, the company announced that the breach was significantly larger than previously disclosed.<\/p>\n

<\/p>\n

Announced:<\/strong>\u00a0January 2016 (updated July 2016)<\/p>\n

Description of breach:<\/strong> From December 2015 – June 2016, at least 1,025 Wendy\u2019s restaurants had their point-of-sale systems affected by a data breach. Wendy\u2019s has reported that customers who paid with their credit or debit card at an affected location may have had their their cardholder name, credit or debit card number, expiration date, cardholder verification value (CVV), and service codes of a customer’s payment compromised.<\/p>\n

Consumers who visited a Wendy\u2019s location during this breach period, are encouraged to determine if they were affected by the breach by searching the list of affected restaurants found here<\/a>.<\/p>\n

Consumers who purchased any items from a compromised Wendy\u2019s during the breach time period, are being urged to closely monitor their credit, and take advantage of their offer to pay for one year of free credit monitoring services by calling them at (866) 779-0485.<\/p>\n

Data breach period:\u00a0<\/strong>December 2015 – June 2016<\/p>\n

Affected customers:<\/strong>\u00a0Unknown. 1,025 locations were affected.<\/p>\n

Official information from Wendy’s:<\/strong>\u00a0An FAQ is available here<\/a>.<\/p>\n

Contact Wendy’s:<\/strong>\u00a0Customers may call a toll-free number (888-846-9467) or email\u00a0PaymentCardUpdate@wendys.com<\/a>\u00a0with specific questions.<\/p>\n

More coverage of this breach:\u00a0<\/strong>KrebsOnSecurity<\/a>,\u00a0<\/strong>July update from KrebsOnSecurity<\/strong><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

NULL<\/p>\n","protected":false},"author":2,"featured_media":0,"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\/843"}],"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=843"}],"version-history":[{"count":1,"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/posts\/843\/revisions"}],"predecessor-version":[{"id":1461,"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/posts\/843\/revisions\/1461"}],"wp:attachment":[{"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/media?parent=843"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/categories?post=843"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fraud.org\/wp-json\/wp\/v2\/tags?post=843"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}