Incident Score: Analysis & Impact (SUR1789058174)

In this Rankiteo incident briefing, we review the Surfshark breach identified under incident ID SUR1789058174.

The analysis begins with a detailed overview of Surfshark's information like the linkedin page: https://www.linkedin.com/company/surfshark, the number of followers: 24823, the industry type: IT Services and IT Consulting and the number of employees: 495 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 502 and after the incident was 437 with a difference of -65 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on Surfshark and their customers.

On 01 September 2026, Surfshark disclosed Unauthorized Access issues under the banner "Surfshark Internal Server Breach".

VPN provider Surfshark disclosed a security breach involving unauthorized third-party access to an internal test server due to a misconfigured engineering server accidentally exposed to the public internet.

The disruption is felt across the environment, affecting Internal test server, secondary isolated server for content accessibility optimization, and exposing Internal engineering materials, system binaries, and configurations.

In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Disconnected affected servers, rotated credentials, and began remediation that includes Full infrastructure remediation completed by September 5, and stakeholders are being briefed through Public disclosure and transparency efforts.

The case underscores how Completed, teams are taking away lessons such as Need to strengthen security around testing environments, enforce production-level security standards for test systems, improve access controls, and enhance monitoring, and recommending next steps like Enforce the same security standards for test systems as live production infrastructure, improve access controls, enhance monitoring, and conduct independent security audits, with advisories going out to stakeholders covering No user data or VPN services were affected; incident posed no direct risk to users.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.