Capcom concludes ransomware investigation, details what happened

Publish date: 2022-07-31

Back in November last year, Capcom was hit by a severe cyber attack that saw personal information, internal briefings and game details compromised and held to ransom. Following a few updates in November and January, Capcom has now issued a lengthy explanation of exactly what happened - and the steps it's taking to prevent it happening again.

In an update post summarising the results of its (now-completed) investigation carried out with the help of specialist companies, Capcom said its internal systems are now "near to completely restored". The attack had encrypted data on Capcom devices, and installed a message demanding Capcom contact the hacking group responsible.

As for how the attack happened, Capcom explained that unauthorised access to the company's internal network was acquired in October 2020 through an old backup VPN at Capcom USA. It seems Covid-19 had a hand in creating conditions for the attack to be successful, as although Capcom had already started switching to newer VPN devices, the growing strain on the company's network due to working from home meant the older VPN was kept as "an emergency backup in case of communication issues". This VPN became the target of the cyber attack, and through this the attackers were able to compromise devices at Capcom's US and Japanese offices, leading to the theft of information.

Resident Evil Village Gameplay Reaction - Resident Evil Village Theory Breakdown

Although some perimeter measures were already in place, Capcom had been in the process of adopting additional defensive measures (a SOC server and EDR), but "had been forced to prioritise infrastructure improvements necessitated by the spread of Covid-19". This meant the security measures had not yet been implemented by the time of the attack.

The external specialist companies concluded the incident was a "malicious, multi-faceted attack that would be difficult to defend against", Capcom said.

Having established a new Technology Security Oversight Committee, Capcom plans to continue strengthening its security. Along with implementing that SOC service and EDR, it's already cleaned all compromised devices and improved management methods for VPNs. It's also made efforts to raise employee awareness of security, and strengthened internal systems with regular verification methods.

The cumulative total for information verified to be compromised now stands at 15,649 people, down 766 from the previously-thought total. Capcom reaffirmed that credit card details and customer details have not been impacted. We don't yet know what sort of damage that compromised personal and corporate data has caused, however, as Capcom is currently unable to confirm this.

Capcom also reiterated that it did not make contact with the threat actor, under advice from law enforcement, and "is not aware of any ransom demand amounts".

"Capcom would once again like to reiterate its deepest apologies for any complications or concerns caused by the incident," the post concluded.

The update is largely focused on personal data, and there's little mention of the large amount of internal corporate information that was splashed across the internet following the attack. Stolen information from the ransomware attack included previously-unannounced ports, release dates and in-progress projects. There's a Resident Evil showcase scheduled for later this week, so some of these may get a proper announcement on Thursday. In the meantime, don't trust any early access invitations for Resident Evil Village, as Capcom has warned these are part of a phishing scam.

Will you support Eurogamer?

We want to make Eurogamer better, and that means better for our readers - not for algorithms. You can help! Become a supporter of Eurogamer and you can view the site completely ad-free, as well as gaining exclusive access to articles, podcasts and conversations that will bring you closer to the team, the stories, and the games we all love. Subscriptions start at £3.99 / $4.99 per month.

Support us View supporter archive

ncG1vNJzZmivp6x7psHRqJ6apZWne6%2Bx02iYq6yZmLmmv45rZ2tpXWWBbn2SZpqaqJOkum6vzqeapa2UmsBuvsCnqqilp5a%2FpnnIp62eq6SetKLAyKilZpyVqa6quNJmrqGZpGK1orzPnqWenA%3D%3D