Capcom disclosed that unauthorized third-party access disrupted parts of its corporate network, affecting internal email and file servers and forcing the company to suspend some network operations to contain the incident. The company said online gameplay services and public websites were not impacted, but investor-relations responses and document requests were delayed while systems were restored and the matter was reported to law enforcement.
Reporting tied the intrusion to Ragnar Locker ransomware after a related sample and ransom note surfaced, with the gang claiming it encrypted about 2,000 devices and stole more than 1 TB of unencrypted data from Capcom systems in Japan, the United States, and Canada. The attackers allegedly demanded $11 million in bitcoin in exchange for a decryptor, deletion of stolen files, and a network penetration report, while leaked samples were said to include financial records, employee documents, contracts, and internal communications.

TTPs, infrastructure, and targeting history in one profile.
6 events from the most recent confirmed update back to the earliest known activity.
According to the new reference, the Ragnar Locker group published a public claim of responsibility for the Capcom intrusion on its leak infrastructure. The post was separate from the earlier ransom note details already reported and marked a public extortion step by the attackers.
Ragnar Locker's ransom note claimed the attackers stole more than 1 TB of unencrypted sensitive data from Capcom systems in Japan, the United States, and Canada and encrypted 2,000 devices. The gang allegedly demanded $11 million in bitcoin for a decryptor, deletion of stolen data, and a network penetration report.
Reporting on November 5 said evidence from a ransomware sample and ransom note indicated the Ragnar Locker gang was responsible for the attack. An update also said the incident may have been caused by Ragnar Locker ransomware.
Capcom disclosed the incident on November 5, stating that unauthorized access had impacted certain internal systems including email and file servers. The company said there was no indication at that stage that customer information had been compromised.
Beginning in the early morning of November 2, 2020, Capcom said unauthorized third-party access caused issues on parts of the Capcom Group network, affecting email and file servers. The company halted some internal network operations to contain the incident and said online gameplay services and public websites were not affected.
After detecting the intrusion, Capcom reported the cyberattack to law enforcement while working to restore impacted systems. The disclosure also noted disruption to investor-relations responses and document requests during recovery.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
See this adversary's TTPs, infrastructure, and targeting history, correlated against your exposure.
4 references tracked. Mallory keeps watching after this page renders.
coveware.com
Open sourcembsd.jp
Open sourcezdnet.com
Open sourcebleepingcomputer.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.