CD Projekt Red announced today that they are delaying the anticipated Cyberpunk 2077 Patch 1.2 to the second half of March 2021 due to their recent cyberattack.
Patch 1.2 is expected to be a major release containing many bug fixes and performance improvements for known issues that players are experiencing.
Today, CDPR announced that due to the recent cyberattack on their systems coupled with the massive scope of the update, they are forced to delay Patch 1.2 to the end of March 2021.
"While we dearly wanted to deliver Patch 1.2 for Cyberpunk 2077 in the timespan we detailed previously, the recent cyber attack on the studio’s IT infrastructure and extensive scope of the update mean this unfortunately will not happen — we’ll need some additional time."
"Our goal for Patch 1.2 goes beyond any of our previous updates. We’ve been working on numerous overall quality improvements and fixes, and we still have work to do to make sure that’s what you get. With that in mind, we’re now aiming for release in the second half of March.."
"It’s not the news we enjoy sharing, but we want to make sure we launch this update properly. Stay tuned for more information as the time draws closer. Thank you for your continued patience and support," CD Projekt explained in a series of tweets.
This month, CD Projekt Red suffered a cyberattack by the HelloKitty ransomware operation that encrypted servers on their network.
In a ransom note created during the attack, the attackers stated that they stole the source code for Cyberpunk 2077, Witcher 3, Gwent, and an unreleased version of Witcher 3 with ray tracing support.
The hackers also claimed to have stolen internal documents related to the employees, administration, accounting, and investor relations.
After the attack wen't public and CDPR announced that they would not pay the ransom, the threat actors began to auction the stolen data on a hacker forum.
The next day, the attackers claimed to have sold the data to a person "outside the forum."
At this time, there is no proof that the threat actors actually sold the data or who may have purchased it.
Break down IAM silos like Bitpanda, KnowBe4, and PathAI
Broken IAM isn't just an IT problem - the impact ripples across your whole business.
This practical guide covers why traditional IAM practices fail to keep up with modern demands, examples of what "good" IAM looks like, and a simple checklist for building a scalable strategy.
Comments
yawnshard - 4 years ago
Rolling back your backups doesn't delay something by an additional month.
But whatever, maybe the extra time makes the patch better than the last, which required additional hotfixes.
billwendel - 4 years ago
It does if you have to look thru the code for possible added malware or commands that could be spread to your customers computers via the update.
You double-check and triple-check and then release.
Devil's advocate tho: They may have wanted to finalize to clear out further bugs and make more bugfixes.