Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Tellemica » TEL1764669631

Incident Score: Analysis & Impact (TEL1764669631)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-193
Company Score Before Incident752 / 1000
Company Score After Incident559 / 1000
Company LinkView Tellemica Profile
INCIDENT NUMBERTEL1764669631
Type of Cyber IncidentBreach
ATTACK VECTORDark Web Data Leak (Historical Dataset), Third-Party Cloud Storage Exploitation
DATA EXPOSEDNames, Addresses, Phone Numbers, Email...
INCIDENT DATE30/06/2024
STATUSSettled (2025)

Key Highlights From The Incident Analysis

  • Timeline of Tellemica's Breach and lateral movement inside company's environment.
  • Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
  • How Rankiteo’s incident engine converts technical details into a normalized incident score.
  • How this cyber incident impacts Tellemica Rankiteo cyber scoring and cyber rating.
  • Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.

Full Incident Analysis Transcript

In this Rankiteo incident briefing, we review the Tellemica breach identified under incident ID TEL1764669631.

The analysis begins with a detailed overview of Tellemica's information like the linkedin page: https://www.linkedin.com/company/tellemica, the number of followers: 279, the industry type: Telecommunications and the number of employees: 12 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 752 and after the incident was 559 with a difference of -193 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 Tellemica and their customers.

AT&T recently reported "AT&T Data Breaches Leading to $177 Million Class-Action Settlement", a noteworthy cybersecurity incident.

AT&T reached a $177 million (£133.9 million) class-action settlement following two major data breaches in 2024, compromising personal information of tens of millions of current and former customers.

The disruption is felt across the environment, affecting Dark Web (historical dataset) and Third-Party Cloud Storage Platform, and exposing Names, Addresses and Phone Numbers, with nearly Tens of millions records at risk, plus an estimated financial loss of $177 million (settlement).

In response, teams activated the incident response plan, and stakeholders are being briefed through Public disclosures (March 2024, July 2024).

The case underscores how Settled (2025).

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.

MITRE ATT&CK® Correlation Analysis

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Phishing: Spearphishing Link (T1566.002) with lower confidence (30%), supported by evidence indicating dark Web Data Leak (Historical Dataset) (possible credential harvest via phishing) and Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (80%), supported by evidence indicating third-Party Cloud Storage Exploitation (unauthorized access to cloud metadata). Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), supported by evidence indicating dataset dating from 2019 or earlier (PII including SSNs, passcodes collected) and Data from Information Repositories: Cloud Storage (T1213.002) with high confidence (95%), supported by evidence indicating metadata associated with calls and texts... downloaded illegally from third-party cloud. Under the Exfiltration tactic, the analysis identified Exfiltration Over Alternative Protocol: Exfiltration Over Unencrypted/Obfuscated Non-C2 Protocol (T1048.003) with moderate to high confidence (70%), supported by evidence indicating dataset surfaced on the dark web (implied unencrypted transfer) and Exfiltration Over Alternative Protocol: Exfiltration Over Asymmetric Encrypted Non-C2 Protocol (T1048.002) with moderate confidence (60%), supported by evidence indicating metadata... downloaded illegally from cloud (possible encrypted channel abuse). Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with moderate to high confidence (85%), supported by evidence indicating passcodes included in leaked 2019 dataset and Credentials from Password Stores: Credentials from Web Browsers (T1555.003) with lower confidence (40%), supported by evidence indicating historical dataset leak *may* include browser-stored credentials (implied by passcodes). Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with lower confidence (10%), supported by evidence indicating no ransomware mentioned, but data exfiltration implies potential leverage (low confidence) and Resource Hijacking: Cloud Resource Hijacking (T1496.002) with moderate to high confidence (75%), supported by evidence indicating third-Party Cloud Storage Exploitation (abuse of cloud resources for metadata exfiltration). Under the Defense Evasion tactic, the analysis identified Indicator Removal: File Deletion (T1070.004) with lower confidence (30%), supported by evidence indicating no direct evidence, but dark web leaks often involve log/file deletion (speculative) and Impair Defenses: Disable or Modify Cloud Logs (T1562.001) with moderate confidence (60%), supported by evidence indicating cloud metadata breach suggests possible log tampering to evade detection. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Sources & References