Report on the Results of the Investigation into the Ransomware Incident and Measures to Prevent Recurrence (Final Report)
Ficha Inc. (the filing company)
A total of 32 of the Company's servers and other devices, GitHub servers, 144 GitHub repositories, and files consolidated on one of the Company's servers
The specific cause and method of the unauthorized access could not be identified. The encryption of relevant logs by the ransomware and other factors constrained the investigation.
Company response
The investigation was conducted with the support of external specialists. The name of the committee chair and the date of establishment are Not disclosed.
Renewal of the external connectivity infrastructure, implementation of multi-factor authentication, and monitoring for suspicious logins, Prevention of internal spread through network segregation and other measures, Strengthening of account management, including separation of administrator privileges and ongoing reviews, Implementation of endpoint security measures, including EDR (Endpoint Detection and Response), Strengthening of the monitoring framework, including an external SOC (Security Operation Center)
At present, there is no revision to the earnings forecasts as a result of this incident.
The Company will work to ensure the effectiveness of its measures to prevent recurrence and make continuous improvements. It will continue to verify the facts and monitor the scope of the impact, and will make timely disclosure if any matters requiring notification become known.
If any matters requiring further disclosure arise, they will be promptly announced.
| Item | Details |
|---|---|
| Event name | Report on the Results of the Investigation into the Ransomware Incident and Measures to Prevent Recurrence (Final Report) |
| Date of occurrence | 9 July 2025 (the date on which the first trace related to this incident was identified) |
| Subject Entity | Ficha Inc. (the filing company) |
| Target Locations / Products | A total of 32 of the Company's servers and other devices, GitHub servers, 144 GitHub repositories, and files consolidated on one of the Company's servers |
| Cause | The specific cause and method of the unauthorized access could not be identified. The encryption of relevant logs by the ransomware and other factors constrained the investigation. |
| Impact on Earnings Forecast | At present, there is no revision to the earnings forecasts as a result of this incident. |
| Investigation structure | The investigation was conducted with the support of external specialists. The name of the committee chair and the date of establishment are Not disclosed. |
| Measures to prevent recurrence | Renewal of the external connectivity infrastructure, implementation of multi-factor authentication, and monitoring for suspicious logins, Prevention of internal spread through network segregation and other measures, Strengthening of account management, including separation of administrator privileges and ongoing reviews, Implementation of endpoint security measures, including EDR (Endpoint Detection and Response), Strengthening of the monitoring framework, including an external SOC (Security Operation Center) |
| Outlook | The Company will work to ensure the effectiveness of its measures to prevent recurrence and make continuous improvements. It will continue to verify the facts and monitor the scope of the impact, and will make timely disclosure if any matters requiring notification become known. |
| Planned follow-up disclosure | If any matters requiring further disclosure arise, they will be promptly announced. |
Items this document does not state (15)
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.The specific cause and method of the unauthorized access could not be identified due to investigative constraints, including the encryption of relevant logs.