Potential information leakage in our development environment
Cyber Security Cloud,Inc. (filing company)
The Company-managed area on GitHub used for software development (development environment)
One set of GitHub credentials used by a Company employee for work was leaked externally, and suspicious access by a third party using those credentials occurred. The cause and route of the credential leak are under investigation.
Company response
None. No impact on the provision of the Company's services or their security functions has been identified, and all services continue to be provided as usual.
A forensic investigation by the Company's security engineers and external specialist organisations
Invalidation of the leaked GitHub credentials / Review and change of the various credentials for other services stored on GitHub / Review and change of relevant credentials and access permissions / Isolation of the relevant development devices and suspension of account use / Investigation of access logs and other records for GitHub and related systems / Identification of personal information and customer information that may have been leaked and investigation of the scope of the impact / Review of the credential management framework and security measures to prevent recurrence
Related procedures
Reporting to the Personal Information Protection Commission and other relevant authorities. The Company is consulting with the affected customers that commissioned the services on the reporting method.
Personal Information Protection Commission and other relevant authorities
The impact of this matter on the Company's business performance is currently under review. The Company will promptly announce any matters requiring disclosure that arise in the future.
The Company will take necessary measures based on the investigation results. Customers confirmed to be affected will be notified in due course, and for personal information entrusted to the Company, the Company will coordinate with the customers that commissioned the services to proceed with notifying the individuals concerned and taking other steps. The Company will continue to work with the relevant authorities and review its credential management framework and security measures.
The Company will promptly report any new matters requiring notification that are identified through the ongoing investigation. Details of the reporting method to be used by the customers that commissioned the services will be provided once finalised.
| Item | Details |
|---|---|
| Event name | Potential information leakage in our development environment |
| Date recognized / date notice received | 5 November 2026 (Suspicious access was confirmed through an investigation of GitHub access logs) |
| Subject Entity | Cyber Security Cloud,Inc. (filing company) |
| Target Locations / Products | The Company-managed area on GitHub used for software development (development environment) |
| Cause | One set of GitHub credentials used by a Company employee for work was leaked externally, and suspicious access by a third party using those credentials occurred. The cause and route of the credential leak are under investigation. |
| Impact on Earnings Forecast | The impact of this matter on the Company's business performance is currently under review. The Company will promptly announce any matters requiring disclosure that arise in the future. |
| Type of litigation or proceeding | Reporting to the Personal Information Protection Commission and other relevant authorities. The Company is consulting with the affected customers that commissioned the services on the reporting method. |
| Court or authority | Personal Information Protection Commission and other relevant authorities |
| Suspended operations | None. No impact on the provision of the Company's services or their security functions has been identified, and all services continue to be provided as usual. |
| Investigation structure | A forensic investigation by the Company's security engineers and external specialist organisations |
| Measures to prevent recurrence | Invalidation of the leaked GitHub credentials / Review and change of the various credentials for other services stored on GitHub / Review and change of relevant credentials and access permissions / Isolation of the relevant development devices and suspension of account use / Investigation of access logs and other records for GitHub and related systems / Identification of personal information and customer information that may have been leaked and investigation of the scope of the impact / Review of the credential management framework and security measures to prevent recurrence |
| Outlook | The Company will take necessary measures based on the investigation results. Customers confirmed to be affected will be notified in due course, and for personal information entrusted to the Company, the Company will coordinate with the customers that commissioned the services to proceed with notifying the individuals concerned and taking other steps. The Company will continue to work with the relevant authorities and review its credential management framework and security measures. |
| Planned follow-up disclosure | The Company will promptly report any new matters requiring notification that are identified through the ongoing investigation. Details of the reporting method to be used by the customers that commissioned the services will be provided once finalised. |
Items this document does not state (12)
These are items the company does not state in this document. We do not leave them blank, nor fill them in from other sources or by inference.
The reasons the company gives
The company's own explanation, not something inferred from the numbers.One set of GitHub credentials used by a Company employee for work was leaked externally, and suspicious access by a third party using those credentials was detected. However, the cause and route of the credential leak and the scope of its impact are under investigation.