CYBER SECURITY CLOUD.
DATA BREACH
Cyber Security Cloud (technology, Japan) was hit by a data breach first reported on 12 November 2026. No group has been publicly named as behind it in these reports. 6 news reports in the last 14 days, 0 in the last 24 hours; the latest, from Howl.Link: “Cybersecurity Cloud may have leaked customer information from GitHub; company says it takes the matter seriously as a security firm”. See every attack on the live map.
What happened in the Cyber Security Cloud data breach
Cyber Security Cloud, Inc. The company's first notice said a single employee's GitHub credential had been taken outside the company, as reported by Yahoo!ニュース and BigGo Finance.
The company said the GitHub area held company names, names and email addresses of some customers, plus communication-related information from service use. It said it could not rule out that third parties had viewed or taken this data.
Nobody has been named as the attacker. The company said its services had not been subject to unauthorised access, unauthorised operation or secondary damage, and that services continued to operate normally, according to its notice and TipRanks.
The company says it has invalidated the stolen credential, checked and changed other service credentials stored on GitHub, reviewed related access rights, isolated the relevant development terminals and suspended their accounts, and is investigating the cause, route and scope. BigGo Finance reported that it had also reported the matter to the Personal Information Protection Commission.
The number of people affected has not been disclosed and is still under investigation.
- What was taken: A single employee's GitHub credential was taken outside the company, according to the company's notice as reported by Yahoo!ニュース. The company says company names, names, email addresses and service-related communication information stored on GitHub may have been viewed or taken by a third party. Whether data was actually taken is still under investigation.
- Who is affected: The number of people or organisations affected has not been disclosed. The company says the information concerns some customers only, and the scope is under investigation.
- Who is behind it: Nobody has been named as the attacker.
- The response: Cyber Security Cloud says it has invalidated the leaked GitHub credential and checked and changed other service credentials stored on GitHub. It has also reviewed related credentials and access rights, isolated the relevant development terminals and suspended their accounts, and is reviewing GitHub and related access logs. BigGo Finance reported that the company is working with an external forensic firm and has reported the matter to the Personal Information Protection Commission. The company says it is working to prevent a recurrence.
Was my data taken in the Cyber Security Cloud data breach?
For this data breach: If you are a customer of Cyber Security Cloud, read the company's notice on its website (cscloud.co.jp) for updates on whether your data was involved. Be cautious with unexpected emails or messages that mention the company or its services, as the company has said leaked customer contact details may have been viewed.
Only Cyber Security Cloud can confirm whose data was involved. If you are a customer, these five steps cover you either way:
- Look for an email or letter from Cyber Security Cloud. Firms whose data is taken usually have to tell the people affected, and it says what was taken.
- If you have an account with Cyber Security Cloud, change its password, and the password anywhere else you used the same one.
- Turn on two-step sign-in where you can, so a stolen password is not enough on its own.
- Expect scam emails, texts and calls that mention Cyber Security Cloud or this breach. Do not click links in them; go to the real website yourself.
- Check whether your email address has turned up in known breaches at haveibeenpwned.com. In the UK, report money lost to fraud to Action Fraud.
Cyber Security Cloud data breach: the details
- Type: Data breach
- Sector: Technology
- Where: Tokyo, Japan
- Reports, last 14 days: 6
- Latest report: 23:17 UTC, 12 November 2026
See the numbers
| Day | Reports |
|---|---|
| 3 Nov | 0 |
| 4 Nov | 0 |
| 5 Nov | 0 |
| 6 Nov | 0 |
| 7 Nov | 0 |
| 8 Nov | 0 |
| 9 Nov | 0 |
| 10 Nov | 0 |
| 11 Nov | 0 |
| 12 Nov | 6 |
| 13 Nov | 0 |
| 14 Nov | 0 |
| 15 Nov | 0 |
| 16 Nov (so far) | 0 |
Latest Cyber Security Cloud news
- Cybersecurity Cloud may have leaked customer information from GitHub; company says it takes the matter seriously as a security firmHowl.Link · Data breach · Tokyo, Japan · 12 Nov 2026, 23:17 UTC
- Cyber Security Cloud may have leaked customer information via GitHub; company says it takes this seriously as a security firmITmedia · Data breach · Tokyo, Japan · 12 Nov 2026, 23:15 UTC
- Japan's Cyber Security Cloud reports unauthorized access to GitHub development platform; one employee credential leaked, raising customer data breach concernsBigGo Finance · Data breach · Tokyo, Japan · 12 Nov 2026, 09:35 UTC
- Cybersecurity firm's shares fall further after suspicious access raises possible personal data leakみんかぶ · Data breach · Japan · 12 Nov 2026, 04:26 UTC
- Cyber Security Cloud shares plunge in afternoon trade after possible information leak found in development environmentYahoo!ファイナンス · Data breach · Tokyo, Japan · 12 Nov 2026, 04:13 UTC
- Cybersecurity Cloud (4493) notice on possible information leak from its development environment, first report日本経済新聞 · Data breach · Tokyo, Japan · 12 Nov 2026, 04:00 UTC
Cyber Security Cloud data breach: timeline
- 2026-11-05: The company confirmed suspicious access to its GitHub area from GitHub access logs, which it says was likely made by a third party using a leaked employee credential.
- 2026-11-13: The company announced a revision to its FY2026 full-year earnings forecast that reflected the incident, according to TipRanks.
Sources for the story
Cyber Security Cloud data breach: common questions
What happened to Cyber Security Cloud?
Cyber Security Cloud (technology, Japan) was hit by a data breach first reported on 12 November 2026. No group has been publicly named as behind it in these reports.
What happened at Cyber Security Cloud?
It said a single employee's GitHub credential had been taken outside the company.
Has customer data definitely been stolen?
Not confirmed. The company says it cannot rule out that third parties viewed or took the information, and its investigation into the scope is ongoing.
Who is behind the attack?
Nobody has been named. The company describes the access as likely made by a third party using the leaked credential.
Are Cyber Security Cloud's services still running?
Yes. The company says it has found no unauthorised access to its services, no unauthorised operation and no secondary damage, and services continue to operate normally.
How many customers are affected?
The company has not disclosed the number of people or organisations affected, and the scope is still under investigation.
Who is behind the Cyber Security Cloud data breach?
No group has been publicly named in the reports collected here. Attribution can take weeks and is often disputed.
Was my data affected?
Only Cyber Security Cloud can say whose data was involved; its own statement is usually linked from the latest reports below. If you are a customer, watch for emails or texts that mention the breach, change your password there and anywhere you reuse it, and turn on two-step sign-in.