Incident Types: The types of cybersecurity incidents that have occurred include Ransomware and Breach.

Total Financial Loss: The total financial loss from these incidents is estimated to be $300 thousand.

Detection and Response: The company detects and responds to cybersecurity incidents through an incident response plan activated with null, and third party assistance with null, and law enforcement notified with null, and containment measures with null, and remediation measures with null, and recovery measures with null, and communication strategy with null, and adaptive behavioral waf with null, and on demand scrubbing services with null, and network segmentation with null, and enhanced monitoring with null..

Common Attack Types: The most common types of attacks the company has faced is Breach.

Identification of Attack Vectors: The company identifies the attack vectors used in incidents through Internal Jira development and ticketing server.

Average Financial Loss: The average financial loss per incident is $100.00 thousand.

Commonly Compromised Data Types: The types of data most commonly compromised in incidents are Internal communications, purchase orders, logs, customer records, and employee data, Personal data, Full Name, Id Number, Address and .

Incident Response Plan: The company's incident response plan is described as null.

Third-Party Assistance: The company involves third-party assistance in incident response through null.

Prevention of Data Exfiltration: The company takes the following measures to prevent data exfiltration: null.

Handling of PII Incidents: The company handles incidents involving personally identifiable information (PII) through by null.

Data Recovery from Ransomware: The company recovers data encrypted by ransomware through null.

Ensuring Regulatory Compliance: The company ensures compliance with regulatory requirements through null, Decision can be appealed within one month.

Key Lessons Learned: The key lessons learned from past incidents are null.

Implemented Recommendations: The company has implemented the following recommendations to improve cybersecurity: null.

Additional Resources: Stakeholders can find additional resources on cybersecurity best practices at and Source: BleepingComputerUrl: nullDate Accessed: null, and Source: MLexDate Accessed: 2025-12-22, and Source: HackManac.

Communication of Investigation Status: The company communicates the status of incident investigations to stakeholders through null.

Advisories Provided: The company provides the following advisories to stakeholders and customers following an incident: were null and null.

Post-Incident Analysis Process: The company's process for conducting post-incident analysis is described as null, null.

Corrective Actions Taken: The company has taken the following corrective actions based on post-incident analysis: null.

Ransom Payment History: The company has Paid ransoms in the past.

Last Ransom Demanded: The amount of the last ransom demanded was null.

Last Attacking Group: The attacking group in the last incident were an Hellcat ransomware operation, alias Rey and Dedale.

Most Recent Incident Detected: The most recent incident detected was on null.

Most Recent Incident Publicly Disclosed: The most recent incident publicly disclosed was on 2025-12-22.

Most Recent Incident Resolved: The most recent incident resolved was on null.

Most Significant Data Compromised: The most significant data compromised in an incident were 106GB of sensitive files, including internal communications, purchase orders, logs, customer records, and employee data, Personal data processed unlawfully during mobile phone line changes, 22 million customer records accessed and 1 million records leaked.

Third-Party Assistance in Most Recent Incident: The third-party assistance involved in the most recent incident was null.

Containment Measures in Most Recent Incident: The containment measures taken in the most recent incident was null.

Most Sensitive Data Compromised: The most sensitive data compromised in a breach were Personal data processed unlawfully during mobile phone line changes, 22 million customer records accessed, 1 million records leaked, 106GB of sensitive files, including internal communications, purchase orders, logs, customer records and and employee data.

Number of Records Exposed in Most Significant Breach: The number of records exposed in the most significant breach was 23.4M.

Highest Ransom Paid: The highest ransom paid in a ransomware incident was null.

Highest Fine Imposed: The highest fine imposed for a regulatory violation was null, €300,000.

Most Significant Legal Action: The most significant legal action taken for a regulatory violation was null, Decision can be appealed within one month.

Most Significant Lesson Learned: The most significant lesson learned from past incidents was null.

Most Significant Recommendation Implemented: The most significant recommendation implemented to improve cybersecurity was null.

Most Recent Source: The most recent source of information about an incident are MLex, BleepingComputer and HackManac.

Most Recent URL for Additional Resources: The most recent URL for additional resources on cybersecurity best practices is null .

Current Status of Most Recent Investigation: The current status of the most recent investigation is null.

Most Recent Stakeholder Advisory: The most recent stakeholder advisory issued was null, .

Most Recent Customer Advisory: The most recent customer advisory issued was an null.

Most Recent Entry Point: The most recent entry point used by an initial access broker was an Internal Jira development and ticketing server.

Most Recent Reconnaissance Period: The most recent reconnaissance period for an incident was null.

Most Significant Root Cause: The most significant root cause identified in post-incident analysis was null, Unlawful processing of personal data during mobile phone line changes.

Most Significant Corrective Action: The most significant corrective action taken based on post-incident analysis was null.