Original Article Text

Click to Toggle View

CISA warns of increased breach risks following Oracle Cloud leak. On Wednesday, CISA warned of heightened breach risks after the compromise of legacy Oracle Cloud servers earlier this year and highlighted the significant threat to enterprise networks. CISA said, "the nature of the reported activity presents potential risk to organizations and individuals, particularly where credential material may be exposed, reused across separate, unaffiliated systems, or embedded (i.e., hardcoded into scripts, applications, infrastructure templates, or automation tools)," even though "the scope and impact remains unconfirmed." "When credential material is embedded, it is difficult to discover and can enable long-term unauthorized access if exposed. The compromise of credential material, including usernames, emails, passwords, authentication tokens, and encryption keys, can pose significant risk to enterprise environments," it added. The U.S. cybersecurity agency also released guidance to mitigate the risks linked to the resulting credential leak, urging network defenders to reset affected users' passwords, replace hardcoded or embedded credentials with secure authentication methods, enforce phishing-resistant multi-factor authentication (MFA) wherever possible, and monitor authentication logs for suspicious activity. This warning comes after Oracle confirmed in email notifications sent to customers that a threat actor leaked credentials stolen from what the company described as "two obsolete servers." However, Oracle added that its Oracle Cloud servers were not compromised, and the incident didn't impact its cloud services or customer data. ​Oracle also privately acknowledged in calls with some of its clients that attackers stole old client credentials after breaching a "legacy environment" last used in 2017. However, the hacker behind the breach posted newer records from 2025 on BreachForums and shared data with BleepingComputer from the end of 2024. BleepingComputer ​​​​​has separately confirmed with multiple Oracle customers that leaked data samples (including associated LDAP display names, email addresses, given names, and other identifying information) received from the threat actor were valid. In late March, cybersecurity firm CybelAngel also revealed that Oracle told customers that an attacker deployed a web shell and additional malware on some of its Gen 1 (also known as Oracle Cloud Classic) servers as early as January 2025. Until the breach was detected in late February, the attacker allegedly stole data from the Oracle Identity Manager (IDM) database, which included hashed passwords, usernames, and user emails. Last month, BleepingComputer first reported that Oracle also issued private customer notifications regarding another January breach at Oracle Health (a SaaS company previously known as Cerner) that impacted patient data at multiple U.S. healthcare organizations and hospitals.

Daily Brief Summary

DATA BREACH // CISA Issues Warning After Oracle Cloud Legacy Server Leak

CISA highlighted increased risks of breaches due to compromised Oracle Cloud legacy servers, warning about the exposure of sensitive credential material.

Oracle confirmed the compromise involved "two obsolete servers," which did not affect current Cloud services or customer data directly.

Leaked credential information included usernames, emails, passwords, authentication tokens, and encryption keys, posing a threat to enterprise environments.

CISA advised implementing several security measures: resetting passwords, replacing hardcoded credentials, enforcing multi-factor authentication, and monitoring authentication logs.

Oracle privately told clients that old client credentials were stolen from a legacy environment last active in 2017.

Threat actors had posted data as recent as 2025 on hacking forums, indicating ongoing unauthorized access and data extraction.

Oracle's breached servers included the use of a web shell and malware, with data theft occurring from the Oracle Identity Manager (IDM) database.

A separate breach in January affected Oracle Health and led to the compromise of U.S. patient data across healthcare organizations and hospitals.