Oracle Faces Second Data Breach, 6 Million Records Compromised

Oracle Faces Second Data Breach, 6 Million Records Compromised

In a startling turn of events, Oracle Corporation experienced a significant data breach involving its older Gen 1 servers, making it the company’s second cybersecurity incident within weeks. The breach came to light after a threat actor, known as “rose87168,” claimed responsibility and disclosed the breach on Breachforums. The compromised information includes 6 million records such as usernames, email addresses, hashed passwords, and sensitive authentication credentials like Single Sign-On (SSO) and Lightweight Directory Access Protocol (LDAP) information. Java Key Store (JKS) files and Enterprise Manager JPS keys were also compromised. While no complete Personally Identifiable Information (PII) was revealed, the data breach has raised significant concerns about Oracle’s overall security protocols.

Details of the Breach

This breach was facilitated by a 2020 Java exploit that enabled the attacker to deploy a web shell and malware targeting Oracle’s Identity Manager (IDM) database. The threat actor managed to remain undetected from January to late February 2025, which led Oracle to initiate an internal investigation. During this period, the attacker was able to access and extract sensitive data, including usernames, email addresses, and hashed passwords. The sensitive authentication credentials that were compromised include critical elements such as SSO and LDAP information, which are essential for secure user authentication and authorization. Additionally, Java Key Store files and Enterprise Manager JPS keys were also compromised, which can have significant implications for the security of affected systems.

The compromised data is approximately 16 months old, indicating that it predates Oracle’s recent security enhancements. Oracle has notified its affected clients about the breach and has taken steps to enhance security around its Gen 1 servers. The company has also assured stakeholders that its primary Oracle Cloud infrastructure and Gen 2 servers were not involved in this incident. The fact that the data is not current may provide some relief to clients, but the breach still poses a considerable threat, especially if the compromised authentication credentials are used to gain unauthorized access to other systems.

Implications and Concerns

“Rose87168” appears to be relatively new to the cybercrime scene, yet their financial motives are clear, as evidenced by a $20 million ransom demand to Oracle. The threat actor has also shown an interest in trading stolen data for zero-day exploits, which could further jeopardize the security of various systems. Security researchers have verified portions of the released data, confirming the breach’s authenticity and adding credibility to the claims made by the threat actor. This incident follows another recent cybersecurity issue involving Oracle Health’s legacy Cerner servers, where U.S. patient data was compromised. Although Oracle has stated that these breaches are unrelated, their close timing has raised significant concerns about the company’s overall security stance.

The Gen 1 server breach highlights the vulnerabilities inherent in legacy systems that have not been fully migrated to modern cloud infrastructure. Experts warn that such breaches can have a cascading effect on the security of enterprise systems and supply chains, potentially leading to more extensive damage. The incident underscores the challenges that large companies face in securing legacy systems while transitioning to newer platforms. Affected clients are strongly advised to reset their credentials, monitor for any unusual activities, and implement stronger security measures to mitigate potential risks.

Oracle’s Response and Future Considerations

This security breach was enabled by a Java exploit from 2020, which let the attacker deploy a web shell and malware targeting Oracle’s Identity Manager (IDM) database. The threat actor stayed undetected from January to late February 2025, prompting Oracle to launch an internal investigation. During this window, the attacker accessed and extracted sensitive data such as usernames, email addresses, and hashed passwords. Compromised authentication credentials included key elements like SSO and LDAP information crucial for secure user authentication. Java Key Store files and Enterprise Manager JPS keys also fell into the wrong hands, posing significant security implications.

The compromised data dates back approximately 16 months, before Oracle’s recent security upgrades. Oracle has informed its affected clients and strengthened security around its Gen 1 servers. They assured stakeholders that the primary Oracle Cloud infrastructure and Gen 2 servers were not compromised. Although the data isn’t current, the breach still poses a serious threat, especially if the stolen credentials are used for unauthorized access to other systems.

Subscribe to our weekly news digest.

Join now and become a part of our fast-growing community.

Invalid Email Address
Thanks for Subscribing!
We'll be sending you our best soon!
Something went wrong, please try again later