Regardless of preliminary studies on the contrary, plainly hackers did handle to steal delicate buyer data from Yum! Manufacturers throughout a current ransomware assault.
The mother or father firm of KFC, Pizza Hut, and Taco Bell chains began sending out notifications to affected clients explaining what sort of data was stolen in the course of the assault that occurred in mid-January this 12 months.
The notifications learn: “Our evaluate decided that the uncovered recordsdata contained a few of your private data, together with [Name or other personal identifier in combination with: Driver’s License Number or Non-Driver Identification Card Number].” That is loads of data for risk actors to commit acts of id theft.
No proof of abuse
Within the preliminary report, the corporate stated there was no proof of buyer information having been taken. However now that this has been confirmed, Yum! manufacturers has amended its declare to say there is not any proof that the stolen information is being actively exploited within the wild.
The ransomware assault that occurred on January 18 this 12 months compelled the corporate to close down as much as 300 eating places in a single marketplace for a day, in accordance with Yum! Manufacturers’ submitting with the U.S. Securities and Alternate Fee (SEC). The shutdown “briefly disrupted” a few of its affected techniques and resulted in information theft, it additionally acknowledged.
“We have now incurred, and will proceed to incur, sure bills associated to this assault, together with bills to reply to, remediate and examine this matter.”
“Whereas this incident triggered momentary disruption, the corporate is conscious of no different restaurant disruptions and doesn’t count on this occasion to have a fabric opposed impression on its enterprise, operations or monetary outcomes,” it stated.
Whereas the corporate stated it notified affected clients and supplied id theft monitoring options in compensation, it didn’t say precisely how many individuals had been affected by the incident.
By way of: BleepingComputer (opens in new tab)
