Zabicall
| Primary URL | Location | Industry | Undetermined |
Country
South Korea
|
Transportation
|
|---|
Profile
Zabicall operates as a call taxi service provider that facilitates passenger transportation through a smartphone‑based dispatch application. The company connects riders with drivers across several South Korean provinces, enabling users to request, track, and pay for rides via its mobile platform. Its service model relies on a centralized dispatch system that coordinates vehicle availability and routes in real time, aiming to provide reliable urban and inter‑city mobility options. Zabicall’s primary market consists of commuters and travelers seeking on‑demand taxi alternatives within the regions where it maintains operational coverage. The organization’s technological infrastructure includes a backend server environment that stores booking data, driver assignments, and user account information, which is essential for the seamless functioning of its app‑based service.
The ransomware incident of July 18 2022 highlighted Zabicall’s dependence on its digital systems and underscored certain distinguishing attributes of its operations. The attack disrupted smartphone app‑based taxi dispatch across Gangwon‑do, Busan, Gyeonggi, Gyeongbuk, and Jeonnam, indicating a broad geographic footprint that spans multiple provincial jurisdictions. Following the breach, Zabicall engaged a national recovery center to identify the ransomware variant, demonstrating a protocol for collaborating with governmental cyber‑security entities during crises. The organization’s response included negotiating with the threat actors, paying a cryptocurrency ransom to regain access to its compromised backup server, and subsequently seeking the decryption key to restore affected data. While the incident revealed vulnerabilities in its backup and recovery procedures, it also illustrated Zabicall’s capacity to mobilize external expertise and undertake urgent remediation actions to resume service delivery. No explicit details regarding ownership, parent‑subsidiary relationships, or corporate structure are available in the provided sources, so those aspects are not addressed here.
