What is known so far
- An outside organization alerted Cyber Security Cloud that a GitHub credential one employee used for work had leaked. [1, 3]
- On November 5, Cyber Security Cloud found earlier suspicious access in its GitHub logs. It believed a third party had used the leaked credential. [1]
- The available logs covered only part of the time the credential was valid and provided limited detail about the access. [1]
- On November 12, the company said someone might have viewed or obtained customer contact details and information about service communications stored in the repository. [1]
- Cyber Security Cloud disabled the leaked credential, changed credentials for other services stored on GitHub and isolated the affected development devices. [1]
- In its November 13 investor presentation, Cyber Security Cloud said it detected suspicious access to a “CSC-managed area on GitHub” used for software development and that information may have been leaked. [2]
- In the same presentation, Cyber Security Cloud said it had found no unauthorized access to its services, which continued operating. [2]
- The company said the full-year earnings forecast revision it announced on November 13 reflects the impact of the incident, and that it would promptly disclose any material impact on current-year results. [2]
What is not published yet
- How the employee’s credential leaked and what type it was.
- The first and last unauthorized access.
- Which GitHub operations the third party performed.
- Whether anyone obtained customer information, and whose information was affected.
Sources
The numbers beside each reported fact refer to the sources below.
- 1.Notice and Apology Regarding Potential Information Leakage in Our Development Environment (First Report)Cyber Security Cloud, Inc. · Nov 12, 2026 · Vendor reportThe leaked credential, the limits of the GitHub logs, the information at risk and the company’s response
- 2.Possible Information Leak in Our Development Environment (FY2026 3Q Financial Materials, page 2)Cyber Security Cloud, Inc. · Nov 13, 2026 · Vendor reportThe company’s confirmation of suspicious GitHub access and service status
- 3.Cyber Security Cloud (CSC): Potential Customer Data Leak from GitHub Development Environment (First Report, November 12)SmartScope · Nov 15, 2026 · NewsReported credential leak, access-log limits, data categories and containment
This notice is written from public reporting while the incident is still being disclosed. It names no control and gives no verdict, because the sources do not yet say what was used against what. It is not an assessment of the victim's security program.