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

Incident Score: Analysis & Impact (JAG2592025111525)

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

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-11
Company Score Before Incident439 / 1000
Company Score After Incident428 / 1000
Company LinkView Oracle Profile
INCIDENT NUMBERJAG2592025111525
Type of Cyber IncidentCyber Attack
ATTACK VECTORNA
DATA EXPOSEDTrue
INCIDENT DATE30/06/2025
STATUSResolved (Operations Stabilized)

Key Highlights From The Incident Analysis

  • Timeline of Oracle's Cyber Attack 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 Oracle 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 Oracle breach identified under incident ID JAG2592025111525.

The analysis begins with a detailed overview of Oracle's information like the linkedin page: https://www.linkedin.com/company/oracle, the number of followers: 11421378, the industry type: IT Services and IT Consulting and the number of employees: 207847 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 439 and after the incident was 428 with a difference of -11 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 Oracle and their customers.

On 02 September 2025, Jaguar Land Rover (JLR) disclosed Cyberattack, Data Breach and Operational Disruption issues under the banner "Cyberattack on Jaguar Land Rover (JLR) Disrupts Production and Incurs £196 Million in Costs".

Jaguar Land Rover (JLR) suffered a cyberattack announced on September 2, 2025, which forced the shutdown of major production plants and resulted in data theft.

The disruption is felt across the environment, affecting Production Plants, Supply Chain Systems and Parts Logistics, and exposing True, plus an estimated financial loss of £196 million (Q3 2025).

In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Shutdown of Production Plants and Isolation of Affected Systems (implied), while recovery efforts such as Phased Restart of Production (completed by October 8, 2025) and Restoration of Wholesale, Parts Logistics, and Supplier Financing continue, and stakeholders are being briefed through Public Disclosure (September 2, 2025), Follow-up Statements on Data Theft and Government Intervention and Financial Results Publication (Q3 2025).

The case underscores how Resolved (Operations Stabilized), with advisories going out to stakeholders covering UK Government Loan Guarantee (£1.5 billion) and Bank of England GDP Impact Assessment.

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 Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating scattered Lapsus$ Hunters (known for abusing valid credentials in past attacks) and Exploit Public-Facing Application (T1190) with moderate confidence (60%), supported by evidence indicating production Plants and Supply Chain Systems disrupted (common targets for app exploits). Under the Impact tactic, the analysis identified Service Stop (T1489) with high confidence (95%), supported by evidence indicating shutdown of major production plants for ~5 weeks and Defacement: Internal Data (T1491.002) with moderate to high confidence (80%), supported by evidence indicating data theft confirmed; implied manipulation of internal systems. 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 (85%), supported by evidence indicating data exfiltration confirmed (method unspecified but common for Lapsus$). Under the Lateral Movement tactic, the analysis identified Remote Services: Remote Desktop Protocol (T1021.001) with moderate to high confidence (70%), supported by evidence indicating supply Chain Systems and Parts Logistics affected (suggests internal pivoting). Under the Defense Evasion tactic, the analysis identified Indicator Removal: File Deletion (T1070.004) with moderate to high confidence (75%), supported by evidence indicating isolation of Affected Systems (implied) suggests attacker cleanup. Under the Credential Access tactic, the analysis identified Credentials from Password Stores (T1555) with moderate to high confidence (80%), supported by evidence indicating scattered Lapsus$ Hunters (known for credential theft from password managers/keystores). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Sources & References