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

Incident Score: Analysis & Impact (TOYTHEFED1773051888)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-58
Company Score Before Incident811 / 1000
Company Score After Incident753 / 1000
Company LinkView FedEx Profile
INCIDENT NUMBERTOYTHEFED1773051888
Type of Cyber IncidentRansomware
ATTACK VECTORExploiting vulnerabilities in public-facing systems, Phishing, Initial access brokers, Social engineering, Help desk compromise
DATA EXPOSEDYes
INCIDENT DATE31/07/2025
STATUSpublished

Key Highlights From The Incident Analysis

  • Timeline of FedEx's Ransomware 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 FedEx 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 FedEx breach identified under incident ID TOYTHEFED1773051888.

The analysis begins with a detailed overview of FedEx's information like the linkedin page: https://www.linkedin.com/company/fedex, the number of followers: 2256620, the industry type: Freight and Package Transportation and the number of employees: 194419 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 811 and after the incident was 753 with a difference of -58 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 FedEx and their customers.

Government agencies recently reported "Emerging and Evolving Ransomware Threats: A 2024–2025 Overview", a noteworthy cybersecurity incident.

Recent years have seen a surge in sophisticated ransomware operations, with several groups refining tactics, expanding targets, and adapting to law enforcement disruptions.

The disruption is felt across the environment, affecting Windows, Linux and VMware ESXi servers, and exposing Yes.

Formal response steps have not been shared publicly yet.

The case underscores how teams are taking away lessons such as Ransomware groups are increasingly operating under affiliate models, employing double extortion tactics, and targeting critical infrastructure. Geopolitical ties and rebranding strategies complicate attribution and disruption efforts, and recommending next steps like Enhance monitoring of public-facing systems for vulnerabilities, Implement robust backup and recovery measures and Strengthen phishing and social engineering defenses.

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 Exploit Public-Facing Application (T1190) with high confidence (90%), with evidence including exploiting vulnerabilities in public-facing systems, and medusa exploits vulnerabilities in public-facing systems, Phishing (T1566) with high confidence (90%), with evidence including phishing listed as attack vector, and medusa uses phishing to breach organizations, Valid Accounts (T1078) with moderate to high confidence (80%), with evidence including stolen VPN credentials used by Qilin, and initial access brokers supply stolen credentials, and Trusted Relationship (T1199) with moderate to high confidence (70%), with evidence including initial access brokers provide entry points, and affiliates recruited from disrupted groups. Under the Execution tactic, the analysis identified User Execution: Malicious File (T1204.002) with moderate to high confidence (80%), with evidence including ransomware strains (.lynx, LockBit, etc.) encrypt files, and data encrypted for impact and Command and Scripting Interpreter (T1059) with moderate to high confidence (70%), with evidence including ransomware written in Golang and Rust (Qilin), and automated encryption processes. Under the Persistence tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (80%), with evidence including stolen VPN credentials used for access, and help desk compromise (Scattered Lapsus$ Hunters) and Create Account (T1136) with moderate confidence (60%), with evidence including affiliates recruited under RaaS models, and potential account creation for persistence. Under the Privilege Escalation tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (80%), with evidence including stolen credentials used for higher access, and initial access brokers provide privileged entry and Exploitation for Privilege Escalation (T1068) with moderate to high confidence (70%), with evidence including exploitation of unpatched vulnerabilities, and vMware ESXi servers targeted (Qilin). Under the Defense Evasion tactic, the analysis identified Obfuscated Files or Information (T1027) with moderate to high confidence (80%), with evidence including ransomware written in Golang and Rust (Qilin), and avoids dark web advertising (Play ransomware), Impair Defenses: Disable or Modify Tools (T1562.001) with moderate to high confidence (70%), with evidence including deleting backups (Lynx ransomware), and disabling security tools likely, and Indicator Removal (T1070) with moderate confidence (60%), with evidence including rebranding of groups (e.g., Lynx, RansomHub), and loose structure of Scattered Lapsus$ Hunters. Under the Credential Access tactic, the analysis identified Brute Force (T1110) with moderate confidence (60%), with evidence including stolen VPN credentials used, and potential brute force for credential access and Credentials from Password Stores (T1555) with moderate to high confidence (70%), with evidence including initial access brokers supply credentials, and help desk compromise (Scattered Lapsus$ Hunters). Under the Discovery tactic, the analysis identified File and Directory Discovery (T1083) with moderate to high confidence (80%), with evidence including data exfiltration before encryption, and targeting of high-value industries and System Information Discovery (T1082) with moderate to high confidence (70%), with evidence including targeting of Windows, Linux, VMware ESXi servers, and adaptation to victim environments. Under the Collection tactic, the analysis identified Data from Local System (T1005) with high confidence (90%), with evidence including data exfiltration before encryption (double extortion), and corporate data and PII compromised and Data from Information Repositories (T1213) with moderate to high confidence (70%), with evidence including targeting of critical infrastructure sectors, and high-value data stolen. Under the Command and Control tactic, the analysis identified Application Layer Protocol (T1071) with moderate to high confidence (80%), with evidence including raaS operations require C2 infrastructure, and affiliates communicate with operators and Ingress Tool Transfer (T1105) with moderate to high confidence (70%), with evidence including ransomware deployment via C2 channels, and tools transferred for encryption. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), with evidence including data exfiltration before encryption (double extortion), and high-volume data theft (e.g., Toyota, FedEx, Disney) and Exfiltration Over Web Service (T1567) with moderate to high confidence (70%), with evidence including data leaked on dark web or public sites, and salesforce campaign (Scattered Lapsus$ Hunters). Under the Impact tactic, the analysis identified Data Encrypted for Impact (T1486) with high confidence (100%), with evidence including ransomware strains (.lynx, LockBit, etc.) encrypt files, and data encryption confirmed in incident, Data Destruction (T1485) with moderate to high confidence (80%), with evidence including deleting backups (Lynx ransomware), and potential destruction of recovery options, and Inhibit System Recovery (T1490) with moderate to high confidence (80%), with evidence including backup deletion (Lynx), and encryption of VMware ESXi servers (Qilin). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Exploit Public-Facing Application (90%)
Phishing (90%)
Valid Accounts (80%)
Trusted Relationship (70%)
Execution
User Execution: Malicious File (80%)
Command and Scripting Interpreter (70%)
Persistence
Valid Accounts (80%)
Create Account (60%)
Privilege Escalation
Valid Accounts (80%)
Exploitation for Privilege Escalation (70%)
Defense Evasion
Obfuscated Files or Information (80%)
Impair Defenses: Disable or Modify Tools (70%)
Indicator Removal (60%)
Credential Access
Brute Force (60%)
Credentials from Password Stores (70%)
Discovery
File and Directory Discovery (80%)
System Information Discovery (70%)
Collection
Data from Local System (90%)
Data from Information Repositories (70%)
Command and Control
Application Layer Protocol (80%)
Ingress Tool Transfer (70%)
Exfiltration
Exfiltration Over C2 Channel (90%)
Exfiltration Over Web Service (70%)
Impact
Data Encrypted for Impact (100%)
Data Destruction (80%)
Inhibit System Recovery (80%)