Company Details
netsuite
16,597
496,833
5112
netsuite.com
0
NET_3125747
In-progress


NetSuite Vendor Cyber Rating & Cyber Score
netsuite.comFounded in 1998, Oracle NetSuite is the world’s first cloud company. For more than 25 years, NetSuite has helped businesses gain the insight, control, and agility to build and grow a successful business. First focused on financials and ERP, we now provide an AI-powered unified business system that includes inventory management, HR, professional services automation, and omnichannel commerce, used by more than 43,000 customers in 219 countries and dependent territories.
Company Details
netsuite
16,597
496,833
5112
netsuite.com
0
NET_3125747
In-progress
Between 750 and 799

NetSuite Global Score (TPRM)XXXX

Description: Oracle Issues Urgent Alert for Critical RCE Flaw in Identity and Web Services Manager Oracle has released an urgent security alert for a critical Remote Code Execution (RCE) vulnerability, tracked as CVE-2026-21992, affecting Oracle Identity Manager and Oracle Web Services Manager. The flaw allows unauthenticated attackers to remotely compromise systems by sending specially crafted network packets, enabling arbitrary code execution on vulnerable servers. Exploitation of this vulnerability could grant threat actors deep system access, allowing them to deploy malware, steal sensitive corporate identity data, or move laterally within an enterprise network. The flaw is rated under CVSS 3.1, though Oracle has withheld technical exploit details to prevent immediate weaponization. The vulnerability impacts Oracle Fusion Middleware versions 12.2.1.4.0 and 14.1.2.1.0 for both affected products. Oracle has released patches under KB878741, but only for versions covered by Premier Support or Extended Support. Organizations running end-of-life software must upgrade to supported releases before applying fixes. Given the severity of the flaw and the risk of exploitation by advanced persistent threats, Oracle emphasizes the need for immediate patch deployment to secure identity management infrastructure. The vulnerability operates over standard network protocols, leaving even HTTPS-secured systems exposed until updates are applied.
Description: Oracle E-Business Suite Hack Leaves Four Major Companies Silent on Impact A recent cyberattack targeting Oracle E-Business Suite (EBS) has disrupted organizations reliant on the platform for critical business operations, including finance, supply chain, HR, and procurement. While many companies have responded with public disclosures and mitigation efforts, Broadcom, Bechtel, Estée Lauder, and Abbott Technologies have yet to issue any statements, raising concerns about transparency and crisis management. The breach exposes vulnerabilities in a widely used enterprise software suite, threatening the integrity of sensitive corporate and customer data. Security researchers and incident response teams are assessing the full scope of the compromise, with affected organizations working to determine exposure and prevent follow-on attacks. In contrast to the silent four, other companies have taken proactive steps, including acknowledging the breach, implementing security measures, collaborating with cybersecurity firms, and notifying stakeholders. This approach is considered best practice in handling enterprise-wide software vulnerabilities. The continued silence from Broadcom, Bechtel, Estée Lauder, and Abbott Technologies leaves stakeholders uninformed about potential risks, data protection efforts, and the companies’ cybersecurity commitments. The lack of disclosure may also invite regulatory scrutiny, particularly for publicly traded firms, while risking long-term reputational damage. As cybersecurity incidents grow in frequency and severity, transparent communication is increasingly seen as a corporate obligation both for stakeholder trust and legal compliance. The absence of updates from these four companies underscores a critical gap in modern incident response policies.
Description: Loblaw Faces Alleged Massive Data Breach as Threat Actor Demands Response A threat actor operating under the handle *"igotafeeling"* on the *DarkWeb Informer* forum has claimed to have breached Loblaw, Canada’s largest food and pharmacy retailer, which owns brands like *President’s Choice, No Frills, Shoppers Drug Mart, Real Canadian Superstore*, and the *PC Optimum* loyalty program. The actor alleges possession of over 1.8 billion records, including: - 75.1 million Salesforce customer records (names, emails, phone numbers, addresses, loyalty IDs, and health card numbers) - 724.9 million Shoppers Drug Mart records (passwords, tokens, loyalty IDs, payment details, and full credit card numbers with expiry dates) - 129.9 million pharmacy fill requests (prescription numbers and patient IDs) - 120.4 million e-commerce fraud-feed records (payment card BINs, last-four digits, and expiry dates) - 20.2 million Delivery Ops Portal records (orders, deliveries, and postal codes) - 3,014 GitLab projects containing Loblaw’s full source code - 19.3 million Oracle identity records (MFA device details and credentials) - 55.3 million marketing and email records across 673 tables The threat actor has given Loblaw until March 19 to respond, accusing the company of *"ghosting"* them and dismissing customer and investor concerns. They have also invited media organizations to verify the data’s authenticity. In response, Loblaw issued a March 12 press release, labeling the incident a *"low-level data breach"* and stating that only *"basic customer information"* (names, phone numbers, and emails) may have been accessed. The company explicitly denied evidence of financial or credit card data compromise directly contradicting the threat actor’s claims. While the breach remains unverified, the scale of the alleged exposure if confirmed would rank among the largest in Canadian history. The situation mirrors past high-profile breaches (e.g., *T-Mobile, Equifax, Capital One*), where initial corporate statements downplayed impact before later revelations proved otherwise. Loblaw customers with *PC Optimum accounts, Shoppers Drug Mart loyalty cards, or prescription histories* may be affected if the claims hold true. The deadline for Loblaw’s response is six days away.
Description: DHS and ICE Contractor Data Breach Exposes Thousands of Entities A recent cybersecurity breach targeting the U.S. Department of Homeland Security’s (DHS) Office of Industry Partnership has exposed sensitive contract details involving over 6,600 organizations. The incident, first reported by the non-profit *Distributed Denial of Secrets*, was publicly disclosed by a hacking collective identifying itself as the *Department of Peace*. The leaked data includes comprehensive records of companies, government agencies, and universities that applied for or secured contracts with DHS and Immigration and Customs Enforcement (ICE). Among the affected entities are major firms such as Anduril, HBGary, L3Harris, Microsoft, Oracle, Palantir, and Raytheon, as well as federal agencies like the FBI and NASA. The compromised information spans: - Company names, URLs, and employee details (names, titles, contact information) - Business and personal addresses - Tax ID numbers, including Employer Identification Numbers (EINs) and potential Social Security Numbers (SSNs) - Government contractor identifiers (UEI numbers, CAGE codes) - Internal DHS staff comments on data updates - A secondary list detailing awarded contracts and their purposes, some of which were not publicly accessible via the DHS’s official portal The *Department of Peace* claimed the breach was motivated by opposition to DHS and ICE’s immigration enforcement policies, citing detentions, injuries, and deaths linked to their operations. The group stated its intent was to expose corporate and institutional ties to these agencies, though it acknowledged that some affected entities such as universities and public safety organizations were not the primary targets of its criticism. The full scope of the breach remains unclear, as the hackers described the data as "likely incomplete." The incident underscores ongoing risks to government contractor confidentiality and the potential for politically motivated cyberattacks to disrupt federal operations.
Description: MSGE Data Breach Exposes Personal Information of Over 131,000 Individuals Madison Square Garden Entertainment (MSGE), the operator of high-profile sports and entertainment venues in New York City and Chicago, disclosed a cybersecurity incident on March 2, 2026, affecting the personal data of more than 131,000 individuals. The breach involved unauthorized access to MSGE’s network, potentially compromising sensitive personally identifiable information (PII), including names, addresses, and Social Security numbers. The law firm Lynch Carpenter, LLP, has launched an investigation into the incident, inviting affected individuals to review potential legal claims. The firm, known for its work in data privacy litigation, has represented millions of clients in similar cases over the past decade. MSGE has not yet released further details on the breach’s origin, timeline, or remediation efforts. The incident adds to a growing list of high-profile data exposures in the entertainment and hospitality sectors, raising concerns about the security of customer and employee records.
Description: ShinyHunters Claims Breach of Wynn Resorts, Leaks 800K Employee Records The ransomware group *ShinyHunters* has allegedly breached Wynn Resorts, claiming to have stolen over 800,000 employee records and demanding 23.34 Bitcoin (≈$1.55 million) to delete the data. The group set a deadline of February 23, 2026, for payment, warning that failure to comply would result in the data being leaked on the dark web. A sample of the stolen data, analyzed by *The Register*, includes full names, emails, phone numbers, job positions, salaries, start dates, birth dates, and other personal details enough to facilitate phishing attacks, credential theft, and financial fraud. According to a group member, the breach occurred in September 2025 via an Oracle PeopleSoft vulnerability, exploiting compromised employee credentials. Wynn Resorts has not yet responded to the claims or media inquiries. *ShinyHunters* has been highly active in recent months, targeting organizations through vishing scams and exploiting identity management systems like Okta. This incident follows high-profile attacks on Caesars Entertainment and MGM Resorts in September 2023, reinforcing concerns over cybersecurity vulnerabilities in the hospitality and gaming sectors.
Description: Hypertherm Discloses Data Breach Impacting U.S. Employees After Oracle EBS Exploit Hypertherm, an employee-owned manufacturer of industrial cutting systems based in Hanover, New Hampshire, has reported a data breach exposing personal information due to a vulnerability in Oracle’s E-Business Suite (EBS) software. The incident was discovered on February 10, 2026, after an unauthorized actor exploited an unknown flaw in Oracle EBS to steal database tables from the company’s systems in August 2025. The breach compromised names and Social Security numbers of affected individuals, though the total number of impacted U.S. residents remains undisclosed. Hypertherm began notifying victims via mail on March 13, 2026, filing reports with the Maine, New Hampshire, and Texas Attorneys General. To date, 334 Texas residents, 166 New Hampshire residents, and 31 Maine residents have been confirmed as affected. The ransomware group CL0P claimed responsibility for the attack, posting about the breach on the dark web’s Tor network on November 21, 2025, categorizing it as a ransomware incident. Hypertherm is offering one year of free identity monitoring through Kroll, including credit monitoring, fraud consultation, and identity theft restoration. Affected individuals can enroll using a membership number provided in their notification letters. The company has also set up a dedicated call center (844-403-4502) for inquiries. While Hypertherm has not released nationwide impact figures, the breach underscores the risks of unpatched software vulnerabilities in enterprise systems. The incident follows a pattern of CL0P’s exploitation of third-party software flaws to extract sensitive data.
Description: University of Pennsylvania Data Breach Impact Far Smaller Than Initially Claimed A high-profile data breach at the University of Pennsylvania (Penn), initially alleged by anonymous hackers to have exposed records of 1.2 million students, donors, and alumni, was confirmed to have affected fewer than 10 individuals, according to a recent legal filing in a proposed class-action lawsuit. The breach, which occurred on October 31, targeted systems linked to development and alumni activities. Hackers sent a provocative email purporting to be from Penn to students and alumni, falsely claiming the university had "terrible security practices" and urging donors to "stop giving us money." Penn swiftly dismissed the hackers’ claims, stating it could not verify the scale of the breach and had engaged cybersecurity specialists to investigate. In a statement, the university confirmed that a "comprehensive review" of the compromised files concluded that only a limited number of individuals had their personal data exposed. Notifications were sent to those affected, as required by law. Penn also announced plans to implement mandatory cybersecurity training and strengthen defenses against future attacks. The incident sparked 18 proposed class-action lawsuits in the U.S. Eastern District Court, with plaintiffs alleging Penn failed to protect sensitive data, enabling cybercriminals to exploit it. However, in December, a federal judge consolidated the cases into a single lawsuit. Since then, eight plaintiffs have withdrawn, after learning that none of those who sued were among the impacted individuals, according to a Monday court filing. Attorneys for the remaining plaintiffs acknowledged that the small scope of the breach could weaken the case if pursued independently. They proposed merging the litigation with an ongoing lawsuit in Western Texas District Court related to a separate, larger breach involving Oracle E-Business Suite, which affected over 100 companies. Penn has not disclosed the number of individuals impacted in that incident. Disagreements among attorneys over the case’s leadership and jurisdiction remain unresolved. A judge is expected to decide which legal team will lead the litigation and whether the case will proceed in Philadelphia or Texas.
Description: Oracle Discloses Critical Proxy Vulnerability in Fusion Middleware (CVE-2026-21962) Oracle has revealed a severe security flaw (CVE-2026-21962) in its Fusion Middleware suite, specifically affecting the Oracle HTTP Server and WebLogic Server Proxy Plug-in. The vulnerability, rated CVSS 10.0, enables unauthenticated remote attackers to exploit systems without user interaction, posing a major risk to enterprise environments. The flaw lies in how the WebLogic Server Proxy Plug-ins for Apache HTTP Server and Microsoft IIS process incoming requests. Due to its location in the proxy layer, attackers can bypass security controls entirely, gaining unauthorized access to sensitive data and the ability to create, delete, or modify system data. The vulnerability’s "Scope Change" (S:C) metric indicates that successful exploitation could extend beyond the plug-in, potentially compromising backend WebLogic Server environments. Affected Versions: - Oracle HTTP Server / Proxy Plug-in: 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0 - WebLogic Server Proxy Plug-in for IIS: 12.2.1.4.0 Oracle has released patches in its Critical Patch Update (CPU), with temporary mitigation recommending restricted network access to affected HTTP ports if immediate patching is not possible. The flaw’s low attack complexity and high impact make it a priority for organizations using these components.
Description: Global Ransomware Attacks Surge 32% in 2025, With Manufacturing and U.S. Organizations Hit Hardest In 2025, global ransomware attacks reached 7,419 incidents, marking a 32% increase from the 5,631 recorded in 2024, according to a report by Comparitech. Of these, 1,173 attacks were confirmed by targeted organizations, while the remaining were claimed by ransomware groups via data leak sites. Collectively, the confirmed attacks breached 59.2 million records, though this figure is expected to rise as delayed reports emerge. ### Key Trends and Sector Impacts - Manufacturing saw the sharpest rise in attacks, surging 56% to 1,466 incidents, with average ransom demands more than doubling from $523,000 in 2024 to $1.2 million in 2025. - Legal firms experienced a 54% increase in attacks, alongside a 60% jump in ransom demands, averaging $610,000. - Healthcare and education saw stable attack volumes, with only 2% increases in incidents, suggesting a potential shift in attacker focus or improved defenses in these sectors. ### Geographic Breakdown The U.S. remained the most targeted country, accounting for 3,810 attacks (51% of the global total), a 33% increase from 2024. Other heavily affected nations included: - Canada: 392 attacks (31% increase) - Germany: 303 attacks (62% increase) - U.K.: 251 attacks (5% decrease) - France: 178 attacks (39% increase) - South Korea: 64 attacks (540% increase), driven largely by attacks on asset management firms following Qilin’s breach of a third-party provider. ### Ransomware Groups and Data Theft - Qilin was the most active group, responsible for 1,034 attacks (14% of the total), including 172 confirmed incidents. The group claimed to have stolen 31.2 petabytes of data, primarily from a single U.S. manufacturer. - Akira ranked second with 765 attacks, while SafePay was linked to the largest number of breached records (16.15 million), nearly all from its attack on Conduent. - DragonForce exposed 6.5 million records, mostly from its attack on the U.K.’s Co-operative Group, which resulted in £206 million ($276 million) in lost revenue. ### Notable Breaches in 2025 - Conduent (U.S.): 15.9 million records exposed in a SafePay attack, with 8.5 terabytes of data allegedly stolen. - Episource (U.S.): 5.4 million records compromised in an unidentified ransomware attack. - University of Phoenix (U.S.): 3.49 million records breached via a Clop attack exploiting an Oracle zero-day vulnerability. - DaVita (U.S.): 2.69 million records exposed in an Interlock attack, with 1.5 terabytes of data stolen. - Sanrio (Japan): 2 million records affected. - Asahi Group (Japan): 1.9 million records compromised. ### Sector-Specific Trends - Businesses bore the brunt of attacks (6,292 incidents, 35% increase), with 43 million records exposed in confirmed cases. Average ransom demands held steady at $1.09 million. - Government entities faced 374 attacks (27% increase), with 2.19 million records compromised. Ransom demands fell 15% to $1.55 million. - Healthcare saw 444 attacks (2% increase), with 10.1 million records exposed. Ransom demands plummeted 84% to $615,000. - Education recorded 252 attacks (2% increase), with 3.9 million records breached. Ransom demands dropped 34% to $457,200. The data underscores a strategic shift in ransomware targeting, with attackers prioritizing high-value commercial and public-sector entities while maintaining pressure on traditionally vulnerable sectors. Despite the surge in attacks, average ransom demands declined overall, dropping 26% to $1.04 million. However, select industries particularly manufacturing and legal services saw significant increases in both attack frequency and ransom demands.
Description: Higher Education Under Siege: A Wave of Cyberattacks Exposes Systemic Vulnerabilities In the first half of 2025, a surge of cyberattacks has targeted major U.S. universities, exposing critical weaknesses in higher education’s cybersecurity defenses. The University of Pennsylvania, Harvard University, and Princeton University all reported breaches within the past two months, following earlier incidents at Columbia University, Dartmouth College, and New York University. Each institution confirmed the attacks stemmed from social engineering, with Harvard and Princeton specifically citing phone-based phishing as the entry point. Officials at the affected schools stated they acted swiftly to contain the breaches and are reinforcing security measures. However, experts warn that universities face an uphill battle. Mike Corn, a former chief information security officer in higher education and current consultant at Vantage Technology, noted that colleges operate like "small cities," with decentralized networks, personal devices, and diverse user behaviors creating countless vulnerabilities. Even robust investments in cybersecurity, he argued, cannot guarantee immunity from attacks especially as AI-driven threats grow more sophisticated. The challenges extend beyond technology. Brian Nichols, CIO at the University of Kentucky, highlighted that while phishing simulations and training have improved awareness, they are not foolproof. Anita Nikolich, director of research and technology innovation at the University of Illinois at Urbana-Champaign, warned that punitive security measures can backfire, alienating faculty who may resist protocols perceived as restrictive. A core tension lies in academic freedom versus centralized IT control: many universities allow individual departments such as medical or business schools to maintain separate IT teams, increasing risk. Nikolich, who previously led IT infrastructure at the University of Chicago, described this fragmentation as a "huge risk factor," as decentralized systems complicate consistent security enforcement. Faculty resistance further complicates the issue. Janice Lanham, a nursing lecturer at Clemson University, nearly fell victim to a phishing scam but caught the deception in time. Yet, as Brian Voss, Clemson’s CIO, observed, some professors view security protocols as obstacles to research and teaching. Voss described a "culture of subservience" in higher-ed IT, where departments prioritize faculty demands over security, often retaining excessive data including sensitive information like Social Security numbers despite the risks. His efforts to reduce data storage have met resistance, with one university even retaining personal data for voter registration purposes, creating what he called "piles of gold for bad guys." The conflict between research needs and security is particularly acute. Nikolich, who also conducts quantum computing research, faced initial pushback when requesting network data for her work. After demonstrating the data’s non-sensitive nature and potential security benefits, she gained access but noted that other universities default to blanket denials. When researchers are blocked, she warned, they often bypass official channels, increasing exposure. The solution, Nikolich suggested, lies in collaboration: IT, security teams, and faculty must treat cybersecurity as a shared priority, balancing innovation with protection. Until then, universities remain prime targets caught between the demands of open academic environments and the escalating sophistication of cyber threats.
Description: Michelin Confirms Data Breach in Cl0p’s Oracle EBS Cyberattack Campaign Tire manufacturer Michelin has confirmed a data breach linked to the ongoing cybercrime campaign targeting organizations using Oracle’s E-Business Suite (EBS). The Cl0p ransomware and extortion group, believed to be operated by the FIN11 threat actor cluster, exploited zero-day vulnerabilities in Oracle EBS to access sensitive data from over 100 organizations, including Michelin. Michelin acknowledged the incident, stating that while its systems were protected by robust security measures, attackers leveraged an Oracle EBS zero-day flaw to infiltrate its network. The company reported that only a "small, localized volume of data" was compromised, with no sensitive or technical IT information affected. No ransomware was deployed, and global operations remained unaffected. Despite Michelin’s assurance that the breach was contained, Cl0p published over 315GB of allegedly stolen files on its leak site. Metadata analysis suggests the data originated from an Oracle EBS environment. Michelin emphasized its swift response, confirming that corrective actions were taken and the vulnerability has since been patched. This attack follows similar breaches at Madison Square Garden, auto parts supplier LKQ, the University of Phoenix, and Korean Air, all tied to the same Oracle EBS campaign. The incidents highlight the growing threat posed by sophisticated extortion groups exploiting enterprise software vulnerabilities.
Description: 2025: A Year of Rising Costs and Escalating Cyber Threats for UK Businesses As 2025 draws to a close, UK businesses and charities have faced a surge in financial pressures from soaring employment costs and supply chain disruptions to oil and tariff shocks. Yet, one of the most damaging expenses has been the fallout from cyberattacks, which have hit nearly half of British companies and 30% of charities over the past year. High-profile victims include retail giants Marks & Spencer, Adidas, and the Co-op Group, as well as Heathrow Airport, Harrods, and Jaguar Land Rover (JLR). The public sector hasn’t been spared either: Germany’s parliament and the UK Foreign Office (breached in October) were among those targeted. Attacks ranged from phishing scams to full-scale digital shutdowns, with some incidents costing hundreds of millions. The scale of cybercrime has reached staggering proportions. Cybersecurity Ventures estimates the global cost of cyberattacks in 2025 at $10.5 trillion (£7.8 trillion) a figure that would rank cybercrime as the world’s third-largest economy, trailing only the US and China. The financial and operational toll underscores the growing threat to organizations across sectors.
Description: TeamPCP Exploits Cloud Misconfigurations in Large-Scale Cybercrime Operation A threat actor known as TeamPCP (also operating under aliases like PCPcat and ShellForce) is conducting automated, worm-like attacks on misconfigured and exposed cloud management services, compromising at least 60,000 servers worldwide since late December. The group’s campaign primarily targets Azure (60% of attacks), AWS (37%), and Google and Oracle cloud environments, exploiting well-documented vulnerabilities and misconfigurations rather than developing new attack methods. TeamPCP’s operations involve scanning for exposed Docker APIs, Kubernetes clusters, Ray dashboards, and systems with leaked secrets (such as `.env` files). Once inside, the group deploys malicious Python and Shell scripts to install proxies, tunneling software, and persistence mechanisms, effectively converting compromised infrastructure into a self-propagating botnet. A key tool in their arsenal is the React2Shell vulnerability (CVE-2025-29927), which allows remote command execution and data exfiltration. The group monetizes its attacks through multiple revenue streams, including: - Cryptocurrency mining using hijacked compute resources. - Data theft and extortion, with stolen records including personal IDs, employment records, and résumés published on a leak site operated by an affiliate, ShellForce. - Selling access to compromised systems for use as proxies or command-and-control infrastructure. - Ransomware deployment, leveraging infected systems as launchpads for further attacks. Notably, TeamPCP has targeted JobsGO, a Vietnamese recruitment platform, exfiltrating over two million records containing sensitive personal and professional data. Most victims are located in South Korea, Canada, the U.S., Serbia, and the UAE, with stolen information often used for phishing, impersonation, or account takeovers. Despite its sophistication, TeamPCP’s techniques are not novel the group relies on automated exploitation of known vulnerabilities and recycled tooling. Security firm Flare warns that the threat actor’s strength lies in its large-scale automation, turning exposed cloud infrastructure into a distributed criminal ecosystem. The group also maintains a Telegram channel (launched in November, with ~700 members) for updates and reputation-building, though researchers suggest it may have operated under previous aliases. The campaign underscores the risks of unsecured cloud control planes, leaked credentials, and poor access controls, as TeamPCP continues to industrialize existing attack vectors with alarming efficiency.
Description: Record-Breaking DDoS Attack by Aisuru/Kimwolf Botnet Peaks at 31.4 Tbps On December 19, Cloudflare mitigated a historic distributed denial-of-service (DDoS) attack launched by the Aisuru (also known as Kimwolf) botnet, reaching an unprecedented 31.4 Tbps and 200 million requests per second (rps). The campaign, dubbed *"The Night Before Christmas,"* targeted telecommunications providers, IT organizations, and Cloudflare’s own infrastructure with hyper-volumetric HTTP and Layer 4 DDoS attacks. This attack surpassed Aisuru’s previous record of 29.7 Tbps, set earlier, and another Microsoft-attributed assault peaking at 15.72 Tbps from 500,000 IP addresses. Over 90% of the attacks in the campaign peaked between 1-5 Tbps, with most lasting 1-2 minutes. Despite their scale, Cloudflare’s automated systems detected and mitigated them without triggering internal alerts. The botnet’s power stems from compromised IoT devices and routers, though the December attacks primarily originated from Android TVs. Cloudflare’s 2025 Q4 DDoS Threat Report revealed a 121% year-over-year increase in DDoS attacks, with 47.1 million incidents recorded in 2025 averaging 5,376 attacks per hour. Network-layer attacks dominated (73%), while HTTP-based assaults made up the remainder. The most targeted industries included telecommunications, IT services, gambling, and gaming, with China, Hong Kong, Germany, Brazil, and the U.S. bearing the brunt of attacks. Bangladesh was the largest source of attacks, followed by Ecuador, Indonesia, and Argentina, while Russia dropped to 10th place. The report also noted a 600% increase in network-layer attacks exceeding 100 million packets per second (Mpps) and a 65% quarter-over-quarter rise in attacks over 1 Tbps. Over 71.5% of HTTP DDoS attacks were linked to known botnets.
Description: MSG Entertainment Investigates Data Breach Impacting Customer Personal Information New York-based Madison Square Garden Entertainment Corp. (MSG Entertainment) is under investigation following a data breach discovered on December 16, 2025, that exposed sensitive customer information. The incident stemmed from a vulnerability in the Oracle eBusiness Suite, hosted by a third-party vendor, which was exploited by hackers as early as August 2025. The breach potentially compromised names, addresses, and Social Security numbers of affected individuals. MSG Entertainment has since begun notifying impacted customers via mail. Edelson Lechtzin LLP, a national class action law firm, is leading an investigation into potential legal claims on behalf of those whose data was exposed. The firm specializes in data privacy litigation and is evaluating remedies for affected parties. MSG Entertainment operates high-profile venues, including Madison Square Garden, Radio City Music Hall, the Beacon Theatre, and the Chicago Theatre. The full scope of the breach and the number of individuals affected remain under review.
Description: University of Phoenix Hit by Massive Data Breach Affecting Millions In November 2025, the University of Phoenix disclosed a significant data breach impacting over 3.4 million current and former students and staff. The breach, attributed to the CL0P ransomware group, exploited a vulnerability in the university’s Oracle E-Business Suite software between August 13 and August 22, 2025, leading to the exfiltration of sensitive personal data. Exposed information included names, dates of birth, Social Security numbers, and financial details such as bank account and routing numbers. The university reported the incident to the California and Maine Attorney Generals’ offices on December 21, 2025, and began notifying affected individuals the following day. Among those impacted were 9,131 Maine residents. The breach has prompted legal action, with Shamis & Gentile P.A., a class-action law firm specializing in data breach cases, investigating potential compensation for victims. The university has offered free IDX identity theft protection services to those affected. The University of Phoenix, a private for-profit institution based in Phoenix, Arizona, serves working adults through online degree programs in fields like business, healthcare, and information systems. The incident underscores the growing threat of ransomware attacks targeting educational institutions.
Description: Clop Ransomware Gang Steals Data of 3.5 Million from University of Phoenix The Clop ransomware gang has stolen the personal and financial data of nearly 3.5 million individuals including current and former students, staff, and suppliers after breaching the University of Phoenix (UoPX) network in August 2025. The attack was part of a broader extortion campaign exploiting a zero-day vulnerability (CVE-2025-61882) in Oracle E-Business Suite (EBS), a financial application used by the university. UoPX, a private for-profit institution based in Phoenix, Arizona, detected the breach on November 21 after Clop listed the university on its data leak site. The stolen data includes names, contact details, dates of birth, Social Security numbers, and bank account information. In early December, the university publicly disclosed the incident and filed an 8-K report with the U.S. Securities and Exchange Commission (SEC). On Monday, UoPX confirmed in notification letters filed with Maine’s Attorney General that 3,489,274 individuals were affected. The university is offering free identity protection services, including credit monitoring, dark web surveillance, and a $1 million fraud reimbursement policy. While UoPX has not officially attributed the attack, the tactics align with Clop’s recent campaign targeting Oracle EBS vulnerabilities. Other U.S. universities, including Harvard and the University of Pennsylvania, have also reported similar breaches linked to the same exploit. Clop has a history of high-profile data theft operations, previously targeting GoAnywhere MFT, Accellion FTA, MOVEit Transfer, Cleo, and Gladinet CentreStack. The U.S. Department of State has offered a $10 million reward for information connecting the gang’s activities to a foreign government. In a separate wave of attacks since late October, multiple universities including Harvard, Princeton, and the University of Pennsylvania have also fallen victim to voice phishing (vishing) attacks, compromising systems tied to development and alumni activities.
Description: The NHS is investigating a cyberattack claimed by the extortion group Clop, which listed the NHS.uk domain on its leak site on November 11 without publishing any stolen data. The attack reportedly exploits a vulnerability in Oracle E-Business Suite (EBS), a system widely used across the NHS for managing sensitive patient data. While Clop did not specify which NHS branch was compromised, the potential exposure of patient records given the NHS’s role as Europe’s largest employer and a critical healthcare provider poses severe risks. The NHS, which refuses to pay ransoms, is collaborating with the National Cyber Security Centre (NCSC) to assess the breach. Historical attacks on the NHS have disrupted life-saving services, and this incident could similarly threaten patient safety if systems are compromised. The UK’s proposed ban on ransom payments for public sector organizations further complicates recovery efforts, leaving the NHS vulnerable to prolonged operational and reputational damage.
Description: US tech company F5 confirmed a data breach in which nation-state attackers stole the source code and vulnerability information related to its BIG-IP family of networking and security products. BIG-IP is a critical infrastructure component used by enterprises for traffic management, load balancing, and security, making this breach particularly severe. The stolen data could enable adversaries to identify and exploit undiscovered flaws in BIG-IP systems, potentially leading to supply-chain attacks, unauthorized network access, or large-scale disruptions in organizations relying on F5’s solutions. The breach underscores the escalating risks of state-sponsored cyber espionage targeting foundational IT infrastructure, with implications for global cybersecurity resilience. F5 has not disclosed whether customer data was compromised, but the theft of proprietary code and vulnerability details poses a long-term threat to its product ecosystem and the broader digital supply chain.
Description: Wits University Hit by Zero-Day Cyberattack, Oracle Investigating Potential Data Breach Wits University in South Africa has confirmed a cyberattack targeting its IT systems, classified as a zero-day exploit a breach leveraging an unknown vulnerability with no available patch at the time of the incident. The attack, which has affected organizations across multiple countries, prompted the university to collaborate with Oracle and cybersecurity experts to assess whether any data was compromised. While the full scope of the breach remains under investigation, Wits University has reported that some IT systems were compromised, though operations continue as normal. The institution has formally notified South Africa’s Information Regulator, adhering to data protection protocols. The incident underscores the growing threat of zero-day vulnerabilities, which leave organizations exposed until patches are developed. Further details on the attack’s impact and affected data are expected as the investigation progresses.
Description: Parexel Reports Data Breach Impacting Sensitive Employee Information Parexel, a global clinical research organization, disclosed a data breach affecting sensitive personal information stored in its Oracle OCI E-Business Suite (Oracle EBS) environment. On October 4, 2025, the company detected suspicious activity within the system, prompting an investigation. The breach, confirmed through forensic analysis, revealed that an unauthorized third party accessed employee-related data. Exposed information may include names, Social Security numbers, dates of birth, financial account numbers, payment card details (excluding CVVs), and national ID numbers, though the exact data varies by individual. On December 17, 2025, Parexel began notifying affected individuals via mail, detailing the compromised information and offering 24 months of complimentary credit monitoring services. The breach notice was filed with the Attorney General of Massachusetts, where impacted residents were among the first to be informed. The full scope of affected individuals and additional details remain under review.
Description: A large-scale phishing campaign targeted Oracle Hospitality through malicious search engine advertisements (malvertising), impersonating its services to deceive users. Victims were redirected to typosquatted domains mimicking legitimate login pages, harvesting credentials, email addresses, phone numbers, and passwords. The attackers bypassed multi-factor authentication (MFA) by capturing real-time one-time passwords (OTP) via SMS or email codes, gaining unauthorized access to cloud-based property management systems.The breach exposed sensitive guest data, including personal information and payment details, stored in these platforms. Technical analysis revealed Russian-speaking threat actors behind the operation, using sophisticated beaconing techniques to track victims’ geolocation, session duration, and engagement. The campaign posed significant risks to Oracle Hospitality’s operational integrity, customer trust, and financial security, with potential downstream impacts on booking systems and guest privacy.Security researchers highlighted the need for phishing-resistant authentication (e.g., passkeys, FIDO2 WebAuthn) and adaptive risk assessments to mitigate future threats. The incident underscores the growing sophistication of industry-specific cyberattacks targeting hospitality providers.
Description: Maritz Holdings Inc. Suffers Data Breach via Oracle E-Business Suite Vulnerability Maritz Holdings Inc., a Missouri-based management consulting firm with $1.4 billion in revenue and 4,250 employees, disclosed a data breach stemming from an exploited vulnerability in Oracle E-Business Suite (EBS). The incident occurred between August 10–13, 2025, before Oracle publicly acknowledged the flaw. The CL0P ransomware group claimed responsibility for the attack, posting details on the dark web. Maritz detected the breach on November 13, 2025, after launching an investigation with cybersecurity experts and notifying law enforcement. The probe confirmed that unauthorized access led to the exposure of sensitive data, including names, Social Security numbers, and financial account information. Affected individuals including current and former Maritz employees and clients were notified in writing on February 27, 2026. While the total number of impacted U.S. victims remains undisclosed, state-specific figures include four in Maine, 85 in Massachusetts, and three in New Hampshire. The breach highlights risks tied to third-party software vulnerabilities, particularly in widely used enterprise systems like Oracle EBS. Legal investigations are underway for potential compensation claims.
Description: SUNY Research Foundation Hit by Zero-Day Data Breach, Exposing Employee Personal Data The SUNY Research Foundation, based in Albany, New York, disclosed a data breach involving a zero-day vulnerability in Oracle’s eBusiness Suite. The attack occurred between August 9 and 11, with cybercriminals accessing personnel files containing sensitive employee information, including Social Security numbers. Oracle identified the flaw and released an urgent patch, but the breach went undetected until early October, when the company notified the foundation on October 10. Despite discovering the breach in October, the foundation only determined which files were accessed on November 26 nearly three months after the initial incident. Affected employees were notified last week, more than 60 days after the files were identified, exceeding New York’s 30-day notification requirement for data breaches. A foundation spokesperson acknowledged the delay, citing the complexity of forensic analysis needed to assess the scope of the breach. The foundation confirmed that no research data was compromised, and the attack was limited to personnel documents. The incident follows a pattern of similar breaches affecting thousands of organizations worldwide using the same Oracle software. The full extent of the exposure and potential misuse of the stolen data remains unclear.
Description: Cox Enterprises, a U.S.-based conglomerate with operations in telecommunications, media, and automotive services (e.g., Cox Communications, Autotrader), suffered a sophisticated data breach via a zero-day exploit (CVE-2025-61882) in Oracle’s E-Business Suite. Hackers, linked to the Cl0p ransomware group, infiltrated the network between August 9–14, 2025, exfiltrating 1.6TB of data including sensitive personal information of 9,479 individuals (names, addresses, dates of birth, Social Security numbers, and internal documents). The breach was detected in late September 2025, with Cl0p leaking the data on the dark web. The attack exploited an unpatched critical vulnerability (CVSS 9.8) allowing unauthorized database access, heightening risks of identity theft, financial fraud, and reputational damage. Oracle released an emergency patch post-breach, but the delay enabled widespread exploitation across other high-profile targets (e.g., The Washington Post, Harvard University). Cox offered affected parties credit monitoring, though long-term risks persist. The incident underscores vulnerabilities in ERP systems, supply chain security gaps, and the escalating threat of ransomware-as-a-service (RaaS) campaigns targeting enterprise software.
Description: Hypertherm, Inc. Data Breach Exposes Sensitive Data in 2025 Oracle EBS Hack Hypertherm, Inc., a manufacturer of industrial cutting products for sectors including shipbuilding, automotive repair, and manufacturing, confirmed a data breach affecting its Oracle E-Business Suite (EBS) systems. The incident, discovered on February 12, 2026, stemmed from an unauthorized intrusion in August 2025, during which an attacker exfiltrated database tables containing sensitive information. Hypertherm launched an investigation with third-party cybersecurity experts and began notifying affected individuals on March 13, 2026. The breach has since drawn legal scrutiny, with Edelson Lechtzin LLP, a national class action law firm, announcing an investigation into potential claims on behalf of impacted parties. The firm is evaluating legal remedies for those whose personal data may have been compromised. Hypertherm’s Oracle EBS software is used to manage critical operations, suggesting the breach could have exposed corporate or customer data. Further details on the scope of the exposed information remain undisclosed. The incident highlights ongoing risks associated with enterprise software vulnerabilities and delayed breach detection.
Description: The Clop ransomware gang exploited a critical zero-day vulnerability (CVE-2025-61882) in Oracle E-Business Suite (EBS), specifically within the BI Publisher Integration component, to conduct data theft attacks since at least August 2025. The flaw allowed unauthenticated remote code execution (RCE) via a single HTTP request, enabling attackers to steal sensitive corporate documents from unpatched systems. Oracle patched the vulnerability in early October 2025, but not before Clop launched an extortion campaign, emailing executives at multiple victim organizations to demand ransoms in exchange for not leaking the stolen data.The attack leveraged a vulnerability chain exposed by leaked proof-of-concept (PoC) exploits from the Scattered Lapsus$ Hunters group, increasing the risk of further exploitation by other threat actors. Clop’s campaign mirrors past high-profile breaches, including MOVEit Transfer (2,770+ organizations affected), Accellion FTA, and GoAnywhere MFT, reinforcing its reputation for large-scale data theft via zero-days. Oracle urged immediate patching, warning that internet-exposed EBS applications remain prime targets. The U.S. State Department has even offered a $10 million reward for intelligence linking Clop to foreign state sponsorship, underscoring the attack’s severity.
Description: Anywhere Real Estate Hit by Clop Ransomware Attack, Exposing 17,429 Customers In August, Anywhere Real Estate disclosed a data breach affecting 17,429 customers, following an attack by the Clop ransomware gang. The cybercriminals infiltrated the company’s Oracle E-Business Suite environment, accessing and potentially exfiltrating sensitive customer data. A breach notification filed with the Maine Attorney General’s Office confirmed the incident, though details on the exact nature of the compromised information remain limited. Clop, a well-known ransomware and extortion group, has been linked to multiple high-profile attacks, often targeting vulnerabilities in enterprise software. The breach at Anywhere Real Estate parent company of brands like Coldwell Banker, Century 21, and Sotheby’s International Realty highlights the growing threat to real estate and mortgage sectors, where vast amounts of personal and financial data are stored. The company has since notified impacted individuals, but the full scope of the breach’s consequences including potential identity theft or fraud remains unclear. This incident follows a broader trend of cyberattacks on real estate firms, underscoring the industry’s vulnerability to sophisticated ransomware operations.
Description: In August 2025, hackers breached Salesloft’s SaaS platform by stealing OAuth access tokens linked to its Drift chatbot integration with Salesforce. The attackers exploited these tokens functioning as trusted non-human identities to impersonate the integration and gain unauthorized access to Salesforce CRM data across hundreds of organizations. Over a 10-day campaign, they exfiltrated sensitive records, including stored credentials like AWS keys and Snowflake tokens from support case attachments. The breach highlighted the risks of unmonitored machine identities with excessive privileges, enabling large-scale data theft without traditional human account compromises.
Description: The Clop ransomware gang exploited a zero-day vulnerability in Oracle’s E-Business Suite, a critical enterprise software used for managing customer data, HR files, and corporate operations. The attack, active since at least July 10, allowed hackers to steal significant amounts of sensitive data, including personal information of corporate executives and employees, as well as customer data from affected organizations. Oracle initially claimed the vulnerabilities were patched, but later confirmed the zero-day flaw enabled remote exploitation without authentication, meaning attackers could breach systems without credentials.Google’s security researchers revealed that dozens of organizations were compromised, with the Clop gang using the stolen data for extortion campaigns. The group has a history of mass-hacking via unpatched vulnerabilities in file transfer tools (e.g., MOVEit, GoAnywhere), amplifying risks of large-scale data leaks. Oracle’s delayed acknowledgment and the ongoing exploitation of the flaw suggest prolonged exposure, increasing potential damage to financial records, executive identities, and corporate intellectual property.
Description: Oracle issued an emergency security update to patch a critical information disclosure vulnerability (CVE-2025-61884, CVSS 7.5) in its E-Business Suite (EBS) Runtime UI component (versions 12.2.3–12.2.14). The flaw allows unauthenticated remote attackers to exploit it over a network without credentials, granting access to sensitive corporate resources, including financial, employee, or customer data. The vulnerability was part of a broader extortion campaign linked to the Cl0p ransomware group (FIN11), which exploited a separate zero-day (CVE-2025-61882, CVSS 9.8) to steal data and send extortion emails to executives. While Oracle did not confirm active exploitation of CVE-2025-61884, the urgent patch suggests high risk. Attackers leveraged hacked email accounts and default password resets to gain credentials, potentially exposing confidential business data, intellectual property, or operational secrets. The incident highlights risks of supply-chain attacks and data breaches in enterprise software, with possible financial fraud, reputational damage, or regulatory penalties if exploited.
Description: Broadcom, a global technology leader valued at hundreds of billions, was among the high-profile victims of Cl0p’s ransomware attack exploiting a zero-day vulnerability in Oracle’s E-Business Suite (CVE-2025-61882 and CVE-2025-21884). The cybercriminal group exfiltrated sensitive corporate and customer data, threatening to leak or sell it unless a ransom was paid. The breach compromised critical systems, risking financial records, proprietary business data, and third-party customer information. Cl0p’s extortion tactics included warnings of public disclosure on their blog, torrent leaks, or sales to malicious actors, amplifying reputational and operational risks. Given Broadcom’s role in semiconductor and infrastructure technology, the attack posed supply chain cascading risks, potentially disrupting clients reliant on its products. Oracle issued emergency patches, but the damage including data theft, potential regulatory fines, and erosion of stakeholder trust had already occurred. The incident underscores vulnerabilities in enterprise software dependencies, with Broadcom facing long-term financial and strategic repercussions if the stolen data is weaponized.
Description: Oracle released an emergency patch for CVE-2025-61882 (CVSS 9.8), a critical zero-day vulnerability in its E-Business Suite, actively exploited by the Cl0p ransomware group and potentially the Scattered LAPSUS$ Hunters. The flaw allows unauthenticated remote attackers to execute arbitrary code via HTTP, compromising the Oracle Concurrent Processing component. Cl0p leveraged this in a high-volume phishing campaign, stealing large volumes of sensitive data from multiple victims in August 2025. Indicators of compromise (IoCs) include malicious IP addresses (e.g., 200.107.207[.]26, 185.181.60[.]11), reverse shell payloads, and exploit scripts (e.g., *oracle_ebs_nday_exploit_poc_...*). Mandiant warned of mass exploitation, urging organizations to investigate potential breaches even after patching, as attackers may have already exfiltrated data. The incident highlights the risk of supply-chain attacks via unpatched enterprise software, with Cl0p’s campaign targeting financial, HR, and operational data potentially disrupting business continuity and exposing customers/employees to fraud or regulatory penalties.
Description: Oracle faced two data security incidents with reported poor incident communication. An attacker allegedly accessed login servers and legacy Cerner data, leading to customers' personal information being at risk. Missteps in Oracle's response include outright denial, potentially misleading statements, and accusations of deleting evidence online, compounding the damage to their reputation.
Description: Oracle Health, the healthcare subsidiary of Oracle Corporation, experienced a data breach involving legacy Cerner data migration servers. This incident, which Oracle has communicated to its customers through private letters, is reported to have potentially exposed sensitive customer data. The breach is a consequence of Oracle's acquisition of Cerner Corp, a notable electronic health records business, as Oracle aimed to transition the healthcare software to cloud infrastructure. The significance of the data involved and the potential ramifications of such breaches in the healthcare sector underline the serious nature of this cybersecurity event.
Description: Oracle recently faced allegations of a data breach, with a threat actor claiming to have stolen 6 million records from Oracle Cloud's SSO login servers. Oracle has denied any breach, stating there was no compromise of their cloud services and customers' data remained secure. The threat actor, rose87168, attempted to sell the data and claimed the information includes SSO passwords, Java Keystore files, key files, and JPS keys from Oracle Cloud servers. Despite encrypted and hashed passwords requiring decryption or cracking, the impact of such a breach if proven accurate could potentially be significant, undermining trust in Oracle's cloud security and potentially impacting customers whose data was compromised.
Description: A breach at Oracle Health has resulted in the theft of patient data from legacy servers impacting multiple US healthcare organizations and hospitals. Unauthorized access by a threat actor after January 22, 2025, led to the exfiltration of Electronic Health Records (EHR) data with potential violations of HIPAA laws. There is uncertainty whether ransomware was involved, but Oracle Health's response has been criticized for lack of transparency and failure to provide proper guidance and documentation, leaving hospitals to navigate the aftermath themselves.
Description: Ransomware in 2025: A Systemic Threat Disrupting Global Supply Chains and Critical Services In 2025, ransomware evolved from isolated IT disruptions into a systemic risk, threatening national supply chains, essential services, and entire industries. Cybersecurity Ventures projects the global cost of ransomware will surge to $275 billion annually by 2031, driven by downtime, data loss, recovery efforts, and lost productivity not just ransom payments. A recent SOCRadar analysis highlighted the top 10 ransomware attacks of 2025, each exposing vulnerabilities across sectors: 1. Salesforce Ecosystem – A SaaS supply chain blind spot exploited for widespread disruption. 2. Oracle E-Business Suite – A zero-day attack leveraging supply chain extortion. 3. Jaguar Land Rover – Britain’s costliest cyberattack, crippling automotive operations. 4. Ingram Micro – A ransomware strike paralyzing global IT distribution. 5. Co-operative Group – A sustained siege on the UK retail sector. 6. PowerSchool – Large-scale extortion targeting the education sector. 7. Synnovis – Healthcare disruption with confirmed patient harm. 8. DaVita – Ransomware striking critical healthcare infrastructure. 9. Asahi Group – Manufacturing halts exposing IT-OT convergence risks. 10. Collins Aerospace – Ransomware grounding European airports. Key patterns emerged across these incidents: - Initial access frequently relied on stolen credentials or social engineering rather than sophisticated exploits. - Supply chain vulnerabilities amplified impact, turning single breaches into cascading failures. - Data theft and operational paralysis often outweighed encryption as the primary damage driver. - Delayed consequences such as regulatory penalties or confirmed human harm surfaced months after the attacks. The incidents underscore ransomware’s growing role as a strategic threat, with far-reaching consequences beyond financial losses.
Description: Oracle has patched a critical zero-day vulnerability (CVE-2025-61882) in its E-Business Suite, actively exploited by the Clop hacking group to steal personal information of corporate executives and extort victims. The flaw allows remote exploitation without credentials, enabling mass data theft from thousands of organizations using the suite for customer data and employee HR files. Initially, Oracle downplayed the threat, linking extortion emails to older patched vulnerabilities from July. However, the newly discovered zero-day confirms ongoing exploitation since at least August 2024, with Clop demanding ransom to prevent leaking stolen data. Google’s Mandiant reported widespread attacks, though not all victims have been contacted yet. The breach poses severe risks to executive privacy, corporate reputation, and operational security, with potential cascading effects on Oracle’s enterprise clients globally.
Description: A new extortion campaign targeted executives across multiple companies using Oracle E-Business Suite, with threat actors (potentially the Clop ransomware gang/FIN11) sending emails claiming theft of sensitive data. The campaign, active since at least September 29, 2025, leveraged hundreds of compromised email accounts, some linked to prior FIN11 activity. While the emails included contact details tied to Clop’s data leak site, Mandiant and Google Cloud have not yet confirmed actual data theft. The attack exploits potential vulnerabilities in Oracle’s platform, though no zero-day confirmation exists. Organizations were urged to investigate unusual access in their Oracle environments. Clop, known for ransomware deployment and data extortion, has historically exploited file transfer flaws (e.g., Cleo zero-days in 2024) to steal corporate data. The U.S. State Department offers a $10M reward for ties between Clop and foreign governments. The incident remains under investigation, with risks including financial extortion, reputational damage, and potential data leaks if claims are substantiated.
Description: Hackers linked to the Russian ransomware gang Clop (FIN11) are exploiting vulnerabilities in Oracle E-Business Suite, a critical enterprise platform managing finance, HR, and supply chain data. The threat actors claim to have stolen sensitive corporate information and are conducting a high-volume extortion campaign, targeting executives across multiple organizations via compromised email accounts. While the exact scope of the breach remains unconfirmed, the group has historically leveraged stolen data for ransom demands rather than system disruption. Oracle previously disclosed a January 2024 incident where hackers accessed legacy systems and stole client credentials, raising concerns about credential reuse and exposure. The current campaign, launched on September 29, 2024, mirrors Clop’s past tactics such as the MOVEit attacks which impacted 2,773 organizations and exposed 96 million records. The group has demanded ransoms under the threat of leaking stolen data, using email addresses tied to Clop’s official leak site. Mandiant and Google Threat Intelligence Group (GTIG) are investigating but have not yet verified the full extent of the breach or the legitimacy of the stolen data claims.
Description: The Clop ransomware gang (Graceful Spider) breached Oracle Corporation by exploiting a critical zero-day vulnerability (CVE-2025-61882) in Oracle E-Business Suite (EBS), an unauthenticated remote code execution (RCE) flaw with a CVSS score of 9.8. The attack bypassed authentication via the SyncServlet endpoint and injected malicious XSLT templates through RF.jsp, granting full control over enterprise systems. Oracle’s internal data and customer information were exposed, with Clop listing the company on its dark web leak site under a 'PAGE CREATED' status. The breach aligns with Clop’s broader campaign targeting high-profile victims (e.g., Mazda, Humana, Washington Post) via extortion emails threatening public data leaks unless ransoms are paid. The attack leveraged reused infrastructure from prior exploits (e.g., 2023 MOVEit vulnerability), with 96 distinct IPs tied to Russian-linked service providers. The incident underscores the severe risk posed by unpatched EBS instances, which manage critical functions like procurement, logistics, and financial records globally.
Description: The cyberattack on Oracle Cloud orchestrated by 'rose87168' led to the theft of 6 million records potentially affecting over 140,000 tenants. Exfiltrated data includes sensitive JKS files, encrypted SSO passwords, key files, and JPS keys. This information is now sold on dark web forums. The breach, exploiting CVE-2021-35587, poses risks of unauthorized access and corporate espionage given the type of data stolen. Oracle's compromised subdomain and vulnerable software version highlight security gaps and raise concerns of lateral movement within the cloud environment.
Description: Oracle Corporation endured a data breach affecting its Gen 1 servers, with no complete PII exposure but involving 6 million data records including usernames, email addresses, and hashed passwords. Sensitive credentials related to SSO and LDAP were also compromised. The breach, attributed to the threat actor 'rose87168' via a 2020 Java exploit, resulted in the theft of JKS files and Enterprise Manager JPS keys from legacy systems approximately 16 months old. Oracle has informed clients and taken steps to bolster Gen 1 server security while maintaining that its Gen 2 servers and primary Oracle Cloud infrastructure remain secure.
Description: The Clop ransomware gang (Graceful Spider) exploited a critical zero-day vulnerability (CVE-2025-61882) in Oracle E-Business Suite (EBS), an enterprise resource planning system used for order management, procurement, and logistics. The unauthenticated remote code execution (RCE) flaw allowed attackers to bypass authentication via the OA_HTML/SyncServlet endpoint and inject malicious XSLT templates through OA_HTML/RF.jsp, granting full control over sensitive ERP data. Oracle was listed on Clop’s dark web leak site, suggesting internal corporate data potentially financial and employee records was compromised. The attack leveraged reused infrastructure from prior campaigns (e.g., 2023 MOVEit exploits), with extortion emails sent to victims demanding ransom to prevent data leaks. Over 1,025 victims and $500M+ in extorted funds since 2019 highlight Clop’s persistence. The breach poses severe risks to Oracle’s supply chain integrity, operational continuity, and reputation, with potential cascading effects on clients like Mazda, Humana, and the Washington Post, also listed as victims.
Description: A Russian cybercrime group breached 100 computer systems belonging to Oracle's retail division and MICROS point-of-sale credit card payment systems. It did not expose corporate networks and other cloud and service offerings that were not affected by the breach. Oracle urged Micros customers to change their passwords and any passwords used by Micros representatives to access their on-premise systems.
Description: On July 10, 2013, Fidelity Investments experienced a data breach reported by the California Office of the Attorney General on July 31, 2013. An unauthorized individual gained access to a report containing sensitive personal information of Oracle Corporation employees, including names and Social Security numbers. The breach exposed confidential employee data, though the exact number of affected individuals remains undisclosed. The incident highlights a significant security lapse, as the compromised data could facilitate identity theft, financial fraud, or targeted phishing attacks against the affected employees. While the breach did not directly impact Fidelity’s customers, the exposure of third-party (Oracle) employee records underscores vulnerabilities in data handling and access controls. The breach’s discovery and reporting delay (21 days) may have further exacerbated risks, as affected individuals were left uninformed during this period. Such breaches erode trust in financial institutions’ ability to safeguard sensitive information, potentially leading to reputational damage and regulatory scrutiny. The nature of the stolen data Social Security numbers makes it particularly high-risk, as this information is immutable and highly valuable to cybercriminals for long-term exploitation.


No incidents recorded for NetSuite in 2026.
No incidents recorded for NetSuite in 2026.
No incidents recorded for NetSuite in 2026.
NetSuite cyber incidents detection timeline including parent company and subsidiaries

Founded in 1998, Oracle NetSuite is the world’s first cloud company. For more than 25 years, NetSuite has helped businesses gain the insight, control, and agility to build and grow a successful business. First focused on financials and ERP, we now provide an AI-powered unified business system that includes inventory management, HR, professional services automation, and omnichannel commerce, used by more than 43,000 customers in 219 countries and dependent territories.

Founded in 2015, Daraz is the leading e-commerce platform in South Asia with operations in Pakistan, Bangladesh, Sri Lanka, Nepal, and Myanmar. It provides sellers and consumers with cutting-edge marketplace technology, targeting a rapidly growing region of over 500 million people. By building an in

Cadence is a market leader in AI and digital twins, pioneering the application of computational software to accelerate innovation in the engineering design of silicon to systems. Our design solutions, based on Cadence’s Intelligent System Design™ strategy, are essential for the world’s leading semic
Broadcom's VMware software manages cloud complexity so customers can modernize infrastructure, accelerate app development, and protect workloads, wherever these reside. Our flagship cloud solutions provide the security and performance of private cloud combined with the scale and agility of public c

NiCE is transforming the world with AI that puts people first. Our purpose-built AI-powered platforms automate engagements into proactive, safe, intelligent actions, empowering individuals and organizations to innovate and act, from interaction to resolution. Trusted by organizations throughout 150
A problem isn't truly solved until it's solved for all. Googlers build products that help create opportunities for everyone, whether down the street or across the globe. Bring your insight, imagination and a healthy disregard for the impossible. Bring everything that makes you unique. Together, we c
Shopify is a leading global commerce company, providing trusted tools to start, grow, market, and manage a retail business of any size. Shopify makes commerce better for everyone with a platform and services that are engineered for reliability, while delivering a better shopping experience for consu
IDEMIA Secure Transactions (IST) is a leading provider of payment, connectivity, and cybersecurity solutions, serving billions of people worldwide. With decades of expertise in cryptography and credential issuance, IST is trusted by over 2000 financial institutions, mobile operators, automotive manu

With our unique ability to offer end-to-end solutions that connect the three pillars of IoT - Sensors, Software, and Services, we enable businesses to move from the traditional to the digital, or improve businesses by introducing a digital element in their products and processes. Now more than ever

At DoorDash, our mission to empower local economies shapes how our team members move quickly and always learn and reiterate to support merchants, Dashers and the communities we serve. We are a technology and logistics company that started with door-to-door delivery, and we are looking for team membe
.png)
Rising costs and shifting consumer demands are reshaping the CPG industry. These 13 trends are compelling companies to adopt new growth...
See how Good Price Pharmacy Warehouse streamlined multi-entity reporting and scaled operations with Oracle NetSuite, supported by RSM.
Demand for internet services is booming, but ISPs must address significant technical, operational, financial, and competitive challenges to...
Oracle collaborates with West Bengal Electronics Industry Development Corporation Limited to offer trainings and certifications for the...
As technology reshapes telecom, mapping the value chain provides operators with a straightforward path toward smarter strategic decisions...
Malicious Chrome extensions on the Chrome Web Store masquerading as productivity and security tools for enterprise HR and ERP platforms were...
Cybersecurity researchers have discovered five new malicious Google Chrome web browser extensions that masquerade as human resources (HR)...
Operations determine whether internet service providers succeed or fail. See how leading ISPs use ERP software to optimize operations and...
Telecommunications is undergoing a transformation, with new technologies and business models redrawing the landscape.

Explore insights on cybersecurity incidents, risk posture, and Rankiteo's assessments.
The official website of NetSuite is http://www.netsuite.com.
According to Rankiteo, NetSuite’s AI-generated cybersecurity score is 787, reflecting their Fair security posture.
According to Rankiteo, NetSuite currently holds 0 security badges, indicating that no recognized compliance certifications are currently verified for the organization.
According to Rankiteo, NetSuite has been affected by multiple supply chain cyber incidents. The affected supply chain sources and their corresponding incident IDs are:
According to Rankiteo, NetSuite is not certified under SOC 2 Type 1.
According to Rankiteo, NetSuite does not hold a SOC 2 Type 2 certification.
According to Rankiteo, NetSuite is not listed as GDPR compliant.
According to Rankiteo, NetSuite does not currently maintain PCI DSS compliance.
According to Rankiteo, NetSuite is not compliant with HIPAA regulations.
According to Rankiteo,NetSuite is not certified under ISO 27001, indicating the absence of a formally recognized information security management framework.
NetSuite operates primarily in the Software Development industry.
NetSuite employs approximately 16,597 people worldwide.
NetSuite presently has no subsidiaries across any sectors.
NetSuite’s official LinkedIn profile has approximately 496,833 followers.
NetSuite is classified under the NAICS code 5112, which corresponds to Software Publishers.
No, NetSuite does not have a profile on Crunchbase.
Yes, NetSuite maintains an official LinkedIn profile, which is actively utilized for branding and talent engagement, which can be accessed here: https://www.linkedin.com/company/netsuite.
As of April 02, 2026, Rankiteo reports that NetSuite has experienced 48 cybersecurity incidents.
NetSuite has an estimated 29,308 peer or competitor companies worldwide.
Incident Types: The types of cybersecurity incidents that have occurred include Ransomware, Cyber Attack, Breach and Vulnerability.
Total Financial Loss: The total financial loss from these incidents is estimated to be $275.48 billion.
Detection and Response: The company detects and responds to cybersecurity incidents through an containment measures with password change recommendation, and communication strategy with customer advisory, and communication strategy with criticized for lack of transparency, and communication strategy with private letters to customers, and communication strategy with outright denial, communication strategy with potentially misleading statements, communication strategy with accusations of deleting evidence online, and remediation measures with informed clients, remediation measures with bolstered gen 1 server security, and law enforcement notified with yes (california office of the attorney general), and third party assistance with okta threat intelligence (analysis by moussa diallo), and containment measures with monitoring for suspicious domain registrations, containment measures with blocking known malicious domains, and remediation measures with implementation of phishing-resistant authentication (e.g., passkeys, fido2 webauthn), remediation measures with adaptive risk assessments for unusual access patterns, and communication strategy with customer advisories about impersonation attempts, communication strategy with industry-wide alerts, and enhanced monitoring with real-time tracking of typosquatted domains, enhanced monitoring with beaconing detection, and incident response plan activated with recommended (investigate oracle e-business suite environments), and third party assistance with mandiant (google cloud), third party assistance with gtig, and enhanced monitoring with recommended (for unusual access), and and third party assistance with mandiant (google cloud), third party assistance with google threat intelligence group (gtig), and communication strategy with public warning via cybersecurity firms (mandiant, gtig), communication strategy with media outreach (recorded future news), and and third party assistance with mandiant (google cloud), and containment measures with emergency patch release (cve-2025-61882), containment measures with advisory for customer mitigation, and remediation measures with patch application, remediation measures with investigation into potential prior compromise, and communication strategy with public advisory, communication strategy with linkedin post by oracle cso, communication strategy with mandiant technical alert, and enhanced monitoring with recommended for customers to detect prior compromise, and incident response plan activated with yes (oracle released patch and urged immediate installation), and third party assistance with google mandiant (investigation and advisory), and containment measures with patch release (cve-2025-61882), containment measures with indicators of compromise (iocs) shared with customers, and remediation measures with urgent patch installation recommended for all customers, and communication strategy with public security advisory by oracle cso rob duhart, communication strategy with linkedin post by google mandiant cto charles carmakal, and incident response plan activated with oracle security alert (urgent patching advisory), and third party assistance with crowdstrike (detection and analysis), third party assistance with mandiant (investigation), third party assistance with google threat intelligence group (gtig), and containment measures with patching cve-2025-61882, containment measures with disabling exposed ebs components, and communication strategy with oracle customer advisory, communication strategy with public disclosure of poc risks, and enhanced monitoring with recommended for oracle ebs environments, and incident response plan activated with yes (google and oracle), and third party assistance with google security researchers, and remediation measures with oracle security advisory issued, remediation measures with technical indicators shared by google for detection, and communication strategy with public advisory by oracle, communication strategy with blog post by google, communication strategy with media statements, and enhanced monitoring with recommended (google provided indicators for detection), and incident response plan activated with yes (oracle released emergency security alerts and patches), and third party assistance with google threat intelligence, third party assistance with mandiant, third party assistance with crowdstrike, and containment measures with emergency patching (cve-2025-61884 & cve-2025-61882), containment measures with urgent advisory for customers to apply updates, and remediation measures with patch deployment, remediation measures with mitigation guidance for unpatched systems, and communication strategy with public security advisories, communication strategy with direct customer notifications, and enhanced monitoring with recommended (oracle advised customers to monitor for exploitation attempts), and incident response plan activated with yes (microsoft patch tuesday), incident response plan activated with yes (certificate revocation), incident response plan activated with yes (doj seizure), incident response plan activated with varies (healthcare sector), and third party assistance with law enforcement (doj), and law enforcement notified with yes (doj), and containment measures with patches released, containment measures with certificate revocation, containment measures with asset seizure, and remediation measures with patch for cve-2025-61884, remediation measures with october 2025 security updates, remediation measures with aem jee misconfiguration fix, remediation measures with malicious cert blacklisting, remediation measures with cisco ios/ios xe patches, remediation measures with bluetooth protocol updates, and and communication strategy with patch tuesday announcement, communication strategy with public breach disclosure, communication strategy with cisa kev catalog update, communication strategy with microsoft security blog, communication strategy with cisco security advisory, communication strategy with doj press release, communication strategy with alias robotics advisory, communication strategy with healthcare it alerts, and and and and and incident response plan activated with partial (5,000 user credentials rotated, but nhi token overlooked), and and and containment measures with token revocation (post-incident), containment measures with token revocation (post-discovery of compromise), and and and and and and and and incident response plan activated with yes (nhs cybersecurity team involved), and third party assistance with yes (national cyber security centre - ncsc), and communication strategy with public statement issued (neither confirmed nor denied intrusion), and remediation measures with patch released in october 2025 security alert, and third party assistance with security researchers (the raven file), and remediation measures with oracle released patch in october 2025, and and third party assistance with potential involvement of mandiant (forensic investigation), and containment measures with patch application (oracle emergency patch on 2025-10-04), containment measures with network segmentation (assumed), and remediation measures with free credit monitoring for affected individuals, remediation measures with ongoing forensic investigation, and communication strategy with notification letters to affected parties, communication strategy with public disclosure via maine attorney general’s office filing, and network segmentation with recommended (not explicitly confirmed), and enhanced monitoring with recommended (not explicitly confirmed), and and third party assistance with mandiant (google-owned cybersecurity firm), and containment measures with oracle security patches (cve-2025-61882, cve-2025-21884), and remediation measures with patch application for oracle ebs vulnerabilities, and communication strategy with oracle security alerts to customers, communication strategy with public disclosure via media, and communication strategy with data breach notification letters mailed to impacted individuals, and communication strategy with public disclosure on official website, sec filing, notification letters to affected individuals, and communication strategy with written notice to affected individuals on dec. 22, 2025, and incident response plan activated with yes, and containment measures with removed hackers' access to internal systems, and remediation measures with stepped up security protocols, and communication strategy with public statements to stakeholders, and containment measures with restricted network access to affected http ports, and remediation measures with patches released in critical patch update (cpu), and incident response plan activated with automated detection and mitigation, and containment measures with automated systems mitigated attacks without triggering internal alerts, and incident response plan activated with engaged cybersecurity specialists, and third party assistance with cybersecurity specialists, and remediation measures with comprehensive review of compromised files, notifications to affected individuals, and communication strategy with public statement dismissing hackers' claims, notifications to affected individuals, and containment measures with oracle released an urgent patch for the zero-day vulnerability, and communication strategy with affected employees were notified last week, and third party assistance with flare (security firm), and communication strategy with notified impacted individuals via breach notification, and communication strategy with customer notifications via mail, and third party assistance with lynch carpenter, llp (investigation), and third party assistance with cybersecurity experts, and law enforcement notified with yes, and communication strategy with written notifications to affected individuals, and incident response plan activated with yes, and containment measures with corrective actions taken, vulnerability patched, and remediation measures with vulnerability patched, and communication strategy with public disclosure and assurance of containment, and communication strategy with press release downplaying the breach and denying financial data compromise, and third party assistance with third-party cybersecurity experts, and communication strategy with notification to affected individuals, and third party assistance with kroll (identity monitoring), and communication strategy with notification letters mailed to affected individuals, dedicated call center (844-403-4502), and communication strategy with lack of public disclosure from affected companies, and third party assistance with oracle and cybersecurity experts, and remediation measures with patch deployment (kb878741), and communication strategy with urgent security alert issued..
Title: Oracle MICROS Point-of-Sale System Breach
Description: A Russian cybercrime group breached 100 computer systems belonging to Oracle's retail division and MICROS point-of-sale credit card payment systems. It did not expose corporate networks and other cloud and service offerings that were not affected by the breach. Oracle urged Micros customers to change their passwords and any passwords used by Micros representatives to access their on-premise systems.
Type: Data Breach
Attack Vector: Network Intrusion
Threat Actor: Russian Cybercrime Group
Title: Alleged Data Breach at Oracle Cloud
Description: Oracle recently faced allegations of a data breach, with a threat actor claiming to have stolen 6 million records from Oracle Cloud's SSO login servers. Oracle has denied any breach, stating there was no compromise of their cloud services and customers' data remained secure. The threat actor, rose87168, attempted to sell the data and claimed the information includes SSO passwords, Java Keystore files, key files, and JPS keys from Oracle Cloud servers. Despite encrypted and hashed passwords requiring decryption or cracking, the impact of such a breach—if proven accurate—could potentially be significant, undermining trust in Oracle's cloud security and potentially impacting customers whose data was compromised.
Type: Data Breach
Threat Actor: rose87168
Motivation: Financial Gain
Title: Cyberattack on Oracle Cloud by 'rose87168'
Description: The cyberattack on Oracle Cloud orchestrated by 'rose87168' led to the theft of 6 million records potentially affecting over 140,000 tenants. Exfiltrated data includes sensitive JKS files, encrypted SSO passwords, key files, and JPS keys. This information is now sold on dark web forums. The breach, exploiting CVE-2021-35587, poses risks of unauthorized access and corporate espionage given the type of data stolen. Oracle's compromised subdomain and vulnerable software version highlight security gaps and raise concerns of lateral movement within the cloud environment.
Type: Data Breach
Attack Vector: Exploitation of CVE-2021-35587
Vulnerability Exploited: CVE-2021-35587
Threat Actor: 'rose87168'
Motivation: Unauthorized accessCorporate espionage
Title: Data Breach at Oracle Health
Description: A breach at Oracle Health has resulted in the theft of patient data from legacy servers impacting multiple US healthcare organizations and hospitals. Unauthorized access by a threat actor after January 22, 2025, led to the exfiltration of Electronic Health Records (EHR) data with potential violations of HIPAA laws. There is uncertainty whether ransomware was involved, but Oracle Health's response has been criticized for lack of transparency and failure to provide proper guidance and documentation, leaving hospitals to navigate the aftermath themselves.
Type: Data Breach
Attack Vector: Unauthorized Access
Title: Oracle Health Data Breach
Description: Oracle Health, the healthcare subsidiary of Oracle Corporation, experienced a data breach involving legacy Cerner data migration servers. This incident, which Oracle has communicated to its customers through private letters, is reported to have potentially exposed sensitive customer data. The breach is a consequence of Oracle's acquisition of Cerner Corp, a notable electronic health records business, as Oracle aimed to transition the healthcare software to cloud infrastructure. The significance of the data involved and the potential ramifications of such breaches in the healthcare sector underline the serious nature of this cybersecurity event.
Type: Data Breach
Title: Oracle Data Security Incidents
Description: Oracle faced two data security incidents with reported poor incident communication. An attacker allegedly accessed login servers and legacy Cerner data, leading to customers' personal information being at risk. Missteps in Oracle's response include outright denial, potentially misleading statements, and accusations of deleting evidence online, compounding the damage to their reputation.
Type: Data Breach
Attack Vector: Login Server AccessLegacy Cerner Data Access
Title: Oracle Corporation Gen 1 Servers Data Breach
Description: Oracle Corporation endured a data breach affecting its Gen 1 servers, with no complete PII exposure but involving 6 million data records including usernames, email addresses, and hashed passwords. Sensitive credentials related to SSO and LDAP were also compromised. The breach, attributed to the threat actor 'rose87168' via a 2020 Java exploit, resulted in the theft of JKS files and Enterprise Manager JPS keys from legacy systems approximately 16 months old. Oracle has informed clients and taken steps to bolster Gen 1 server security while maintaining that its Gen 2 servers and primary Oracle Cloud infrastructure remain secure.
Type: Data Breach
Attack Vector: 2020 Java Exploit
Vulnerability Exploited: Java Vulnerability
Threat Actor: rose87168
Title: Fidelity Investments Data Breach (2013) Affecting Oracle Corporation Employees
Description: The California Office of the Attorney General reported a data breach involving Fidelity Investments on July 31, 2013. The breach occurred on July 10, 2013, when an unauthorized individual accessed a report that included personal information of Oracle Corporation employees, such as names and Social Security numbers. The total number of individuals affected is unknown.
Date Detected: 2013-07-10
Date Publicly Disclosed: 2013-07-31
Type: Data Breach
Threat Actor: Unauthorized Individual
Title: Large-Scale Phishing Operation Targeting Hospitality Industry via Malvertising
Description: A sophisticated phishing campaign is targeting the hospitality industry through malicious search engine advertisements (malvertising). Cybercriminals impersonate at least thirteen hotel and vacation rental service providers (including Oracle Hospitality and Airbnb) to steal credentials and breach cloud-based property management systems. The operation employs typosquatted domains, fake login pages, and advanced tactics to bypass multi-factor authentication (MFA), including real-time capture of one-time passwords (OTP) and SMS/email codes. Technical analysis suggests Russian-speaking threat actors, with infrastructure leveraging Russian datacenter proxies and beaconing techniques for victim tracking. The campaign poses significant risks to guest data, payment information, and operational systems across the sector.
Type: phishing
Attack Vector: malicious advertisements (malvertising)typosquatted domainsfake login pagessocial engineering
Vulnerability Exploited: human trust in search engine adslack of phishing-resistant authenticationweak MFA implementations
Threat Actor: Russian-speaking cybercriminalsunknown APT/group (potential initial access brokers)
Motivation: financial gaindata theftfraud (e.g., unauthorized bookings)sale of credentials on dark web
Title: Extortion Campaign Targeting Oracle E-Business Suite Systems
Description: Mandiant and Google are tracking a new extortion campaign where executives at multiple companies received emails claiming that sensitive data was stolen from their Oracle E-Business Suite systems. The campaign began in late September 2025, with extortion emails sent from hundreds of compromised accounts, some linked to the FIN11 threat group (associated with Clop ransomware). The emails contain contact addresses listed on Clop's data leak site, but there is insufficient evidence to confirm if data was actually stolen. Organizations are advised to investigate their Oracle E-Business Suite environments for unusual access or compromise.
Date Detected: 2025-09-29
Date Publicly Disclosed: 2025-09-29
Type: Extortion
Attack Vector: Compromised Email AccountsPotential Zero-Day Exploitation (Oracle E-Business Suite)
Threat Actor: FIN11 (suspected)Clop Ransomware Gang (potential link)
Motivation: Financial Gain (Extortion)
Title: Clop Ransomware Gang Targets Oracle E-Business Suite in Extortion Campaign
Description: Hackers possibly connected to the Russian ransomware gang Clop (FIN11) are attempting to extort corporate executives by threatening to leak sensitive information allegedly stolen through Oracle's E-Business Suite. The campaign, tracked by Mandiant and Google Threat Intelligence Group (GTIG), involves extortion emails sent from compromised accounts, with claims of data theft from Oracle’s widely used business platform. The group has historically exploited vulnerabilities in file transfer tools (e.g., MOVEit, GoAnywhere) to steal and sell data for ransom. Investigations are ongoing, and the veracity of the claims remains unconfirmed.
Date Detected: 2023-09-29
Date Publicly Disclosed: 2023-10-04
Type: Data Breach
Attack Vector: Phishing/Spoofed EmailsExploitation of Vulnerabilities in Oracle E-Business SuiteCompromised Accounts
Threat Actor: Clop (FIN11)Potentially Impersonating Clop
Motivation: Financial Gain (Extortion/Ransom)
Title: Critical Zero-Day Exploit in Oracle E-Business Suite (CVE-2025-61882) Linked to Cl0p Ransomware Attacks
Description: Oracle released an emergency update to patch a critical zero-day vulnerability (CVE-2025-61882, CVSS 9.8) in its E-Business Suite, actively exploited by the Cl0p ransomware group in a high-volume data theft campaign. The flaw allows unauthenticated remote code execution via HTTP in the Oracle Concurrent Processing component. Indicators of compromise (IoCs) suggest involvement of the Scattered LAPSUS$ Hunters group, with evidence of exploit PoCs and malicious IP activity. Mandiant reported the campaign as part of a broader wave of attacks targeting Oracle EBS vulnerabilities, including those patched in July 2025 and the newly disclosed zero-day.
Date Detected: 2025-08
Date Publicly Disclosed: 2025-08
Type: Data Breach
Attack Vector: Network-based (HTTP)Unauthenticated Remote Code Execution
Vulnerability Exploited: CVE-2025-61882 (CVSS 9.8) - Oracle E-Business Suite Concurrent Processing Component
Threat Actor: Cl0p Ransomware GroupScattered LAPSUS$ Hunters
Motivation: Data TheftFinancial Gain (Ransomware)Exploitation of Zero-Day for Mass Compromise
Title: Oracle E-Business Suite Zero-Day Vulnerability Exploitation by Clop Hacking Group
Description: Oracle has patched a zero-day vulnerability (CVE-2025-61882) in its Oracle E-Business Suite, which the Clop hacking group is actively exploiting to steal personal information about corporate executives. The vulnerability allows exploitation over a network without authentication. Oracle urged customers to install the patch immediately, as thousands of organizations globally use the E-Business Suite for critical operations, including storing customer and HR data. The Clop group has been sending extortion emails to executives since late September 2025, demanding ransom payments to prevent the publication of stolen personal data. The exploitation campaign began in August 2025, following Oracle's July patches for previously identified vulnerabilities.
Date Detected: 2025-08-01
Date Publicly Disclosed: 2025-10-02
Type: Data Breach
Attack Vector: Network-based exploitation (no authentication required)Extortion emails
Vulnerability Exploited: CVE-2025-61882 (Zero-day in Oracle E-Business Suite)
Threat Actor: Clop (hacking group linked to ransomware and extortion)
Motivation: Financial gain (extortion)Data theft
Title: Clop Ransomware Exploits Oracle E-Business Suite Zero-Day (CVE-2025-61882) in Data Theft Attacks
Description: The Clop ransomware gang has been exploiting a critical Oracle E-Business Suite (EBS) zero-day bug (CVE-2025-61882) in data theft attacks since at least early August 2025. The vulnerability, patched by Oracle in early October 2025, resides in the BI Publisher Integration component of Oracle EBS's Concurrent Processing, allowing unauthenticated remote code execution (RCE) via a single HTTP request. Clop has been using this flaw to steal sensitive documents and extort victims via email campaigns. Other threat actors, including GRACEFUL SPIDER, may also be involved. Oracle has urged customers to patch immediately, as the public disclosure of the PoC exploit is expected to escalate attacks.
Date Detected: 2025-08-09
Date Publicly Disclosed: 2025-10-03
Type: Data Theft
Attack Vector: Unauthenticated Remote Code Execution (RCE)HTTP Request ExploitationEmail-Based Extortion
Vulnerability Exploited: CVE-2025-61882 (Oracle E-Business Suite BI Publisher Integration Component)
Threat Actor: Clop Ransomware GangGRACEFUL SPIDER (moderate confidence)
Motivation: Financial Gain (Extortion)Data Theft for Leverage
Title: Clop Extortion Gang Exploits Zero-Day in Oracle E-Business Suite to Steal Corporate Data
Description: Security researchers at Google reported that the Clop extortion gang exploited multiple security vulnerabilities, including a zero-day bug, in Oracle’s E-Business Suite software to steal significant amounts of data from dozens of organizations. The campaign, active since at least July 10, targeted corporate executives and involved extortion emails. Oracle initially claimed the vulnerabilities were patched in July, but later confirmed the zero-day could be exploited remotely without credentials. The Clop gang, linked to Russia, is known for mass-hacking campaigns exploiting unknown vulnerabilities in managed file transfer tools and enterprise software.
Date Detected: 2023-10-05T00:00:00Z
Date Publicly Disclosed: 2023-10-05T00:00:00Z
Type: Data Breach
Attack Vector: Exploitation of Zero-Day Vulnerability (CVE Unknown)Network-Based Attack (No Credentials Required)Extortion Emails
Vulnerability Exploited: Zero-Day in Oracle E-Business SuitePreviously Patched Vulnerabilities (Exploited Post-Patch)
Threat Actor: Clop Ransomware/Extortion Gang
Motivation: Financial Gain (Extortion)Data Theft for Dark Web Sale
Title: Oracle E-Business Suite Vulnerabilities (CVE-2025-61884 & CVE-2025-61882) Exploited in Extortion Campaigns
Description: Oracle issued emergency security updates to address critical vulnerabilities (CVE-2025-61884 and CVE-2025-61882) in its E-Business Suite (EBS). The flaws, exploitable remotely without authentication, were linked to extortion campaigns by the Cl0p ransomware group (FIN11). Attackers exploited these vulnerabilities to steal sensitive data, send extortion emails to executives, and potentially gain control of Oracle Concurrent Processing components. Oracle urged immediate patching to mitigate risks, while Google Mandiant and CrowdStrike attributed the attacks to Cl0p with moderate confidence. A proof-of-concept (POC) exploit was disclosed on October 3, 2025, increasing the likelihood of further exploitation by threat actors.
Date Detected: 2025-07-10
Date Publicly Disclosed: 2025-10-14
Type: Vulnerability Exploitation
Attack Vector: NetworkHTTPExploitation of Public-Facing Application
Vulnerability Exploited: CVE-2025-61884 (CVSS 7.5 - Information Disclosure in Runtime UI)CVE-2025-61882 (CVSS 9.8 - Remote Code Execution in BI Publisher Integration/Concurrent Processing)
Threat Actor: Cl0p Ransomware Group (Graceful Spider)FIN11Potential involvement of Scattered Spider, Slippy Spider (Lapsus$), ShinyHunters
Motivation: Financial GainData TheftExtortion
Title: ['Oracle E-Business Suite Remotely Exploitable Vulnerability (CVE-2025-61884)', 'Microsoft Zero-Day Exploits (CVE-2025-24990, CVE-2025-59230, CVE-2025-47827)', 'F5 Data Breach: Nation-State Attackers Stole BIG-IP Source Code', "Adobe Experience Manager 'Perfect' Vulnerability (CVE-2025-54253)", 'Microsoft Revokes 200 Certificates Used for Malicious Teams Installers (Vanilla Tempest Ransomware)', 'Cisco Zero-Day Rootkit Deployment on Network Switches (CVE-2025-20352)', 'U.S. Seizes $15B in Bitcoin Linked to Forced-Labor Crypto Scam', 'Unitree G1 Humanoid Robot Bluetooth Vulnerability (Espionage Risk)', 'Healthcare Cybersecurity Breakdown: 93% of U.S. Organizations Attacked (Patient Care Disruptions)']
Description: ['Oracle disclosed a remotely exploitable vulnerability (CVE-2025-61884) in its E-Business Suite, requiring immediate attention.', "Microsoft's October 2025 Patch Tuesday addressed 175+ vulnerabilities, including three zero-days (CVE-2025-24990, CVE-2025-59230, CVE-2025-47827) actively exploited by attackers.", 'F5 confirmed a breach where nation-state attackers stole source code and vulnerability details for its BIG-IP networking/security products.', 'CISA added CVE-2025-54253 (Adobe Experience Manager misconfiguration) to its Known Exploited Vulnerabilities catalog due to in-the-wild exploitation.', 'Microsoft revoked 200 software-signing certificates used by Vanilla Tempest ransomware group to distribute malicious Microsoft Teams installers.', 'Threat actors exploited CVE-2025-20352 (Cisco IOS/IOS XE) to deploy Linux rootkits on vulnerable network switches.', 'The U.S. government seized $15 billion in Bitcoin tied to a forced-labor crypto scam and human trafficking operation.', 'Alias Robotics revealed vulnerabilities in Unitree G1 humanoid robots, enabling Bluetooth hacks and data leaks to China.', 'Proofpoint reported 93% of U.S. healthcare organizations faced cyberattacks (avg. 43 incidents/organization), with 72% disrupting patient care.']
Date Detected: 2025-10-01 (Patch Tuesday)
Date Publicly Disclosed: 2025-10-01 (Patch Tuesday)
Date Resolved: [None, '2025-10-01 (Patches Released)', None, None, '2025-10-01 (Certificates Revoked)', None, '2025-10-01 (Seizure)', None, None]
Type: Vulnerability
Attack Vector: Remote ExploitationNation-State Cyber EspionageMisconfiguration ExploitationMalicious Software Signing CertificatesCVE-2025-20352 (IOS/IOS XE)Cryptocurrency Scam (Forced Labor)Bluetooth Exploitation
Vulnerability Exploited: CVE-2025-61884 (Oracle EBS)CVE-2025-54253 (AEM Misconfiguration)CVE-2025-20352 (Cisco IOS/IOS XE)Bluetooth Protocol Flaws
Threat Actor: Nation-State AttackersVanilla Tempest (Ransomware Group)Cryptocurrency Fraud Syndicate
Motivation: Cyber Espionage (Source Code Theft)Financial Gain (Ransomware)Financial Gain (Crypto Fraud)Espionage/Data Theft
Title: ['Salesloft/Drift OAuth Token Breach (2025)', 'New York Times GitHub Token Leak (2024)', 'Cloudflare Atlassian Compromise (2023)']
Description: ["In August 2025, hackers breached Salesloft's SaaS platform and stole OAuth access tokens for its Drift chatbot integration with Salesforce. By hijacking these tokens (which function as a trusted non-human identity between Drift and Salesforce), the attackers were able to impersonate the integration and access Salesforce CRM data at hundreds of organizations. Over a ten-day campaign, they used this backdoor to query and exfiltrate sensitive records, even pulling stored credentials like AWS keys and Snowflake tokens from support case attachments.", "In January 2024, the New York Times suffered a breach not through a phished password or zero-day exploit, but via an exposed GitHub API token. Attackers discovered a token credential for the Times' cloud code repository, which had inadvertently been made public, and used it to access about 270 GB of internal source code and data. This token acted as a non-human identity with broad privileges, allowing direct repository access without any interactive login.", "The fallout from the 2023 Okta breach revealed the danger of orphaned and unrotated service credentials. Cloudflare, an Okta customer, had rotated some 5,000 user credentials after the incident. However, an overlooked non-human account (an API token tied to a service account) remained active. Attackers leveraged that one leftover token (with its associated service credentials) to gain access to Cloudflare's Atlassian suite (Jira, Confluence, Bitbucket), effectively bypassing the human password reset effort."]
Date Detected: 2025-082024-012023
Date Resolved: [None, None, None]
Type: Data Breach (OAuth Token Compromise)
Attack Vector: Compromised OAuth Tokens (Non-Human Identity)Exposed GitHub API Token (Non-Human Identity)Orphaned API Token (Non-Human Identity)
Vulnerability Exploited: Overprivileged OAuth TokensPublicly Exposed API TokenUnrotated Service Account Token
Motivation: Data ExfiltrationData TheftUnauthorized Access
Title: Potential Cyberattack on UK's National Health Service (NHS) by Clop Extortion Crew
Description: The UK's National Health Service (NHS) is investigating claims of a cyberattack by the extortion crew Clop. The gang, known for targeting organizations using an Oracle E-Business Suite (EBS) exploit, listed the NHS on its leak site on November 11, 2023, but has not yet published any stolen data. The NHS has neither confirmed nor denied the intrusion, and its cybersecurity team is collaborating with the National Cyber Security Centre (NCSC) to investigate. Clop did not specify which branch of the NHS was compromised, and the NHS does not pay ransoms, making extortion unlikely to succeed. The attack highlights the NHS's vulnerability as a high-value target due to its vast sensitive patient data and critical life-saving systems.
Date Publicly Disclosed: 2023-11-11
Type: potential data breach
Attack Vector: exploit of Oracle E-Business Suite (EBS) vulnerability
Vulnerability Exploited: Oracle E-Business Suite (EBS) exploit (unspecified)
Threat Actor: Clop (extortion crew)
Motivation: financial extortiondata theft
Title: Clop Ransomware Exploits Zero-Day CVE-2025-61882 in Oracle E-Business Suite
Description: The Clop ransomware gang (Graceful Spider) breached Oracle Corporation's internal systems by exploiting a critical zero-day vulnerability (CVE-2025-61882) in Oracle E-Business Suite (EBS). The unauthenticated remote code execution (RCE) flaw allowed attackers to bypass authentication via the OA_HTML/SyncServlet endpoint and inject malicious XSLT templates via OA_HTML/RF.jsp, granting full control over ERP data. The attack, part of a broader supply chain campaign, targeted Oracle and other major entities like Mazda, Humana, and the Washington Post. Clop listed Oracle on its dark web leak site, threatening to release financial and personal records unless ransom demands were met. Evidence links the attack infrastructure to prior MOVEit exploits (CVE-2023-34362), with 96 distinct IPs identified, primarily hosted on Russian-based providers.
Date Detected: 2025-06
Date Publicly Disclosed: 2025-10
Type: Ransomware
Attack Vector: Unauthenticated Remote Code Execution (RCE)Authentication Bypass via SyncServletXSLT Injection via RF.jsp
Vulnerability Exploited: CVE-2025-61882 (Critical, CVSS 9.8)
Threat Actor: Clop Ransomware Gang (Graceful Spider)
Motivation: Financial GainData Extortion
Title: Clop Ransomware Gang Exploits Zero-Day Vulnerability in Oracle E-Business Suite (CVE-2025-61882)
Description: The Clop ransomware gang (Graceful Spider) claimed to have breached Oracle Corporation’s internal systems by exploiting a critical zero-day vulnerability (CVE-2025-61882) in Oracle E-Business Suite (EBS). The unauthenticated remote code execution (RCE) flaw, with a CVSS score of 9.8, was actively exploited since August 2025, two months before Oracle released a patch in October 2025. The attack leveraged the OA_HTML/SyncServlet endpoint for authentication bypass and malicious XSLT injection via OA_HTML/RF.jsp. Clop listed Oracle and high-profile customers (e.g., Mazda, Humana, Washington Post) on its dark web leak site, threatening data exposure unless ransom demands were met. Evidence suggests Oracle may have been compromised via its own unpatched EBS software, risking exposure of internal corporate and customer data.
Date Detected: 2025-08
Type: Ransomware Attack
Attack Vector: Unauthenticated Remote Code Execution (RCE)Authentication Bypass via SyncServletXSLT Injection via RF.jsp
Vulnerability Exploited: Cve Id: CVE-2025-61882, Affected Product: Oracle E-Business Suite (Versions 12.2.3 – 12.2.14), Vulnerability Type: Unauthenticated Remote Code Execution (RCE), Cvss Score: 9.8, Authentication BypassXSLT InjectionPatch Status: Patched in October 2025 (exploited since August 2025).
Threat Actor: Name: ['Clop Ransomware Gang', 'Graceful Spider']Origin: Russian-linkedConfirmed Victims: 1025Ransom Extracted: $500 million (since 2019)Associated Infrastructure: {'ip_addresses': 96, 'reused_ips_from_moveit': 41, 'geographic_distribution': [{'country': 'Germany', 'ip_count': 16}, {'country': 'Brazil', 'ip_count': 13}, {'country': 'Panama', 'ip_count': 12}], 'service_providers': ['Russian-based']}
Motivation: Financial GainData ExtortionReputation Damage
Title: The Silent Siege: Cox Enterprises’ Oracle Breach and the Shadowy World of Zero-Day Exploits
Description: Cox Enterprises, a U.S. conglomerate in telecommunications, media, and automotive services, suffered a data breach due to a zero-day exploit (CVE-2025-61882) in Oracle’s E-Business Suite. The breach, attributed to the Cl0p ransomware group, exposed sensitive personal data of 9,479 individuals, including names, addresses, dates of birth, Social Security numbers, and other identifiers. The incident occurred between August 9–14, 2025, but was detected in late September. Cl0p leaked 1.6 TB of stolen data on the dark web, and Cox offered affected parties free credit monitoring. The breach highlights vulnerabilities in ERP systems and the risks of delayed patching, with broader implications for supply chain security and regulatory compliance.
Date Detected: 2025-09-01T00:00:00Z
Date Publicly Disclosed: 2025-09-30T00:00:00Z
Type: Data Breach
Attack Vector: Zero-Day Exploit (CVE-2025-61882)Unauthenticated AccessMulti-Stage Java ImplantsData Exfiltration
Vulnerability Exploited: CVE-2025-61882 (Critical Authentication Bypass in Oracle E-Business Suite)
Threat Actor: Cl0p Ransomware Group (alleged)
Motivation: Financial GainData TheftExtortion
Title: Cl0p Exploits Zero-Day Vulnerabilities in Oracle E-Business Suite Leading to Massive Data Breaches
Description: The cybercriminal group Cl0p exploited two zero-day vulnerabilities (CVE-2025-61882 and CVE-2025-21884) in Oracle’s E-Business Suite (EBS), leading to data breaches in over 100 companies, including Broadcom, Estée Lauder, Mazda, and Canon. The group demanded significant ransom payments, threatening to leak or sell exfiltrated data if unpaid. Oracle issued security patches, but the attacks had already compromised sensitive corporate and customer data across multiple industries and geographies.
Date Detected: 2023-09-01
Date Publicly Disclosed: 2023-11-20
Type: Ransomware
Attack Vector: Zero-Day Exploit (CVE-2025-61882, CVE-2025-21884)Unauthenticated HTTP RequestsData Exfiltration
Threat Actor: Cl0p (Clop)
Motivation: Financial Gain (Ransomware Extortion)
Title: Parexel Data Breach Involving Sensitive Personal Information
Description: Parexel reported a data breach where sensitive personal identifiable information in its Oracle OCI E-Business Suite environment may have been compromised. An unauthorized third party accessed the data, leading to the exposure of personal and financial information of employees.
Date Detected: 2025-10-04
Date Publicly Disclosed: 2025-12-17
Type: Data Breach
Threat Actor: Unauthorized third party
Title: Clop Ransomware Gang Steals Data of 3.5 Million University of Phoenix Students and Staff
Description: The Clop ransomware gang has stolen the data of nearly 3.5 million University of Phoenix (UoPX) students, staff, and suppliers after breaching the university's network in August 2025. The attackers exploited a zero-day vulnerability in the Oracle E-Business Suite (EBS) financial application to steal sensitive personal and financial information.
Date Detected: 2025-11-21
Date Publicly Disclosed: 2025-12-01
Type: Data Breach, Ransomware
Attack Vector: Exploitation of zero-day vulnerability (CVE-2025-61882)
Vulnerability Exploited: CVE-2025-61882 (Oracle E-Business Suite)
Threat Actor: Clop ransomware gang
Motivation: Extortion, Data Theft
Title: University of Phoenix Data Breach
Description: In November 2025, University of Phoenix discovered a major data breach that may have affected millions of current and former students and staff. A vulnerability in Oracle E-Business Suite software was exploited by the CL0P ransomware group between Aug. 13 and Aug. 22, 2025, resulting in the exfiltration of sensitive data.
Date Detected: 2025-11-21
Date Publicly Disclosed: 2025-12-21
Type: Data Breach
Attack Vector: Exploitation of software vulnerability
Vulnerability Exploited: Oracle E-Business Suite software vulnerability
Threat Actor: CL0P ransomware group
Title: None
Description: Multiple high-profile cyber incidents affecting British businesses, charities, and government entities in 2025, including phishing attacks, digital shutdowns, and data breaches. Notable companies and organizations impacted include Marks and Spencer, Adidas, Co-op Group, Heathrow Airport, Harrods, Jaguar Land Rover (JLR), the German parliament, and the UK Foreign Office.
Type: phishing
Title: Multiple University Data Breaches Due to Social Engineering Attacks
Description: In the past two months, the University of Pennsylvania, Harvard University, and Princeton University have fallen victim to data breaches attributed to social engineering attacks, specifically phone-based phishing. Earlier in 2025, Columbia University, Dartmouth College, and New York University also experienced similar incidents. These breaches highlight vulnerabilities in higher education cybersecurity infrastructure.
Type: Data Breach
Attack Vector: Social Engineering (Phone-based Phishing)
Vulnerability Exploited: Human error, lack of centralized IT control, decentralized IT departments
Title: Oracle Discloses Critical Proxy Vulnerability in Fusion Middleware (CVE-2026-21962)
Description: Oracle has revealed a severe security flaw (CVE-2026-21962) in its Fusion Middleware suite, specifically affecting the Oracle HTTP Server and WebLogic Server Proxy Plug-in. The vulnerability, rated CVSS 10.0, enables unauthenticated remote attackers to exploit systems without user interaction, posing a major risk to enterprise environments. The flaw lies in how the WebLogic Server Proxy Plug-ins for Apache HTTP Server and Microsoft IIS process incoming requests. Due to its location in the proxy layer, attackers can bypass security controls entirely, gaining unauthorized access to sensitive data and the ability to create, delete, or modify system data. The vulnerability’s 'Scope Change' (S:C) metric indicates that successful exploitation could extend beyond the plug-in, potentially compromising backend WebLogic Server environments.
Type: Vulnerability Exploitation
Attack Vector: Remote
Vulnerability Exploited: CVE-2026-21962
Title: Ransomware in 2025: A Systemic Threat Disrupting Global Supply Chains and Critical Services
Description: In 2025, ransomware evolved from isolated IT disruptions into a systemic risk, threatening national supply chains, essential services, and entire industries. The top 10 ransomware attacks of 2025 exposed vulnerabilities across sectors, including SaaS supply chain blind spots, zero-day attacks, and sustained sieges on critical infrastructure.
Date Publicly Disclosed: 2025
Type: Ransomware
Attack Vector: Stolen credentialsSocial engineeringSupply chain vulnerabilities
Vulnerability Exploited: Zero-daySaaS supply chain blind spotsIT-OT convergence risks
Motivation: Financial gainExtortionOperational disruption
Title: Record-Breaking DDoS Attack by Aisuru/Kimwolf Botnet Peaks at 31.4 Tbps
Description: On December 19, Cloudflare mitigated a historic distributed denial-of-service (DDoS) attack launched by the Aisuru (also known as Kimwolf) botnet, reaching an unprecedented 31.4 Tbps and 200 million requests per second (rps). The campaign, dubbed 'The Night Before Christmas,' targeted telecommunications providers, IT organizations, and Cloudflare’s own infrastructure with hyper-volumetric HTTP and Layer 4 DDoS attacks.
Date Detected: 2024-12-19
Type: DDoS
Attack Vector: HTTP DDoSLayer 4 DDoS
Vulnerability Exploited: Compromised IoT devices and routers, primarily Android TVs
Threat Actor: Aisuru/Kimwolf Botnet
Title: University of Pennsylvania Data Breach
Description: A high-profile data breach at the University of Pennsylvania (Penn), initially alleged by anonymous hackers to have exposed records of 1.2 million students, donors, and alumni, was confirmed to have affected fewer than 10 individuals. The breach targeted systems linked to development and alumni activities, with hackers sending provocative emails falsely claiming poor security practices.
Date Detected: 2023-10-31
Type: Data Breach
Threat Actor: Anonymous Hackers
Title: SUNY Research Foundation Hit by Zero-Day Data Breach, Exposing Employee Personal Data
Description: The SUNY Research Foundation, based in Albany, New York, disclosed a data breach involving a zero-day vulnerability in Oracle’s eBusiness Suite. The attack occurred between August 9 and 11, with cybercriminals accessing personnel files containing sensitive employee information, including Social Security numbers. Oracle identified the flaw and released an urgent patch, but the breach went undetected until early October. Despite discovering the breach in October, the foundation only determined which files were accessed on November 26, nearly three months after the initial incident. Affected employees were notified last week, exceeding New York’s 30-day notification requirement for data breaches.
Date Detected: 2023-10-10
Type: Data Breach
Attack Vector: Zero-day vulnerability
Vulnerability Exploited: Zero-day vulnerability in Oracle’s eBusiness Suite
Title: Global Ransomware Attacks Surge 32% in 2025, With Manufacturing and U.S. Organizations Hit Hardest
Description: In 2025, global ransomware attacks reached 7,419 incidents, marking a 32% increase from 2024. Manufacturing saw the sharpest rise in attacks (56% to 1,466 incidents), with average ransom demands doubling to $1.2 million. The U.S. remained the most targeted country (3,810 attacks, 51% of global total). Notable breaches included Conduent (15.9M records), Episource (5.4M records), and University of Phoenix (3.49M records). Ransomware groups like Qilin, Akira, and SafePay were highly active, with Qilin responsible for 1,034 attacks.
Date Publicly Disclosed: 2025
Type: Ransomware
Vulnerability Exploited: Oracle zero-day vulnerability
Threat Actor: QilinAkiraSafePayClopInterlockDragonForce
Motivation: Financial gainData exfiltration
Title: TeamPCP Exploits Cloud Misconfigurations in Large-Scale Cybercrime Operation
Description: A threat actor known as TeamPCP (also operating under aliases like PCPcat and ShellForce) is conducting automated, worm-like attacks on misconfigured and exposed cloud management services, compromising at least 60,000 servers worldwide since late December. The group’s campaign primarily targets Azure (60% of attacks), AWS (37%), and Google and Oracle cloud environments, exploiting well-documented vulnerabilities and misconfigurations. TeamPCP deploys malicious Python and Shell scripts to install proxies, tunneling software, and persistence mechanisms, converting compromised infrastructure into a self-propagating botnet. The group monetizes its attacks through cryptocurrency mining, data theft and extortion, selling access to compromised systems, and ransomware deployment.
Date Detected: late December
Type: Cloud Misconfiguration Exploitation
Attack Vector: Exposed Docker APIsKubernetes clustersRay dashboardsLeaked secrets (.env files)React2Shell vulnerability (CVE-2025-29927)
Vulnerability Exploited: CVE-2025-29927 (React2Shell)Cloud misconfigurationsLeaked credentials
Threat Actor: TeamPCP (aka PCPcat, ShellForce)
Motivation: Financial gainData extortionCryptocurrency miningSelling access to compromised systems
Title: Anywhere Real Estate Hit by Clop Ransomware Attack, Exposing 17,429 Customers
Description: In August, Anywhere Real Estate disclosed a data breach affecting 17,429 customers, following an attack by the Clop ransomware gang. The cybercriminals infiltrated the company’s Oracle E-Business Suite environment, accessing and potentially exfiltrating sensitive customer data. A breach notification filed with the Maine Attorney General’s Office confirmed the incident, though details on the exact nature of the compromised information remain limited.
Date Publicly Disclosed: 2023-08
Type: Ransomware
Attack Vector: Vulnerability in enterprise software
Vulnerability Exploited: Oracle E-Business Suite
Threat Actor: Clop ransomware gang
Motivation: Extortion
Title: ShinyHunters Claims Breach of Wynn Resorts, Leaks 800K Employee Records
Description: The ransomware group ShinyHunters has allegedly breached Wynn Resorts, claiming to have stolen over 800,000 employee records and demanding 23.34 Bitcoin (≈$1.55 million) to delete the data. The group set a deadline of February 23, 2026, for payment, warning that failure to comply would result in the data being leaked on the dark web. A sample of the stolen data includes full names, emails, phone numbers, job positions, salaries, start dates, birth dates, and other personal details.
Date Detected: 2025-09
Type: Ransomware
Attack Vector: Exploiting Oracle PeopleSoft vulnerability via compromised employee credentials
Vulnerability Exploited: Oracle PeopleSoft vulnerability
Threat Actor: ShinyHunters
Motivation: Financial gain
Title: MSG Entertainment Data Breach Impacting Customer Personal Information
Description: MSG Entertainment is under investigation following a data breach discovered on December 16, 2025, that exposed sensitive customer information. The incident stemmed from a vulnerability in the Oracle eBusiness Suite, hosted by a third-party vendor, which was exploited by hackers as early as August 2025. The breach potentially compromised names, addresses, and Social Security numbers of affected individuals.
Date Detected: 2025-12-16
Type: Data Breach
Attack Vector: Third-party vendor vulnerability
Vulnerability Exploited: Oracle eBusiness Suite vulnerability
Title: MSGE Data Breach Exposes Personal Information of Over 131,000 Individuals
Description: Madison Square Garden Entertainment (MSGE) disclosed a cybersecurity incident affecting the personal data of more than 131,000 individuals. The breach involved unauthorized access to MSGE’s network, potentially compromising sensitive personally identifiable information (PII), including names, addresses, and Social Security numbers.
Date Publicly Disclosed: 2026-03-02
Type: Data Breach
Title: Maritz Holdings Inc. Suffers Data Breach via Oracle E-Business Suite Vulnerability
Description: Maritz Holdings Inc., a Missouri-based management consulting firm, disclosed a data breach stemming from an exploited vulnerability in Oracle E-Business Suite (EBS). The CL0P ransomware group claimed responsibility for the attack, leading to the exposure of sensitive data, including names, Social Security numbers, and financial account information.
Date Detected: 2025-11-13
Date Publicly Disclosed: 2026-02-27
Type: Data Breach
Attack Vector: Exploited vulnerability in Oracle E-Business Suite
Vulnerability Exploited: Oracle E-Business Suite (EBS) vulnerability
Threat Actor: CL0P ransomware group
Title: DHS and ICE Contractor Data Breach Exposes Thousands of Entities
Description: A recent cybersecurity breach targeting the U.S. Department of Homeland Security’s (DHS) Office of Industry Partnership has exposed sensitive contract details involving over 6,600 organizations. The leaked data includes comprehensive records of companies, government agencies, and universities that applied for or secured contracts with DHS and Immigration and Customs Enforcement (ICE). The breach was claimed by the hacking collective *Department of Peace*, motivated by opposition to DHS and ICE’s immigration enforcement policies.
Type: Data Breach
Threat Actor: Department of Peace
Motivation: Opposition to DHS and ICE’s immigration enforcement policies
Title: Michelin Data Breach in Cl0p’s Oracle EBS Cyberattack Campaign
Description: Tire manufacturer Michelin confirmed a data breach linked to the ongoing cybercrime campaign targeting organizations using Oracle’s E-Business Suite (EBS). The Cl0p ransomware and extortion group exploited zero-day vulnerabilities in Oracle EBS to access sensitive data from over 100 organizations, including Michelin. Cl0p published over 315GB of allegedly stolen files on its leak site, with metadata suggesting the data originated from an Oracle EBS environment.
Type: Data Breach
Attack Vector: Exploitation of zero-day vulnerability in Oracle EBS
Vulnerability Exploited: Oracle EBS zero-day flaw
Threat Actor: Cl0p (FIN11)
Motivation: Extortion
Title: Alleged Massive Data Breach at Loblaw
Description: A threat actor operating under the handle 'igotafeeling' on the DarkWeb Informer forum has claimed to have breached Loblaw, Canada’s largest food and pharmacy retailer. The actor alleges possession of over 1.8 billion records, including customer data, pharmacy records, payment details, and source code. Loblaw has labeled the incident a 'low-level data breach' and denied evidence of financial or credit card data compromise.
Date Publicly Disclosed: 2024-03-12
Type: Data Breach
Threat Actor: igotafeeling
Motivation: Extortion (response demanded by March 19)
Title: Hypertherm, Inc. Data Breach Exposes Sensitive Data in 2025 Oracle EBS Hack
Description: Hypertherm, Inc., a manufacturer of industrial cutting products for sectors including shipbuilding, automotive repair, and manufacturing, confirmed a data breach affecting its Oracle E-Business Suite (EBS) systems. The incident stemmed from an unauthorized intrusion in August 2025, during which an attacker exfiltrated database tables containing sensitive information. The breach has drawn legal scrutiny, with Edelson Lechtzin LLP investigating potential claims on behalf of impacted parties.
Date Detected: 2026-02-12
Date Publicly Disclosed: 2026-03-13
Type: Data Breach
Attack Vector: Unauthorized Intrusion
Vulnerability Exploited: Oracle E-Business Suite (EBS) Vulnerability
Title: Hypertherm Data Breach Impacting U.S. Employees After Oracle EBS Exploit
Description: Hypertherm, an employee-owned manufacturer of industrial cutting systems, reported a data breach exposing personal information due to a vulnerability in Oracle’s E-Business Suite (EBS) software. The breach compromised names and Social Security numbers of affected individuals.
Date Detected: 2026-02-10
Date Publicly Disclosed: 2026-03-13
Type: Data Breach
Attack Vector: Exploitation of unknown vulnerability in Oracle EBS
Vulnerability Exploited: Unknown flaw in Oracle E-Business Suite (EBS)
Threat Actor: CL0P
Motivation: Ransomware
Title: Oracle E-Business Suite Hack Leaves Four Major Companies Silent on Impact
Description: A recent cyberattack targeting Oracle E-Business Suite (EBS) has disrupted organizations reliant on the platform for critical business operations, including finance, supply chain, HR, and procurement. While many companies have responded with public disclosures and mitigation efforts, Broadcom, Bechtel, Estée Lauder, and Abbott Technologies have yet to issue any statements, raising concerns about transparency and crisis management. The breach exposes vulnerabilities in a widely used enterprise software suite, threatening the integrity of sensitive corporate and customer data.
Type: Cyberattack
Vulnerability Exploited: Oracle E-Business Suite vulnerabilities
Title: Wits University Zero-Day Cyberattack
Description: Wits University in South Africa has confirmed a cyberattack targeting its IT systems, classified as a zero-day exploit leveraging an unknown vulnerability with no available patch at the time of the incident. The attack has affected organizations across multiple countries, prompting collaboration with Oracle and cybersecurity experts to assess data compromise.
Type: Zero-Day Exploit
Vulnerability Exploited: Unknown vulnerability (zero-day)
Title: Oracle Critical RCE Flaw in Identity and Web Services Manager (CVE-2026-21992)
Description: Oracle has released an urgent security alert for a critical Remote Code Execution (RCE) vulnerability, tracked as CVE-2026-21992, affecting Oracle Identity Manager and Oracle Web Services Manager. The flaw allows unauthenticated attackers to remotely compromise systems by sending specially crafted network packets, enabling arbitrary code execution on vulnerable servers. Exploitation could grant threat actors deep system access, allowing them to deploy malware, steal sensitive corporate identity data, or move laterally within an enterprise network.
Type: Remote Code Execution (RCE)
Attack Vector: Network packets
Vulnerability Exploited: CVE-2026-21992
Common Attack Types: The most common types of attacks the company has faced is Breach.
Identification of Attack Vectors: The company identifies the attack vectors used in incidents through CVE-2021-35587, malvertising (malicious search engine ads)typosquatted domains, Compromised Email Accounts, Compromised Email AccountsPotential Exploitation of Oracle E-Business Suite Vulnerabilities, Oracle E-Business Suite Concurrent Processing Component (via HTTP), CVE-2025-61882 (Oracle E-Business Suite zero-day), CVE-2025-61882 (Oracle EBS BI Publisher), Zero-Day Vulnerability in Oracle E-Business Suite (Network-Based, No Authentication Required), Exploitation of Oracle EBS Vulnerabilities (CVE-2025-61882, CVE-2025-61884)Hacked User EmailsDefault Password Reset Mechanisms, Misconfigured AEM JEECompromised Software Signing CertificatesCVE-2025-20352 (IOS/IOS XE)Phishing/Social Engineering (Forced Labor Scam)Bluetooth Interface, Compromised OAuth tokens (Drift-Salesforce integration)Exposed GitHub API token (public repository)Orphaned API token (Okta service account), potential Oracle E-Business Suite (EBS) exploit, OA_HTML/SyncServlet (Authentication Bypass) & OA_HTML/RF.jsp (XSLT Injection), Oracle E-Business Suite (EBS) SyncServlet endpoint, Zero-day exploit (CVE-2025-61882) in Oracle E-Business Suite, Zero-day vulnerabilities in Oracle EBS (CVE-2025-61882, CVE-2025-21884), Oracle E-Business Suite (EBS) zero-day vulnerability (CVE-2025-61882), Phone-based phishing (social engineering), Stolen credentialsSocial engineering, Exposed Docker APIsKubernetes clustersRay dashboardsLeaked secrets, Compromised employee credentials, Oracle EBS zero-day vulnerability and Oracle EBS vulnerability.

Data Compromised: Credit card payment information
Systems Affected: MICROS Point-of-Sale Systems
Payment Information Risk: True

Data Compromised: Sso passwords, Java keystore files, Key files, Jps keys
Systems Affected: Oracle Cloud SSO login servers
Brand Reputation Impact: Potential undermining of trust in Oracle's cloud security

Data Compromised: Jks files, Encrypted sso passwords, Key files, Jps keys

Data Compromised: Electronic health records (ehr)
Systems Affected: Legacy Servers
Legal Liabilities: Potential HIPAA violations

Systems Affected: legacy Cerner data migration servers

Data Compromised: Personal Information
Systems Affected: Login ServersLegacy Cerner Data
Brand Reputation Impact: Damaged Reputation

Data Compromised: Usernames, Email addresses, Hashed passwords, Sso credentials, Ldap credentials, Jks files, Enterprise manager jps keys
Systems Affected: Gen 1 serverslegacy systems

Data Compromised: Names, Social security numbers
Identity Theft Risk: High (PII exposed)

Data Compromised: Guest personal information, Payment data, Booking system credentials, Operational data
Systems Affected: cloud-based property management systemsguest messaging platformsauthentication systems
Operational Impact: potential unauthorized access to booking systemsreputation damagecustomer trust erosion
Brand Reputation Impact: high (due to impersonation of major brands like Oracle Hospitality and Airbnb)
Identity Theft Risk: ['high (guest PII and payment data exposed)']
Payment Information Risk: ['high (credit card details and transaction data at risk)']

Systems Affected: Oracle E-Business Suite (potential)
Brand Reputation Impact: Potential (due to extortion claims)

Data Compromised: Potentially finance, hr, and supply chain data (oracle e-business suite)
Systems Affected: Oracle E-Business Suite
Brand Reputation Impact: High (Potential Reputation Damage Due to Extortion Threats)
Identity Theft Risk: Potential (If PII Stolen)

Data Compromised: Large amounts of data (exact scope undisclosed)
Systems Affected: Oracle E-Business Suite (Concurrent Processing Component)
Brand Reputation Impact: High (due to zero-day exploitation and association with Cl0p ransomware)
Identity Theft Risk: Potential (depends on stolen data types)

Data Compromised: Personal information of corporate executives, Customer data, Employee hr files
Systems Affected: Oracle E-Business Suite
Brand Reputation Impact: High (extortion campaign targeting executives, potential data leaks)
Identity Theft Risk: High (personal information of executives targeted)

Data Compromised: Sensitive documents, Potentially pii or corporate data
Systems Affected: Oracle E-Business Suite (EBS) with unpatched BI Publisher Integration
Brand Reputation Impact: High (due to extortion and potential data leaks)
Identity Theft Risk: ['Potential (if PII was stolen)']

Data Compromised: Corporate executive data, Customer data, Employee hr files, Sensitive corporate data
Systems Affected: Oracle E-Business Suite
Brand Reputation Impact: High (Associated with Mass Hacking Campaign)
Identity Theft Risk: High (Personal Information of Executives Compromised)

Data Compromised: Sensitive resources, Potential oracle e-business suite data (as claimed in extortion emails)
Systems Affected: Oracle E-Business Suite (Versions 12.2.3–12.2.14)Runtime UI ComponentBI Publisher IntegrationConcurrent Processing Component
Operational Impact: Potential Disruption Due to Unauthorized AccessEmergency Patching Requirements
Brand Reputation Impact: Potential Reputation Damage Due to Data Theft Claims and Extortion Campaigns
Identity Theft Risk: ['High (Due to Potential Exposure of Sensitive Data)']

Financial Loss: $15 billion (Seized)
Data Compromised: Big-ip source code & vulnerability info, Robot sensor/data leaks
Systems Affected: Oracle E-Business SuiteMicrosoft Products (Multiple)F5 BIG-IP Networking/Security ProductsAdobe Experience Manager (JEE)Microsoft Teams (Malicious Installers)Cisco Network Switches (IOS/IOS XE)Cryptocurrency Wallets/ExchangesUnitree G1 Humanoid Robots
Downtime: [None, None, None, None, None, None, None, None, 'Patient Care Disruptions (72% of Incidents)']
Operational Impact: Source Code Integrity RiskMalware Distribution InfrastructureNetwork Compromise (Rootkits)Fraud Operation ShutdownEspionage Risk (China-Linked)
Conversion Rate Impact: [None, None, None, None, None, None, None, None, None]
Revenue Loss: [None, None, None, None, None, None, None, None, None]
Customer Complaints: [None, None, None, None, None, None, None, None, 'High (Healthcare)']
Brand Reputation Impact: High (F5)High (Microsoft)High (Cisco)Severe (Crypto Scam)High (Unitree/Alias Robotics)Severe (Healthcare Sector)
Legal Liabilities: Criminal Charges (Forced Labor)HIPAA/Regulatory Violations
Identity Theft Risk: [None, None, None, None, None, None, None, None, 'High (Patient Data)']
Payment Information Risk: [None, None, None, None, None, None, 'High', None, None]

Data Compromised: Salesforce crm data (including aws keys and snowflake tokens from support case attachments), 270 gb of internal source code and data, Access to cloudflare's atlassian suite (jira, confluence, bitbucket)
Systems Affected: Salesforce CRM (via Drift integration)GitHub (New York Times' cloud code repository)Atlassian Suite (Jira, Confluence, Bitbucket)
Downtime: [None, None, None]
Operational Impact: Unauthorized access to CRM data across hundreds of organizationsExposure of internal source code and proprietary dataBypass of human password reset efforts, enabling stealthy backdoor access
Conversion Rate Impact: [None, None, None]
Revenue Loss: [None, None, None]
Customer Complaints: [None, None, None]
Brand Reputation Impact: Potential reputational damage due to unauthorized CRM data accessReputational risk from exposure of internal source codeReputational impact from unauthorized access to Atlassian suite
Identity Theft Risk: ['High (AWS keys and Snowflake tokens exposed)', 'Moderate (internal credentials potentially exposed in source code)', 'Moderate (potential access to sensitive Atlassian data)']
Payment Information Risk: [None, None, None]

Brand Reputation Impact: potential reputational harm due to public disclosure of attack claims
Identity Theft Risk: high (if patient data was accessed, given NHS stores vast quantities of sensitive data)

Data Compromised: Financial records, Personal records, Erp data
Systems Affected: Oracle E-Business Suite (Versions 12.2.3–12.2.14)Internal Corporate Systems
Operational Impact: Potential disruption to order management, procurement, and logistics functions
Brand Reputation Impact: High (public listing on dark web leak site)
Identity Theft Risk: High (personal records exposed)

Data Compromised: Internal corporate data, Customer information, Financial records, Personal data
Systems Affected: Oracle E-Business Suite (EBS) ServersEnterprise Resource Planning (ERP) Systems
Operational Impact: Potential disruption to order management, procurement, and logistics
Brand Reputation Impact: High (public listing on dark web leak site)
Identity Theft Risk: ['High (PII exposure risk)']

Data Compromised: Names, Addresses, Dates of birth, Social security numbers, Personal identifiers, Internal documents, Employee records, Customer details
Systems Affected: Oracle E-Business SuiteERP SystemsDatabases
Operational Impact: Potential disruption to HR, financial, and supply chain operations
Brand Reputation Impact: High (potential erosion of customer trust, regulatory scrutiny)
Legal Liabilities: Potential lawsuits (e.g., Bloomberg Law report on Oracle’s liability)Regulatory fines under GDPR/CCPA
Identity Theft Risk: High (9,479 individuals affected)

Systems Affected: Oracle E-Business Suite (EBS) versions 12.2.3–12.2.14
Operational Impact: Significant (data exfiltration, potential system compromise)
Brand Reputation Impact: High (public disclosure of breaches, ransom demands)
Identity Theft Risk: High (PII and sensitive corporate data exfiltrated)

Data Compromised: Sensitive personal identifiable information
Systems Affected: Oracle OCI E-Business Suite (Oracle EBS)
Identity Theft Risk: High
Payment Information Risk: High

Data Compromised: 3,489,274 records
Systems Affected: Oracle E-Business Suite (EBS) financial application
Brand Reputation Impact: Yes
Legal Liabilities: Potential regulatory fines and legal actions
Identity Theft Risk: Yes
Payment Information Risk: Yes

Data Compromised: Sensitive personally identifiable information
Systems Affected: Oracle E-Business Suite
Identity Theft Risk: High
Payment Information Risk: High

Financial Loss: hundreds of millions of pounds
Operational Impact: digital shutdown

Data Compromised: Personal data of students, faculty, and staff
Systems Affected: Internal university systems
Operational Impact: Disruption of university operations, increased security protocols
Brand Reputation Impact: Reputational damage to affected universities
Identity Theft Risk: High (potential exposure of personally identifiable information)

Data Compromised: Sensitive data
Systems Affected: Oracle HTTP Server, WebLogic Server Proxy Plug-in
Operational Impact: Unauthorized creation, deletion, or modification of system data

Financial Loss: $275 billion annually by 2031 (projected global cost)
Systems Affected: SaaS platformsIT distribution networksHealthcare infrastructureManufacturing OT systemsAviation systems
Downtime: True
Operational Impact: Crippling automotive operationsParalyzing global IT distributionHealthcare disruption with confirmed patient harmManufacturing haltsGrounding of European airports
Revenue Loss: True

Systems Affected: Telecommunications providersIT organizationsCloudflare infrastructure
Operational Impact: Automated mitigation without triggering internal alerts

Data Compromised: Personal data of fewer than 10 individuals
Systems Affected: Development and alumni activities systems
Brand Reputation Impact: Provocative emails falsely claiming poor security practices
Legal Liabilities: 18 proposed class-action lawsuits (consolidated into one)

Data Compromised: Personnel files containing sensitive employee information, including Social Security numbers
Systems Affected: Oracle’s eBusiness Suite
Legal Liabilities: Potential violation of New York’s 30-day notification requirement for data breaches
Identity Theft Risk: High (Social Security numbers exposed)

Financial Loss: £206 million ($276 million) in lost revenue (Co-operative Group)$276 million (Co-operative Group)
Data Compromised: 59.2 million records (confirmed), 31.2 petabytes (Qilin)
Revenue Loss: ['£206 million ($276 million) (Co-operative Group)']

Data Compromised: Over two million records (personal IDs, employment records, résumés)
Systems Affected: 60,000+ servers worldwide
Operational Impact: Compromised infrastructure converted into a botnet for further attacks
Identity Theft Risk: High (personal and professional data used for phishing, impersonation, or account takeovers)

Data Compromised: Sensitive customer data
Systems Affected: Oracle E-Business Suite
Identity Theft Risk: Potential

Data Compromised: 800,000 employee records
Identity Theft Risk: High

Data Compromised: Names, addresses, Social Security numbers
Systems Affected: Oracle eBusiness Suite (third-party hosted)
Legal Liabilities: Potential class action investigation
Identity Theft Risk: High

Data Compromised: Personal Identifiable Information (PII)
Identity Theft Risk: High

Data Compromised: Sensitive data, including names, Social Security numbers, and financial account information
Systems Affected: Oracle E-Business Suite (EBS)
Legal Liabilities: Potential compensation claims
Identity Theft Risk: High
Payment Information Risk: High

Data Compromised: Sensitive contract details, company names, URLs, employee details, addresses, tax ID numbers, government contractor identifiers, internal DHS staff comments, awarded contracts
Brand Reputation Impact: Potential reputational damage to affected entities
Identity Theft Risk: High (exposure of SSNs, EINs, and personal details)

Data Compromised: 315GB of files
Systems Affected: Oracle EBS environment
Operational Impact: None (global operations unaffected)

Data Compromised: Over 1.8 billion records allegedly exposed
Systems Affected: SalesforceShoppers Drug Mart systemsGitLab projectsOracle identity systemsE-commerce platforms
Brand Reputation Impact: Potential significant impact if claims are verified
Identity Theft Risk: High (health card numbers, prescription IDs, PII)
Payment Information Risk: High (full credit card numbers with expiry dates)

Data Compromised: Sensitive information, database tables
Systems Affected: Oracle E-Business Suite (EBS)
Legal Liabilities: Potential class action investigation

Data Compromised: Names, Social Security numbers
Systems Affected: Oracle E-Business Suite (EBS)
Identity Theft Risk: High

Data Compromised: Sensitive corporate and customer data
Systems Affected: Finance, supply chain, HR, and procurement systems
Operational Impact: Disruption of critical business operations
Brand Reputation Impact: Potential long-term reputational damage

Systems Affected: Some IT systems compromised
Operational Impact: Operations continue as normal

Data Compromised: Sensitive corporate identity data
Systems Affected: Oracle Identity Manager, Oracle Web Services Manager
Operational Impact: Lateral movement within enterprise network, malware deployment
Identity Theft Risk: High
Average Financial Loss: The average financial loss per incident is $5.74 billion.
Commonly Compromised Data Types: The types of data most commonly compromised in incidents are Credit Card Payment Information, , Sso Passwords, Java Keystore Files, Key Files, Jps Keys, , Jks Files, Encrypted Sso Passwords, Key Files, Jps Keys, , Electronic Health Records (Ehr), , Sensitive Customer Data, , Personal Information, Usernames, Email Addresses, Hashed Passwords, Sso Credentials, Ldap Credentials, Jks Files, Enterprise Manager Jps Keys, , Personally Identifiable Information (Pii), , Credentials (Usernames, Passwords), Pii (Email Addresses, Phone Numbers), Guest Data, Payment Information, Booking Details, , Potentially Finance, Hr, Supply Chain Data, Client Credentials (From January Incident), , Personal Information (Executives), Customer Data, Employee Hr Files, , Sensitive Corporate Documents, Potentially Pii, , Personally Identifiable Information (Pii) Of Executives, Customer Data, Employee Hr Files, Corporate Sensitive Data, , Sensitive Resources, Potentially Oracle Ebs Data (As Per Extortion Claims), , Source Code & Vulnerability Details, Robot Sensor Data, , Crm Data (Salesforce), Aws Keys, Snowflake Tokens, Internal Source Code (270 Gb), Proprietary Data, Atlassian Suite Data (Jira, Confluence, Bitbucket), , Financial Records, Personal Records, Erp Data, , Corporate Internal Data, Customer Information, Financial Records, Personal Data, , Pii (Personally Identifiable Information), Internal Documents, Employee Records, Customer Details, , Corporate Data, Customer Data, Sensitive Business Information, , Name, Social Security Number, Date Of Birth, Financial Account Number, Payment Card Number (Without Cvv), National Id Number, , Personal Information, Financial Information, , Names, Dates Of Birth, Social Security Numbers, Bank Account Numbers, Bank Routing Numbers, , Personal data, potentially including personally identifiable information, Sensitive data, Personal data, Personnel files, Social Security numbers, Personally Identifiable Information, Corporate Data, , Personal Ids, Employment Records, Résumés, , Sensitive customer data, Full Names, Emails, Phone Numbers, Job Positions, Salaries, Start Dates, Birth Dates, Other Personal Details, , Personal Information, Personally Identifiable Information (PII), Names, Social Security Numbers, Financial Account Information, , Contract details, company information, employee details, tax ID numbers, government identifiers, internal comments, awarded contracts, Files (unspecified), Customer Records (Names, Emails, Phone Numbers, Addresses, Loyalty Ids), Health Card Numbers, Pharmacy Fill Requests (Prescription Numbers, Patient Ids), Payment Details (Full Credit Card Numbers With Expiry Dates, Bins, Last-Four Digits), Source Code (Gitlab Projects), Mfa Device Details And Credentials (Oracle Identity Records), Marketing And Email Records, , Sensitive information, database tables, Personally Identifiable Information (PII), Sensitive corporate and customer data and Corporate identity data.

Entity Name: Oracle Cloud
Entity Type: Cloud Service Provider
Industry: Technology
Customers Affected: 140,000 tenants

Entity Name: Oracle Health
Entity Type: Healthcare Technology Company
Industry: Healthcare
Location: United States
Customers Affected: Multiple US healthcare organizations and hospitals

Entity Name: Oracle Health
Entity Type: Company
Industry: Healthcare

Entity Name: Oracle Corporation
Entity Type: Corporation
Industry: Technology

Entity Name: Fidelity Investments
Entity Type: Financial Services
Industry: Investment Management
Location: United States

Entity Name: Oracle Corporation
Entity Type: Corporation
Industry: Technology
Location: United States
Customers Affected: Unknown (employees affected)

Entity Name: Oracle Hospitality
Entity Type: technology provider
Industry: hospitality
Location: global
Size: large enterprise

Entity Name: Airbnb
Entity Type: vacation rental platform
Industry: hospitality
Location: global
Size: large enterprise

Entity Name: Unnamed hotel and vacation rental providers (11+ others)
Entity Type: hotel chains, property management companies, vacation rental services
Industry: hospitality
Location: global

Entity Type: Multiple Companies (Executives Targeted)

Entity Name: Oracle (Primary Target)
Entity Type: Corporation
Industry: Technology/Enterprise Software
Location: Global (HQ: Redwood Shores, California, USA)
Size: Large (Fortune 100)
Customers Affected: Numerous Organizations (Exact Number Undisclosed)

Entity Name: Oracle Corporation
Entity Type: Technology Vendor
Industry: Enterprise Software
Location: Global (HQ: Redwood City, California, USA)
Size: Large (Multinational)
Customers Affected: Multiple (exact number undisclosed)

Entity Name: Oracle Corporation
Entity Type: Technology Company
Industry: Enterprise Software
Location: Global (HQ: Redwood Shores, California, USA)
Size: Large (thousands of organizations use Oracle E-Business Suite)
Customers Affected: Multiple (exact number unspecified, includes corporate executives)

Entity Name: Multiple Organizations Using Oracle E-Business Suite
Entity Type: Corporations, Enterprises
Location: Global (targeting internet-exposed EBS applications)

Entity Name: Oracle Corporation
Entity Type: Software Vendor
Industry: Technology
Location: Redwood City, California, USA
Size: Large Enterprise
Customers Affected: Dozens of Organizations (Exact Number Undisclosed)

Entity Name: Oracle Corporation
Entity Type: Software Vendor
Industry: Technology
Location: Global (HQ: Redwood City, California, USA)
Size: Large Enterprise
Customers Affected: Multiple (Exact Number Unspecified)

Entity Name: Unspecified Organizations Using Oracle E-Business Suite
Entity Type: Enterprises, Government Agencies, Potential High-Value Targets
Location: Global

Entity Name: Oracle
Entity Type: Corporation
Industry: Enterprise Software
Location: USA
Size: Large

Entity Name: Microsoft
Entity Type: Corporation
Industry: Technology
Location: USA
Size: Large
Customers Affected: Global (Windows/Teams Users)

Entity Name: F5
Entity Type: Corporation
Industry: Networking/Security
Location: USA
Size: Large
Customers Affected: BIG-IP Customers

Entity Name: Adobe
Entity Type: Corporation
Industry: Software
Location: USA
Size: Large
Customers Affected: Experience Manager Users

Entity Name: Multiple Organizations
Entity Type: Corporations/Institutions
Industry: Cross-Sector
Location: Global
Size: Varies
Customers Affected: Vanilla Tempest Targets

Entity Name: Cisco Customers
Entity Type: Corporations/Governments
Industry: Networking
Location: Global
Size: Varies
Customers Affected: IOS/IOS XE Users

Entity Name: Unnamed Crypto Scam Victims
Entity Type: Individuals/Institutions
Industry: Finance
Location: Global
Customers Affected: $15B in Bitcoin Seized

Entity Name: Unitree Robotics
Entity Type: Corporation
Industry: Robotics
Location: China
Size: Medium
Customers Affected: G1 Robot Owners

Entity Name: U.S. Healthcare Organizations
Entity Type: Hospitals/Clinics
Industry: Healthcare
Location: USA
Size: Varies (93% of orgs)
Customers Affected: Patients (72% Disrupted)

Entity Name: Salesloft
Entity Type: SaaS Platform
Industry: Sales Engagement/CRM
Customers Affected: Hundreds of organizations (via Salesforce CRM access)

Entity Name: Drift
Entity Type: Chatbot Integration
Industry: Conversational Marketing

Entity Name: Salesforce (via Drift integration)
Entity Type: CRM Platform
Industry: Customer Relationship Management
Customers Affected: Hundreds of organizations

Entity Name: The New York Times
Entity Type: Media Organization
Industry: News/Publishing
Location: New York, USA

Entity Name: GitHub (New York Times' repository)
Entity Type: Code Hosting Platform
Industry: Software Development

Entity Name: Cloudflare
Entity Type: Web Infrastructure/Security
Industry: Cybersecurity/CDN

Entity Name: Atlassian (Jira, Confluence, Bitbucket)
Entity Type: Collaboration/DevOps Tools
Industry: Software Development

Entity Name: UK National Health Service (NHS)
Entity Type: public healthcare system
Industry: healthcare
Location: United Kingdom
Size: large (largest employer in Europe)

Entity Name: Oracle Corporation
Entity Type: Technology Vendor
Industry: Enterprise Software
Location: United States
Size: Large (Multinational)

Entity Name: MAZDA.COM
Entity Type: Corporate
Industry: Automotive

Entity Name: HUMANA.COM
Entity Type: Corporate
Industry: Healthcare Insurance

Entity Name: Washington Post
Entity Type: Media
Industry: News/Publishing

Entity Name: Oracle Corporation
Entity Type: Technology Vendor
Industry: Enterprise Software
Location: Global (HQ: Redwood City, California, USA)
Size: Large (Multinational)
Customers Affected: Potentially high (internal systems + customers using EBS)

Entity Name: Mazda
Entity Type: Corporation
Industry: Automotive
Location: Global

Entity Name: Humana
Entity Type: Corporation
Industry: Healthcare Insurance
Location: USA

Entity Name: The Washington Post
Entity Type: Media Organization
Industry: News/Publishing
Location: USA

Entity Name: Cox Enterprises
Entity Type: Conglomerate
Industry: Telecommunications, Media, Automotive Services
Location: United States
Size: 55,000+ employees, $23B+ annual revenue
Customers Affected: 9,479 individuals

Entity Name: Oracle
Entity Type: Corporation
Industry: Technology (Enterprise Software)
Location: United States
Size: Large (Fortune 500)

Entity Name: Broadcom
Entity Type: Corporation
Industry: Semiconductors/Technology
Location: United States
Size: Large (Fortune 500)

Entity Name: Estée Lauder Companies
Entity Type: Corporation
Industry: Cosmetics/Retail
Location: United States
Size: Large (Fortune 500)

Entity Name: Mazda
Entity Type: Corporation
Industry: Automotive
Location: Japan
Size: Large

Entity Name: Canon
Entity Type: Corporation
Industry: Technology/Imaging
Location: Japan
Size: Large

Entity Name: Michelin
Entity Type: Corporation
Industry: Automotive/Tires
Location: France
Size: Large

Entity Name: Humana
Entity Type: Corporation
Industry: Healthcare/Insurance
Location: United States
Size: Large (Fortune 500)

Entity Name: Fruit of the Loom
Entity Type: Corporation
Industry: Apparel
Location: United States
Size: Large

Entity Name: Abbott Laboratories
Entity Type: Corporation
Industry: Healthcare/Pharmaceuticals
Location: United States
Size: Large (Fortune 500)

Entity Name: Grupo Bimbo
Entity Type: Corporation
Industry: Food/Baking
Location: Mexico
Size: Large

Entity Name: A10 Networks
Entity Type: Corporation
Industry: Technology/Networking
Location: United States
Size: Mid-Large

Entity Name: Envoy
Entity Type: Corporation
Industry: Technology/Workplace Solutions
Location: United States
Size: Mid-Large

Entity Name: Greater Cleveland RTA
Entity Type: Government Agency
Industry: Transportation
Location: United States
Size: Mid

Entity Name: Frontrol
Entity Type: Corporation
Industry: Technology/Security

Entity Name: MAS Holdings
Entity Type: Corporation
Industry: Apparel/Manufacturing
Location: Sri Lanka
Size: Large

Entity Name: Trane Technologies
Entity Type: Corporation
Industry: HVAC/Manufacturing
Location: United States
Size: Large

Entity Name: Treet Corp
Entity Type: Corporation
Industry: Manufacturing

Entity Name: University of Phoenix
Entity Type: Educational Institution
Industry: Education
Location: United States
Size: Large

Entity Name: L&L Products
Entity Type: Corporation
Industry: Automotive/Manufacturing
Location: United States
Size: Mid-Large

Entity Name: Worley
Entity Type: Corporation
Industry: Engineering/Consulting
Location: Australia
Size: Large

Entity Name: Fleet Management Limited
Entity Type: Corporation
Industry: Logistics/Transportation

Entity Name: Alshaya Group
Entity Type: Corporation
Industry: Retail/Hospitality
Location: Kuwait
Size: Large

Entity Name: Bechtel Corporation
Entity Type: Corporation
Industry: Construction/Engineering
Location: United States
Size: Large

Entity Name: WellBiz Brands, Inc.
Entity Type: Corporation
Industry: Retail/Wellness
Location: United States
Size: Mid

Entity Name: Dooney & Bourke
Entity Type: Corporation
Industry: Luxury Accessories
Location: United States
Size: Mid

Entity Name: Greenball
Entity Type: Corporation
Industry: Manufacturing

Entity Name: Sumitomo Chemical
Entity Type: Corporation
Industry: Chemicals
Location: Japan
Size: Large

Entity Name: Aljomaih Automotive Company (AAC)
Entity Type: Corporation
Industry: Automotive
Location: Saudi Arabia
Size: Large

Entity Name: Parexel
Entity Type: Company
Industry: Clinical Research, Pharmaceutical
Customers Affected: Employees

Entity Name: University of Phoenix
Entity Type: Educational Institution
Industry: Higher Education
Location: Phoenix, Arizona, USA
Size: Over 100,000 enrolled students and nearly 3,000 academic staff
Customers Affected: 3,489,274 (current and former students, employees, faculty, and suppliers)

Entity Name: University of Phoenix
Entity Type: Educational Institution
Industry: Higher Education
Location: Phoenix, Arizona, USA
Size: Large
Customers Affected: 3,489,274

Entity Name: Marks and Spencer
Entity Type: business
Industry: retail
Location: UK

Entity Name: Adidas
Entity Type: business
Industry: apparel
Location: UK

Entity Name: Co-op Group
Entity Type: business
Industry: retail
Location: UK

Entity Name: Heathrow Airport
Entity Type: business
Industry: aviation
Location: UK

Entity Name: Harrods
Entity Type: business
Industry: retail
Location: UK

Entity Name: Jaguar Land Rover (JLR)
Entity Type: business
Industry: automotive
Location: UK

Entity Name: German Parliament
Entity Type: government
Industry: public sector
Location: Germany

Entity Name: UK Foreign Office
Entity Type: government
Industry: public sector
Location: UK

Entity Name: University of Pennsylvania
Entity Type: University
Industry: Higher Education
Location: United States
Size: Large
Customers Affected: Thousands of students, faculty, and staff

Entity Name: Harvard University
Entity Type: University
Industry: Higher Education
Location: United States
Size: Large
Customers Affected: Thousands of students, faculty, and staff

Entity Name: Princeton University
Entity Type: University
Industry: Higher Education
Location: United States
Size: Large
Customers Affected: Thousands of students, faculty, and staff

Entity Name: Columbia University
Entity Type: University
Industry: Higher Education
Location: United States
Size: Large
Customers Affected: Thousands of students, faculty, and staff

Entity Name: Dartmouth College
Entity Type: University
Industry: Higher Education
Location: United States
Size: Large
Customers Affected: Thousands of students, faculty, and staff

Entity Name: New York University
Entity Type: University
Industry: Higher Education
Location: United States
Size: Large
Customers Affected: Thousands of students, faculty, and staff

Entity Name: Oracle
Entity Type: Corporation
Industry: Technology/Software

Entity Name: Salesforce Ecosystem
Entity Type: SaaS
Industry: Technology

Entity Name: Oracle E-Business Suite
Entity Type: Enterprise Software
Industry: Technology

Entity Name: Jaguar Land Rover
Entity Type: Automotive
Industry: Manufacturing
Location: UK

Entity Name: Ingram Micro
Entity Type: IT Distribution
Industry: Technology
Location: Global

Entity Name: Co-operative Group
Entity Type: Retail
Industry: Retail
Location: UK

Entity Name: PowerSchool
Entity Type: Education Software
Industry: Education

Entity Name: Synnovis
Entity Type: Healthcare Services
Industry: Healthcare

Entity Name: DaVita
Entity Type: Healthcare
Industry: Healthcare

Entity Name: Asahi Group
Entity Type: Manufacturing
Industry: Manufacturing

Entity Name: Collins Aerospace
Entity Type: Aerospace
Industry: Aviation
Location: Europe

Entity Name: Cloudflare
Entity Type: Cybersecurity Infrastructure Provider
Industry: Technology

Entity Name: University of Pennsylvania
Entity Type: University
Industry: Education
Location: Philadelphia, Pennsylvania, USA
Customers Affected: Fewer than 10 individuals (students, donors, alumni)

Entity Name: SUNY Research Foundation
Entity Type: Research Foundation
Industry: Education/Research
Location: Albany, New York
Customers Affected: Employees

Entity Name: Conduent
Entity Type: Business
Industry: Technology/Business Services
Location: U.S.

Entity Name: Episource
Entity Type: Business
Industry: Healthcare/Technology
Location: U.S.

Entity Name: University of Phoenix
Entity Type: Education
Industry: Education
Location: U.S.

Entity Name: DaVita
Entity Type: Business
Industry: Healthcare
Location: U.S.

Entity Name: Sanrio
Entity Type: Business
Industry: Retail/Consumer Goods
Location: Japan

Entity Name: Asahi Group
Entity Type: Business
Industry: Food & Beverage
Location: Japan

Entity Name: Co-operative Group
Entity Type: Business
Industry: Retail
Location: U.K.

Entity Name: JobsGO
Entity Type: Recruitment platform
Industry: Human Resources/Recruitment
Location: Vietnam
Customers Affected: Over two million records exposed

Entity Type: Cloud service providers
Industry: Technology/Cloud Computing
Location: South KoreaCanadaU.S.SerbiaUAE
Customers Affected: 60,000+ servers compromised

Entity Name: Anywhere Real Estate
Entity Type: Corporation
Industry: Real Estate
Customers Affected: 17,429

Entity Name: Wynn Resorts
Entity Type: Organization
Industry: Hospitality and Gaming
Customers Affected: 800,000 employees

Entity Name: Madison Square Garden Entertainment Corp. (MSG Entertainment)
Entity Type: Corporation
Industry: Entertainment, Venue Management
Location: New York, USA

Entity Name: Madison Square Garden Entertainment (MSGE)
Entity Type: Corporation
Industry: Entertainment and Hospitality
Location: New York City and Chicago, USA
Customers Affected: 131000

Entity Name: Maritz Holdings Inc.
Entity Type: Management Consulting Firm
Industry: Consulting
Location: Missouri, USA
Size: 4,250 employees, $1.4 billion revenue
Customers Affected: Current and former employees and clients

Entity Name: Anduril
Entity Type: Company
Industry: Defense/Technology

Entity Name: HBGary
Entity Type: Company
Industry: Cybersecurity

Entity Name: L3Harris
Entity Type: Company
Industry: Defense/Aerospace

Entity Name: Microsoft
Entity Type: Company
Industry: Technology

Entity Name: Oracle
Entity Type: Company
Industry: Technology

Entity Name: Palantir
Entity Type: Company
Industry: Data Analytics/Defense

Entity Name: Raytheon
Entity Type: Company
Industry: Defense/Aerospace

Entity Name: FBI
Entity Type: Government Agency
Industry: Law Enforcement

Entity Name: NASA
Entity Type: Government Agency
Industry: Aerospace

Entity Name: Universities
Entity Type: Educational Institution
Industry: Education

Entity Name: Michelin
Entity Type: Corporation
Industry: Tire Manufacturing

Entity Name: Loblaw Companies Limited
Entity Type: Retailer / Pharmacy
Industry: Retail, Grocery, Pharmacy, Loyalty Programs
Location: Canada
Size: Large (Canada’s largest food and pharmacy retailer)
Customers Affected: Potentially millions (PC Optimum, Shoppers Drug Mart, prescription users)

Entity Name: Hypertherm, Inc.
Entity Type: Manufacturer
Industry: Industrial Cutting Products, Shipbuilding, Automotive Repair, Manufacturing

Entity Name: Hypertherm
Entity Type: Manufacturer
Industry: Industrial cutting systems
Location: Hanover, New Hampshire, USA
Customers Affected: 531 (334 Texas residents, 166 New Hampshire residents, 31 Maine residents)

Entity Name: Abbott Technologies
Entity Type: Company

Entity Name: Wits University
Entity Type: Educational Institution
Industry: Education
Location: South Africa

Entity Name: Oracle
Entity Type: Technology Vendor
Industry: Software/IT Services
Customers Affected: Organizations using Oracle Fusion Middleware versions 12.2.1.4.0 and 14.1.2.1.0

Containment Measures: Password Change Recommendation
Communication Strategy: Customer Advisory

Communication Strategy: Criticized for lack of transparency

Communication Strategy: Private letters to customers

Communication Strategy: Outright DenialPotentially Misleading StatementsAccusations of Deleting Evidence Online

Remediation Measures: Informed clientsBolstered Gen 1 server security

Law Enforcement Notified: Yes (California Office of the Attorney General)

Third Party Assistance: Okta Threat Intelligence (Analysis By Moussa Diallo).
Containment Measures: monitoring for suspicious domain registrationsblocking known malicious domains
Remediation Measures: implementation of phishing-resistant authentication (e.g., passkeys, FIDO2 WebAuthn)adaptive risk assessments for unusual access patterns
Communication Strategy: customer advisories about impersonation attemptsindustry-wide alerts
Enhanced Monitoring: real-time tracking of typosquatted domainsbeaconing detection

Incident Response Plan Activated: Recommended (investigate Oracle E-Business Suite environments)
Third Party Assistance: Mandiant (Google Cloud), Gtig.
Enhanced Monitoring: Recommended (for unusual access)

Incident Response Plan Activated: True
Third Party Assistance: Mandiant (Google Cloud), Google Threat Intelligence Group (Gtig).
Communication Strategy: Public Warning via Cybersecurity Firms (Mandiant, GTIG)Media Outreach (Recorded Future News)

Incident Response Plan Activated: True
Third Party Assistance: Mandiant (Google Cloud).
Containment Measures: Emergency Patch Release (CVE-2025-61882)Advisory for Customer Mitigation
Remediation Measures: Patch ApplicationInvestigation into Potential Prior Compromise
Communication Strategy: Public AdvisoryLinkedIn Post by Oracle CSOMandiant Technical Alert
Enhanced Monitoring: Recommended for customers to detect prior compromise

Incident Response Plan Activated: Yes (Oracle released patch and urged immediate installation)
Third Party Assistance: Google Mandiant (Investigation And Advisory).
Containment Measures: Patch release (CVE-2025-61882)Indicators of Compromise (IoCs) shared with customers
Remediation Measures: Urgent patch installation recommended for all customers
Communication Strategy: Public security advisory by Oracle CSO Rob DuhartLinkedIn post by Google Mandiant CTO Charles Carmakal

Incident Response Plan Activated: ['Oracle Security Alert (Urgent Patching Advisory)']
Third Party Assistance: Crowdstrike (Detection And Analysis), Mandiant (Investigation), Google Threat Intelligence Group (Gtig).
Containment Measures: Patching CVE-2025-61882Disabling Exposed EBS Components
Communication Strategy: Oracle Customer AdvisoryPublic Disclosure of PoC Risks
Enhanced Monitoring: Recommended for Oracle EBS Environments

Incident Response Plan Activated: Yes (Google and Oracle)
Third Party Assistance: Google Security Researchers.
Remediation Measures: Oracle Security Advisory IssuedTechnical Indicators Shared by Google for Detection
Communication Strategy: Public Advisory by OracleBlog Post by GoogleMedia Statements
Enhanced Monitoring: Recommended (Google Provided Indicators for Detection)

Incident Response Plan Activated: Yes (Oracle Released Emergency Security Alerts and Patches)
Third Party Assistance: Google Threat Intelligence, Mandiant, Crowdstrike.
Containment Measures: Emergency Patching (CVE-2025-61884 & CVE-2025-61882)Urgent Advisory for Customers to Apply Updates
Remediation Measures: Patch DeploymentMitigation Guidance for Unpatched Systems
Communication Strategy: Public Security AdvisoriesDirect Customer Notifications
Enhanced Monitoring: Recommended (Oracle Advised Customers to Monitor for Exploitation Attempts)

Incident Response Plan Activated: [None, 'Yes (Microsoft Patch Tuesday)', None, None, 'Yes (Certificate Revocation)', None, 'Yes (DOJ Seizure)', None, 'Varies (Healthcare Sector)']
Third Party Assistance: Law Enforcement (Doj).
Law Enforcement Notified: Yes (DOJ),
Containment Measures: Patches ReleasedCertificate RevocationAsset Seizure
Remediation Measures: Patch for CVE-2025-61884October 2025 Security UpdatesAEM JEE Misconfiguration FixMalicious Cert BlacklistingCisco IOS/IOS XE PatchesBluetooth Protocol Updates
Communication Strategy: Patch Tuesday AnnouncementPublic Breach DisclosureCISA KEV Catalog UpdateMicrosoft Security BlogCisco Security AdvisoryDOJ Press ReleaseAlias Robotics AdvisoryHealthcare IT Alerts
Adaptive Behavioral WAF: [None, None, None, None, None, None, None, None, None]
On-Demand Scrubbing Services: [None, None, None, None, None, None, None, None, None]
Network Segmentation: [None, None, None, None, None, None, None, None, None]

Incident Response Plan Activated: [None, None, 'Partial (5,000 user credentials rotated, but NHI token overlooked)']
Containment Measures: Token revocation (post-incident)Token revocation (post-discovery of compromise)
Adaptive Behavioral WAF: [None, None, None]
On-Demand Scrubbing Services: [None, None, None]
Network Segmentation: [None, None, None]

Incident Response Plan Activated: yes (NHS cybersecurity team involved)
Third Party Assistance: yes (National Cyber Security Centre - NCSC)
Communication Strategy: public statement issued (neither confirmed nor denied intrusion)

Remediation Measures: Patch released in October 2025 Security Alert

Third Party Assistance: Security Researchers (The Raven File).
Remediation Measures: Oracle released patch in October 2025

Incident Response Plan Activated: True
Third Party Assistance: Potential Involvement Of Mandiant (Forensic Investigation).
Containment Measures: Patch application (Oracle emergency patch on 2025-10-04)Network segmentation (assumed)
Remediation Measures: Free credit monitoring for affected individualsOngoing forensic investigation
Communication Strategy: Notification letters to affected partiesPublic disclosure via Maine Attorney General’s Office filing
Network Segmentation: Recommended (not explicitly confirmed)
Enhanced Monitoring: Recommended (not explicitly confirmed)

Incident Response Plan Activated: True
Third Party Assistance: Mandiant (Google-Owned Cybersecurity Firm).
Containment Measures: Oracle security patches (CVE-2025-61882, CVE-2025-21884)
Remediation Measures: Patch application for Oracle EBS vulnerabilities
Communication Strategy: Oracle security alerts to customersPublic disclosure via media

Communication Strategy: Data breach notification letters mailed to impacted individuals

Communication Strategy: Public disclosure on official website, SEC filing, notification letters to affected individuals

Communication Strategy: Written notice to affected individuals on Dec. 22, 2025

Incident Response Plan Activated: Yes
Containment Measures: Removed hackers' access to internal systems
Remediation Measures: Stepped up security protocols
Communication Strategy: Public statements to stakeholders

Containment Measures: Restricted network access to affected HTTP ports
Remediation Measures: Patches released in Critical Patch Update (CPU)

Incident Response Plan Activated: Automated detection and mitigation
Containment Measures: Automated systems mitigated attacks without triggering internal alerts

Incident Response Plan Activated: Engaged cybersecurity specialists
Third Party Assistance: Cybersecurity specialists
Remediation Measures: Comprehensive review of compromised files, notifications to affected individuals
Communication Strategy: Public statement dismissing hackers' claims, notifications to affected individuals

Containment Measures: Oracle released an urgent patch for the zero-day vulnerability
Communication Strategy: Affected employees were notified last week

Third Party Assistance: Flare (security firm)

Communication Strategy: Notified impacted individuals via breach notification

Communication Strategy: Customer notifications via mail

Third Party Assistance: Lynch Carpenter, LLP (investigation)

Third Party Assistance: Cybersecurity experts
Law Enforcement Notified: Yes
Communication Strategy: Written notifications to affected individuals

Incident Response Plan Activated: Yes
Containment Measures: Corrective actions taken, vulnerability patched
Remediation Measures: Vulnerability patched
Communication Strategy: Public disclosure and assurance of containment

Communication Strategy: Press release downplaying the breach and denying financial data compromise

Third Party Assistance: Third-party cybersecurity experts
Communication Strategy: Notification to affected individuals

Third Party Assistance: Kroll (identity monitoring)
Communication Strategy: Notification letters mailed to affected individuals, dedicated call center (844-403-4502)

Communication Strategy: Lack of public disclosure from affected companies

Third Party Assistance: Oracle and cybersecurity experts

Remediation Measures: Patch deployment (KB878741)
Communication Strategy: Urgent security alert issued
Incident Response Plan: The company's incident response plan is described as Recommended (investigate Oracle E-Business Suite environments), , , Yes (Oracle released patch and urged immediate installation), Oracle Security Alert (Urgent Patching Advisory), , Yes (Google and Oracle), Yes (Oracle Released Emergency Security Alerts and Patches), Yes (Microsoft Patch Tuesday), Yes (Certificate Revocation), Yes (DOJ Seizure), Varies (Healthcare Sector), , Partial (5,000 user credentials rotated, but NHI token overlooked), , , , , Yes, Automated detection and mitigation, Engaged cybersecurity specialists, Yes.
Third-Party Assistance: The company involves third-party assistance in incident response through Okta Threat Intelligence (analysis by Moussa Diallo), , Mandiant (Google Cloud), GTIG, , Mandiant (Google Cloud), Google Threat Intelligence Group (GTIG), , Mandiant (Google Cloud), , Google Mandiant (investigation and advisory), , CrowdStrike (Detection and Analysis), Mandiant (Investigation), Google Threat Intelligence Group (GTIG), , Google Security Researchers, , Google Threat Intelligence, Mandiant, CrowdStrike, , Law Enforcement (DOJ), , , , Security researchers (THE RAVEN FILE), , Potential involvement of Mandiant (forensic investigation), , Mandiant (Google-owned cybersecurity firm), , Cybersecurity specialists, Flare (security firm), Lynch Carpenter, LLP (investigation), Cybersecurity experts, Third-party cybersecurity experts, Kroll (identity monitoring), Oracle and cybersecurity experts.

Type of Data Compromised: Credit card payment information
Sensitivity of Data: High

Type of Data Compromised: Sso passwords, Java keystore files, Key files, Jps keys
Number of Records Exposed: 6 million
Sensitivity of Data: High
Data Encryption: Encrypted and hashed passwords

Type of Data Compromised: Jks files, Encrypted sso passwords, Key files, Jps keys
Number of Records Exposed: 6 million
Sensitivity of Data: High
Data Exfiltration: Yes
Data Encryption: Yes
File Types Exposed: JKS filesSSO passwordsKey filesJPS keys

Type of Data Compromised: Electronic health records (ehr)
Data Exfiltration: Electronic Health Records (EHR)

Type of Data Compromised: Sensitive customer data
Sensitivity of Data: High

Type of Data Compromised: Personal Information

Type of Data Compromised: Usernames, Email addresses, Hashed passwords, Sso credentials, Ldap credentials, Jks files, Enterprise manager jps keys
Number of Records Exposed: 6 million
Sensitivity of Data: High
File Types Exposed: JKS filesJPS keys

Type of Data Compromised: Personally identifiable information (pii)
Number of Records Exposed: Unknown
Sensitivity of Data: High
Data Exfiltration: Yes (report accessed)
Personally Identifiable Information: NamesSocial Security Numbers

Type of Data Compromised: Credentials (usernames, passwords), Pii (email addresses, phone numbers), Guest data, Payment information, Booking details
Sensitivity of Data: high (financial and personal identifiable information)
Data Exfiltration: likely (credentials sold on dark web)
Personally Identifiable Information: namesemail addressesphone numberspotential payment card data

Data Exfiltration: Claimed (unsubstantiated)

Type of Data Compromised: Potentially finance, hr, supply chain data, Client credentials (from january incident)
Sensitivity of Data: High (Enterprise-Critical and Potentially PII)
Data Exfiltration: Claimed by Threat Actor (Unverified)
Personally Identifiable Information: Potential (If HR Data Compromised)


Type of Data Compromised: Personal information (executives), Customer data, Employee hr files
Sensitivity of Data: High (personal and corporate-sensitive data)
Data Exfiltration: Yes (evidenced by extortion emails)
Personally Identifiable Information: Yes (executives' personal data)

Type of Data Compromised: Sensitive corporate documents, Potentially pii
Sensitivity of Data: High (confidential business documents)
Data Exfiltration: Confirmed (by Clop for extortion)
Personally Identifiable Information: Possible (not explicitly confirmed)

Type of Data Compromised: Personally identifiable information (pii) of executives, Customer data, Employee hr files, Corporate sensitive data
Sensitivity of Data: High
Data Exfiltration: Confirmed
Personally Identifiable Information: Yes (Executives and Employees)

Type of Data Compromised: Sensitive resources, Potentially oracle ebs data (as per extortion claims)
Sensitivity of Data: High (Potential Access to Confidential Business Data)
Data Exfiltration: Claimed in Extortion Emails (Unverified)

Type of Data Compromised: Source code & vulnerability details, Robot sensor data
Number of Records Exposed: None, None, None, None, None, None, None, None, None
Sensitivity of Data: High (Proprietary Code)High (Espionage Risk)High (PHI/PII)
Data Exfiltration: Yes (Source Code)Yes (China-Linked)Likely (Ransomware)
Data Encryption: [None, None, None, None, None, None, None, None, None]
Personally Identifiable Information: Yes (Patient Data)

Type of Data Compromised: Crm data (salesforce), aws keys, snowflake tokens, Internal source code (270 gb), proprietary data, Atlassian suite data (jira, confluence, bitbucket)
Number of Records Exposed: None, None, None
Sensitivity of Data: High (credentials, CRM data)High (source code, internal data)High (Atlassian suite data)
Data Exfiltration: Yes (sensitive records, credentials)Yes (270 GB of data)Likely (unauthorized access to Atlassian data)
Data Encryption: [None, None, None]
File Types Exposed: CRM records, support case attachments (containing credentials)Source code files, internal documentationJira tickets, Confluence pages, Bitbucket repositories
Personally Identifiable Information: Possible (via CRM data)Possible (in source code/comments)Possible (in Atlassian data)

Sensitivity of Data: high (potential patient data, including personally identifiable information)
Data Exfiltration: unconfirmed (Clop listed NHS on leak site but no data published yet)
Personally Identifiable Information: likely (NHS stores vast quantities of patient data)

Type of Data Compromised: Financial records, Personal records, Erp data
Sensitivity of Data: High
Data Exfiltration: Confirmed (threatened release on dark web)
Personally Identifiable Information: Yes

Type of Data Compromised: Corporate internal data, Customer information, Financial records, Personal data
Sensitivity of Data: High
Data Exfiltration: Claimed by Clop (evidenced by dark web leak site listing)
Personally Identifiable Information: Likely (based on extortion threats)

Type of Data Compromised: Pii (personally identifiable information), Internal documents, Employee records, Customer details
Number of Records Exposed: 9,479 individuals
Sensitivity of Data: High (includes SSNs, dates of birth, addresses)
Data Exfiltration: 1.6 TB of data leaked on the dark web
File Types Exposed: DatabasesDocumentsHR/Employee Records

Type of Data Compromised: Corporate data, Customer data, Sensitive business information
Sensitivity of Data: High

Type of Data Compromised: Name, Social security number, Date of birth, Financial account number, Payment card number (without cvv), National id number
Sensitivity of Data: High
Personally Identifiable Information: Yes

Type of Data Compromised: Personal information, Financial information
Number of Records Exposed: 3,489,274
Sensitivity of Data: High (Social Security numbers, bank account and routing numbers, dates of birth, contact information)
Data Exfiltration: Yes
Personally Identifiable Information: Yes

Type of Data Compromised: Names, Dates of birth, Social security numbers, Bank account numbers, Bank routing numbers
Number of Records Exposed: 3,489,274
Sensitivity of Data: High
Data Exfiltration: Yes
Personally Identifiable Information: Yes

Type of Data Compromised: Personal data, potentially including personally identifiable information
Sensitivity of Data: High (personal and potentially sensitive information)
Personally Identifiable Information: Likely (e.g., Social Security numbers, payroll data)

Type of Data Compromised: Sensitive data

Data Encryption: True

Type of Data Compromised: Personal data
Number of Records Exposed: Fewer than 10
Personally Identifiable Information: Yes

Type of Data Compromised: Personnel files, Social Security numbers
Sensitivity of Data: High (Personally Identifiable Information)
Personally Identifiable Information: Social Security numbers

Type of Data Compromised: Personally identifiable information, Corporate data
Number of Records Exposed: 59.2 million (confirmed), 15.9 million (Conduent), 5.4 million (Episource), 3.49 million (University of Phoenix), 2.69 million (DaVita), 2 million (Sanrio), 1.9 million (Asahi Group)
Data Exfiltration: 31.2 petabytes (Qilin)8.5 terabytes (Conduent)1.5 terabytes (DaVita)

Type of Data Compromised: Personal ids, Employment records, Résumés
Number of Records Exposed: Over two million
Sensitivity of Data: High (personally identifiable and professional information)

Type of Data Compromised: Sensitive customer data
Number of Records Exposed: 17,429
Sensitivity of Data: High
Data Exfiltration: Potential
Personally Identifiable Information: Potential

Type of Data Compromised: Full names, Emails, Phone numbers, Job positions, Salaries, Start dates, Birth dates, Other personal details
Number of Records Exposed: 800,000
Sensitivity of Data: High
Data Exfiltration: Yes
Personally Identifiable Information: Yes

Type of Data Compromised: Personal Information
Sensitivity of Data: High (Social Security numbers, names, addresses)
Personally Identifiable Information: Names, addresses, Social Security numbers

Type of Data Compromised: Personally Identifiable Information (PII)
Number of Records Exposed: 131000
Sensitivity of Data: High (names, addresses, Social Security numbers)
Personally Identifiable Information: Names, addresses, Social Security numbers

Type of Data Compromised: Names, Social security numbers, Financial account information
Sensitivity of Data: High
Personally Identifiable Information: Yes

Type of Data Compromised: Contract details, company information, employee details, tax ID numbers, government identifiers, internal comments, awarded contracts
Number of Records Exposed: 6,600+ organizations
Sensitivity of Data: High (includes SSNs, EINs, personal and business addresses, internal communications)
Personally Identifiable Information: Names, titles, contact information, SSNs, EINs, addresses

Type of Data Compromised: Files (unspecified)
Sensitivity of Data: Non-sensitive, non-technical IT data
Data Exfiltration: Yes (315GB published on leak site)

Type of Data Compromised: Customer records (names, emails, phone numbers, addresses, loyalty ids), Health card numbers, Pharmacy fill requests (prescription numbers, patient ids), Payment details (full credit card numbers with expiry dates, bins, last-four digits), Source code (gitlab projects), Mfa device details and credentials (oracle identity records), Marketing and email records
Number of Records Exposed: 1.8 billion (alleged)
Sensitivity of Data: High (PII, financial data, health information, source code)
Data Exfiltration: Alleged (data sold on dark web if claims are true)
Personally Identifiable Information: Yes (names, emails, phone numbers, addresses, health card numbers, prescription IDs)

Type of Data Compromised: Sensitive information, database tables
Sensitivity of Data: High
Data Exfiltration: Yes

Type of Data Compromised: Personally Identifiable Information (PII)
Sensitivity of Data: High (Social Security numbers)
Data Exfiltration: Yes (database tables stolen)
File Types Exposed: Database tables
Personally Identifiable Information: Names, Social Security numbers

Type of Data Compromised: Sensitive corporate and customer data
Sensitivity of Data: High

Type of Data Compromised: Corporate identity data
Sensitivity of Data: High
Prevention of Data Exfiltration: The company takes the following measures to prevent data exfiltration: Informed clients, Bolstered Gen 1 server security, , implementation of phishing-resistant authentication (e.g., passkeys, FIDO2 WebAuthn), adaptive risk assessments for unusual access patterns, , Patch Application, Investigation into Potential Prior Compromise, , Urgent patch installation recommended for all customers, , Oracle Security Advisory Issued, Technical Indicators Shared by Google for Detection, , Patch Deployment, Mitigation Guidance for Unpatched Systems, , Patch for CVE-2025-61884, October 2025 Security Updates, AEM JEE Misconfiguration Fix, Malicious Cert Blacklisting, Cisco IOS/IOS XE Patches, Bluetooth Protocol Updates, , , Patch released in October 2025 Security Alert, , Oracle released patch in October 2025, , Free credit monitoring for affected individuals, Ongoing forensic investigation, , Patch application for Oracle EBS vulnerabilities, , Stepped up security protocols, Patches released in Critical Patch Update (CPU), Comprehensive review of compromised files, notifications to affected individuals, Vulnerability patched, Patch deployment (KB878741).
Handling of PII Incidents: The company handles incidents involving personally identifiable information (PII) through by password change recommendation, , monitoring for suspicious domain registrations, blocking known malicious domains, , emergency patch release (cve-2025-61882), advisory for customer mitigation, , patch release (cve-2025-61882), indicators of compromise (iocs) shared with customers, , patching cve-2025-61882, disabling exposed ebs components, , emergency patching (cve-2025-61884 & cve-2025-61882), urgent advisory for customers to apply updates, , patches released, certificate revocation, asset seizure, , token revocation (post-incident), token revocation (post-discovery of compromise), , patch application (oracle emergency patch on 2025-10-04), network segmentation (assumed), , oracle security patches (cve-2025-61882, cve-2025-21884), , removed hackers' access to internal systems, restricted network access to affected http ports, automated systems mitigated attacks without triggering internal alerts, oracle released an urgent patch for the zero-day vulnerability, corrective actions taken and vulnerability patched.

Ransomware Strain: Clop (potential link)
Data Exfiltration: Claimed (unsubstantiated)

Ransomware Strain: Clop (Claimed Affiliation)
Data Exfiltration: Claimed (Unverified)

Ransom Demanded: Yes (extortion emails sent to executives)
Data Exfiltration: Yes

Ransom Demanded: ['Undisclosed (extortion emails sent to executives)']
Ransomware Strain: Clop
Data Encryption: ['No (data theft-only campaign)']
Data Exfiltration: ['Yes']

Ransom Demanded: Extortion Emails Sent (Amount Unspecified)
Ransomware Strain: Cl0p
Data Exfiltration: Claimed (Unverified)

Ransom Demanded: [None, None, None, None, None, None, None, None, None]
Ransomware Strain: Vanilla Tempest
Data Encryption: [None, None, None, None, None, None, None, None, 'Likely (Ransomware)']
Data Exfiltration: [None, None, None, None, None, None, None, None, 'Likely (Double Extortion)']

Ransom Demanded: [None, None, None]
Data Encryption: [None, None, None]
Data Exfiltration: ['Yes', 'Yes', 'Likely']

Ransom Paid: no (NHS policy is to not pay ransoms)
Data Exfiltration: unconfirmed

Ransomware Strain: Clop
Data Exfiltration: Confirmed (threatened public release)

Ransom Demanded: True
Ransomware Strain: Cl0p (Clop)
Data Exfiltration: True

Ransom Demanded: True
Data Encryption: True
Data Exfiltration: True

Ransom Demanded: ['$1.2 million (manufacturing average)', '$610,000 (legal firms average)', '$1.09 million (businesses average)', '$1.55 million (government average)', '$615,000 (healthcare average)', '$457,200 (education average)']
Ransomware Strain: QilinAkiraSafePayClopInterlockDragonForce
Data Exfiltration: ['31.2 petabytes (Qilin)', '8.5 terabytes (Conduent)', '1.5 terabytes (DaVita)']

Data Exfiltration: True

Ransom Demanded: 23.34 Bitcoin (≈$1.55 million)
Data Exfiltration: Yes

Data Exfiltration: Alleged

Regulations Violated: HIPAA,

Regulatory Notifications: California Office of the Attorney General

Regulatory Notifications: CISA Warning (January Incident, Potentially Linked)

Regulatory Notifications: Oracle Customer Advisory (non-regulatory)

Regulations Violated: Anti-Money Laundering (AML),
Fines Imposed: [None, None, None, None, None, None, None, None, None]
Legal Actions: None, None, None, None, None, None, Criminal Prosecution (Forced Labor), None, Potential HIPAA Enforcement,
Regulatory Notifications: CISA KEV Catalog

Fines Imposed: [None, None, None]
Legal Actions: None, None, None,

Regulations Violated: Potential GDPR (EU), CCPA (California), State breach notification laws (e.g., Maine),
Legal Actions: Potential lawsuits (e.g., against Oracle for delayed patching),
Regulatory Notifications: Maine Attorney General’s Office filingCISA alerts for related vulnerabilities (e.g., CVE-2025-61757)

Regulatory Notifications: Reported to the Attorney General of the Commonwealth of Massachusetts

Regulations Violated: Potential violations of data protection laws (e.g., FERPA, GDPR if applicable),
Regulatory Notifications: Filed with Maine's Attorney General, SEC filing

Regulatory Notifications: California Attorney General's officeMaine Attorney General's office

Legal Actions: Class-action lawsuit (consolidated)
Regulatory Notifications: Notifications sent to affected individuals as required by law

Regulations Violated: New York’s 30-day notification requirement for data breaches

Regulatory Notifications: Maine Attorney General’s Office

Legal Actions: Class action investigation by Edelson Lechtzin LLP

Legal Actions: Potential (under investigation by Lynch Carpenter, LLP)

Legal Actions: Legal investigations underway for potential compensation claims

Legal Actions: Class action investigation by Edelson Lechtzin LLP

Regulatory Notifications: Filed reports with Maine, New Hampshire, and Texas Attorneys General

Regulatory Notifications: Notified South Africa’s Information Regulator
Ensuring Regulatory Compliance: The company ensures compliance with regulatory requirements through None, None, None, None, None, None, Criminal Prosecution (Forced Labor), None, Potential HIPAA Enforcement, , None, None, None, , Potential lawsuits (e.g., against Oracle for delayed patching), , Class-action lawsuit (consolidated), Class action investigation by Edelson Lechtzin LLP, Potential (under investigation by Lynch Carpenter, LLP), Legal investigations underway for potential compensation claims, Class action investigation by Edelson Lechtzin LLP.

Lessons Learned: Malvertising is an effective initial access vector for targeted phishing campaigns., MFA bypass techniques (e.g., real-time OTP capture) undermine traditional authentication methods., Typosquatted domains and convincing phishing pages can evade user scrutiny., Russian-speaking threat actors continue to leverage proxy infrastructure for anonymity., Hospitality industry is a high-value target due to sensitive guest data and payment systems.

Lessons Learned: Zero-day vulnerabilities in widely used enterprise software like Oracle E-Business Suite can lead to rapid, high-impact exploitation by multiple threat actors. Organizations must prioritize patch management and assume breach scenarios even after patching, given the likelihood of prior compromise during mass exploitation campaigns.

Lessons Learned: Zero-day vulnerabilities in enterprise software like Oracle EBS are high-value targets for ransomware groups., Public PoC disclosures accelerate exploitation by multiple threat actors., Proactive patching and exposure management are critical for mitigating RCE risks.

Lessons Learned: Zero-day vulnerabilities in widely used enterprise software can lead to large-scale data breaches. Proactive patch management and monitoring for unusual network activity are critical. Vendors must ensure transparent communication during ongoing incidents to avoid misinformation.

Lessons Learned: Critical Importance of Timely Patching for Public-Facing Applications, Risks of Zero-Day Exploitation in Enterprise Software, Need for Enhanced Monitoring of Oracle EBS Instances, Potential for Mass Extortion Campaigns Leveraging Stolen Credentials

Lessons Learned: Proactive vulnerability management is critical for enterprise software (Oracle)., Zero-day exploits underscore the need for rapid patch deployment (Microsoft)., Nation-state threats target high-value intellectual property (F5)., Misconfigurations in enterprise software remain a top attack vector (Adobe)., Certificate abuse highlights risks in software supply chains (Microsoft Teams)., Network device vulnerabilities can enable persistent rootkit infections (Cisco)., Cryptocurrency fraud operations require cross-agency coordination (DOJ)., IoT/robotics security lags behind espionage risks (Unitree G1)., Healthcare cybersecurity gaps directly impact patient safety (Proofpoint).

Lessons Learned: Non-human identities (NHIs) such as OAuth tokens, API keys, and service accounts are high-value targets for attackers due to their broad privileges and lack of oversight. Organizations must extend identity security controls to include NHIs, not just human users., Publicly exposed API tokens can act as unguarded backdoors, granting attackers direct access to sensitive systems without needing to bypass interactive login protections. Token hygiene (e.g., avoiding public exposure, enforcing least privilege) is critical., Orphaned or unrotated service credentials can undermine incident response efforts. Even after rotating human credentials, overlooked NHIs can provide attackers with persistent access. Comprehensive credential rotation must include all identities—human and non-human., Dynamic SaaS Security Platforms are essential for discovering, monitoring, and securing NHIs. Traditional identity controls are insufficient for the scale and complexity of machine identities in modern SaaS environments.

Lessons Learned: Zero-day exploits in ERP systems pose severe risks due to their central role in operations., Delayed detection (weeks between breach and discovery) exacerbates impact., Supply chain vulnerabilities (e.g., Oracle software) require proactive patch management., Ransomware-as-a-Service (RaaS) models enable scalable, sophisticated attacks., Public disclosure strategies must balance transparency with investigative integrity.

Lessons Learned: Supplier vulnerabilities in enterprise software (e.g., Oracle EBS) can cascade into large-scale breaches across industries. Proactive patch management and supply chain risk monitoring (e.g., via SCRM platforms like Z2Data) are critical to mitigating third-party risks. Cl0p’s delayed data leak strategy highlights the importance of rapid incident response to prevent public exposure of sensitive data.

Lessons Learned: Universities are highly vulnerable to cyberattacks due to decentralized IT structures, lack of centralized control, and human error. Cybersecurity training and awareness are critical but not sufficient alone. There is a need for better collaboration between IT departments and faculty to balance security with academic freedom.

Lessons Learned: Ransomware has evolved into a systemic risk with cascading impacts on supply chains, critical services, and industries. Initial access often relies on stolen credentials or social engineering, and supply chain vulnerabilities amplify the impact. Data theft and operational paralysis are primary damage drivers, with delayed consequences such as regulatory penalties or human harm.

Lessons Learned: Limited scope of breach despite initial claims, need for improved cybersecurity measures

Lessons Learned: The incident underscores the risks of unsecured cloud control planes, leaked credentials, and poor access controls, highlighting the need for robust cloud security practices.

Lessons Learned: Highlights risks tied to third-party software vulnerabilities, particularly in widely used enterprise systems like Oracle EBS

Lessons Learned: Transparent communication is increasingly seen as a corporate obligation for stakeholder trust and legal compliance.

Recommendations: Change Passwords, Enhance Security MeasuresChange Passwords, Enhance Security Measures

Recommendations: Adopt phishing-resistant authentication (e.g., passkeys, FIDO2 WebAuthn)., Implement adaptive risk assessments to detect anomalous access patterns., Monitor for suspicious domain registrations (e.g., typosquatting)., Educate employees and customers about malvertising and phishing risks., Deploy behavioral analytics to detect beaconing and tracking scripts., Restrict access to property management systems with zero-trust principles., Collaborate with threat intelligence providers (e.g., Okta) for IOCs.Adopt phishing-resistant authentication (e.g., passkeys, FIDO2 WebAuthn)., Implement adaptive risk assessments to detect anomalous access patterns., Monitor for suspicious domain registrations (e.g., typosquatting)., Educate employees and customers about malvertising and phishing risks., Deploy behavioral analytics to detect beaconing and tracking scripts., Restrict access to property management systems with zero-trust principles., Collaborate with threat intelligence providers (e.g., Okta) for IOCs.Adopt phishing-resistant authentication (e.g., passkeys, FIDO2 WebAuthn)., Implement adaptive risk assessments to detect anomalous access patterns., Monitor for suspicious domain registrations (e.g., typosquatting)., Educate employees and customers about malvertising and phishing risks., Deploy behavioral analytics to detect beaconing and tracking scripts., Restrict access to property management systems with zero-trust principles., Collaborate with threat intelligence providers (e.g., Okta) for IOCs.Adopt phishing-resistant authentication (e.g., passkeys, FIDO2 WebAuthn)., Implement adaptive risk assessments to detect anomalous access patterns., Monitor for suspicious domain registrations (e.g., typosquatting)., Educate employees and customers about malvertising and phishing risks., Deploy behavioral analytics to detect beaconing and tracking scripts., Restrict access to property management systems with zero-trust principles., Collaborate with threat intelligence providers (e.g., Okta) for IOCs.Adopt phishing-resistant authentication (e.g., passkeys, FIDO2 WebAuthn)., Implement adaptive risk assessments to detect anomalous access patterns., Monitor for suspicious domain registrations (e.g., typosquatting)., Educate employees and customers about malvertising and phishing risks., Deploy behavioral analytics to detect beaconing and tracking scripts., Restrict access to property management systems with zero-trust principles., Collaborate with threat intelligence providers (e.g., Okta) for IOCs.Adopt phishing-resistant authentication (e.g., passkeys, FIDO2 WebAuthn)., Implement adaptive risk assessments to detect anomalous access patterns., Monitor for suspicious domain registrations (e.g., typosquatting)., Educate employees and customers about malvertising and phishing risks., Deploy behavioral analytics to detect beaconing and tracking scripts., Restrict access to property management systems with zero-trust principles., Collaborate with threat intelligence providers (e.g., Okta) for IOCs.Adopt phishing-resistant authentication (e.g., passkeys, FIDO2 WebAuthn)., Implement adaptive risk assessments to detect anomalous access patterns., Monitor for suspicious domain registrations (e.g., typosquatting)., Educate employees and customers about malvertising and phishing risks., Deploy behavioral analytics to detect beaconing and tracking scripts., Restrict access to property management systems with zero-trust principles., Collaborate with threat intelligence providers (e.g., Okta) for IOCs.

Recommendations: Investigate Oracle E-Business Suite environments for unusual access or compromise, Monitor for high-volume extortion email campaigns from compromised accounts, Assess potential links to FIN11/Clop ransomware activityInvestigate Oracle E-Business Suite environments for unusual access or compromise, Monitor for high-volume extortion email campaigns from compromised accounts, Assess potential links to FIN11/Clop ransomware activityInvestigate Oracle E-Business Suite environments for unusual access or compromise, Monitor for high-volume extortion email campaigns from compromised accounts, Assess potential links to FIN11/Clop ransomware activity

Recommendations: Immediately apply Oracle's emergency patch for CVE-2025-61882., Conduct forensic investigations to detect signs of prior exploitation., Monitor for IoCs, including the listed IP addresses (200.107.207[.]26, 185.181.60[.]11) and exploit artifacts., Enhance logging and network segmentation for Oracle EBS environments., Review Mandiant's advisory for additional mitigation strategies.Immediately apply Oracle's emergency patch for CVE-2025-61882., Conduct forensic investigations to detect signs of prior exploitation., Monitor for IoCs, including the listed IP addresses (200.107.207[.]26, 185.181.60[.]11) and exploit artifacts., Enhance logging and network segmentation for Oracle EBS environments., Review Mandiant's advisory for additional mitigation strategies.Immediately apply Oracle's emergency patch for CVE-2025-61882., Conduct forensic investigations to detect signs of prior exploitation., Monitor for IoCs, including the listed IP addresses (200.107.207[.]26, 185.181.60[.]11) and exploit artifacts., Enhance logging and network segmentation for Oracle EBS environments., Review Mandiant's advisory for additional mitigation strategies.Immediately apply Oracle's emergency patch for CVE-2025-61882., Conduct forensic investigations to detect signs of prior exploitation., Monitor for IoCs, including the listed IP addresses (200.107.207[.]26, 185.181.60[.]11) and exploit artifacts., Enhance logging and network segmentation for Oracle EBS environments., Review Mandiant's advisory for additional mitigation strategies.Immediately apply Oracle's emergency patch for CVE-2025-61882., Conduct forensic investigations to detect signs of prior exploitation., Monitor for IoCs, including the listed IP addresses (200.107.207[.]26, 185.181.60[.]11) and exploit artifacts., Enhance logging and network segmentation for Oracle EBS environments., Review Mandiant's advisory for additional mitigation strategies.

Recommendations: Install Oracle's patch for CVE-2025-61882 immediately, Monitor systems for Indicators of Compromise (IoCs) provided by Oracle, Enhance security for executive personal data, Review third-party vulnerability disclosures for proactive patchingInstall Oracle's patch for CVE-2025-61882 immediately, Monitor systems for Indicators of Compromise (IoCs) provided by Oracle, Enhance security for executive personal data, Review third-party vulnerability disclosures for proactive patchingInstall Oracle's patch for CVE-2025-61882 immediately, Monitor systems for Indicators of Compromise (IoCs) provided by Oracle, Enhance security for executive personal data, Review third-party vulnerability disclosures for proactive patchingInstall Oracle's patch for CVE-2025-61882 immediately, Monitor systems for Indicators of Compromise (IoCs) provided by Oracle, Enhance security for executive personal data, Review third-party vulnerability disclosures for proactive patching

Recommendations: Immediately patch CVE-2025-61882 in Oracle E-Business Suite environments., Restrict internet exposure of EBS applications and enforce authentication controls., Monitor for signs of data exfiltration, especially via BI Publisher components., Prepare for extortion attempts if using Oracle EBS, given Clop’s history of targeting such vulnerabilities., Engage threat intelligence services (e.g., CrowdStrike, Mandiant) for proactive detection.Immediately patch CVE-2025-61882 in Oracle E-Business Suite environments., Restrict internet exposure of EBS applications and enforce authentication controls., Monitor for signs of data exfiltration, especially via BI Publisher components., Prepare for extortion attempts if using Oracle EBS, given Clop’s history of targeting such vulnerabilities., Engage threat intelligence services (e.g., CrowdStrike, Mandiant) for proactive detection.Immediately patch CVE-2025-61882 in Oracle E-Business Suite environments., Restrict internet exposure of EBS applications and enforce authentication controls., Monitor for signs of data exfiltration, especially via BI Publisher components., Prepare for extortion attempts if using Oracle EBS, given Clop’s history of targeting such vulnerabilities., Engage threat intelligence services (e.g., CrowdStrike, Mandiant) for proactive detection.Immediately patch CVE-2025-61882 in Oracle E-Business Suite environments., Restrict internet exposure of EBS applications and enforce authentication controls., Monitor for signs of data exfiltration, especially via BI Publisher components., Prepare for extortion attempts if using Oracle EBS, given Clop’s history of targeting such vulnerabilities., Engage threat intelligence services (e.g., CrowdStrike, Mandiant) for proactive detection.Immediately patch CVE-2025-61882 in Oracle E-Business Suite environments., Restrict internet exposure of EBS applications and enforce authentication controls., Monitor for signs of data exfiltration, especially via BI Publisher components., Prepare for extortion attempts if using Oracle EBS, given Clop’s history of targeting such vulnerabilities., Engage threat intelligence services (e.g., CrowdStrike, Mandiant) for proactive detection.

Recommendations: Immediately patch Oracle E-Business Suite to the latest version., Monitor networks for indicators of compromise (IoCs) provided by Google., Implement multi-factor authentication (MFA) for all critical systems., Conduct regular security audits for enterprise software., Educate employees about phishing and extortion email tactics.Immediately patch Oracle E-Business Suite to the latest version., Monitor networks for indicators of compromise (IoCs) provided by Google., Implement multi-factor authentication (MFA) for all critical systems., Conduct regular security audits for enterprise software., Educate employees about phishing and extortion email tactics.Immediately patch Oracle E-Business Suite to the latest version., Monitor networks for indicators of compromise (IoCs) provided by Google., Implement multi-factor authentication (MFA) for all critical systems., Conduct regular security audits for enterprise software., Educate employees about phishing and extortion email tactics.Immediately patch Oracle E-Business Suite to the latest version., Monitor networks for indicators of compromise (IoCs) provided by Google., Implement multi-factor authentication (MFA) for all critical systems., Conduct regular security audits for enterprise software., Educate employees about phishing and extortion email tactics.Immediately patch Oracle E-Business Suite to the latest version., Monitor networks for indicators of compromise (IoCs) provided by Google., Implement multi-factor authentication (MFA) for all critical systems., Conduct regular security audits for enterprise software., Educate employees about phishing and extortion email tactics.

Recommendations: Apply Oracle Security Alerts and Critical Patch Updates Immediately, Monitor for Signs of Exploitation (e.g., Unusual Database Activity, Extortion Emails), Implement Multi-Factor Authentication (MFA) for Oracle EBS, Review and Secure Default Password Reset Mechanisms, Segment Networks to Limit Lateral Movement, Engage Third-Party Threat Intelligence for Indicators of Compromise (IOCs)Apply Oracle Security Alerts and Critical Patch Updates Immediately, Monitor for Signs of Exploitation (e.g., Unusual Database Activity, Extortion Emails), Implement Multi-Factor Authentication (MFA) for Oracle EBS, Review and Secure Default Password Reset Mechanisms, Segment Networks to Limit Lateral Movement, Engage Third-Party Threat Intelligence for Indicators of Compromise (IOCs)Apply Oracle Security Alerts and Critical Patch Updates Immediately, Monitor for Signs of Exploitation (e.g., Unusual Database Activity, Extortion Emails), Implement Multi-Factor Authentication (MFA) for Oracle EBS, Review and Secure Default Password Reset Mechanisms, Segment Networks to Limit Lateral Movement, Engage Third-Party Threat Intelligence for Indicators of Compromise (IOCs)Apply Oracle Security Alerts and Critical Patch Updates Immediately, Monitor for Signs of Exploitation (e.g., Unusual Database Activity, Extortion Emails), Implement Multi-Factor Authentication (MFA) for Oracle EBS, Review and Secure Default Password Reset Mechanisms, Segment Networks to Limit Lateral Movement, Engage Third-Party Threat Intelligence for Indicators of Compromise (IOCs)Apply Oracle Security Alerts and Critical Patch Updates Immediately, Monitor for Signs of Exploitation (e.g., Unusual Database Activity, Extortion Emails), Implement Multi-Factor Authentication (MFA) for Oracle EBS, Review and Secure Default Password Reset Mechanisms, Segment Networks to Limit Lateral Movement, Engage Third-Party Threat Intelligence for Indicators of Compromise (IOCs)Apply Oracle Security Alerts and Critical Patch Updates Immediately, Monitor for Signs of Exploitation (e.g., Unusual Database Activity, Extortion Emails), Implement Multi-Factor Authentication (MFA) for Oracle EBS, Review and Secure Default Password Reset Mechanisms, Segment Networks to Limit Lateral Movement, Engage Third-Party Threat Intelligence for Indicators of Compromise (IOCs)

Recommendations:

Recommendations: Implement **unified visibility** of all non-human identities (OAuth apps, API keys, service accounts, bots) across SaaS applications using automated discovery tools., Enforce **least privilege** for NHIs by auditing and restricting overly permissive access scopes. Ensure integrations and tokens can only access the data they explicitly require., Deploy **continuous anomaly monitoring** to detect deviations in NHI behavior (e.g., unusual access times, data volumes, or locations). Baseline normal activity and flag anomalies in real time., Automate **credential rotation and expiration** for all NHIs. Use platforms that detect stale tokens, rotate secrets regularly, and disable unused credentials., Apply **compensating controls** for NHIs where MFA is not feasible (e.g., IP restrictions, scoped access, session monitoring)., Maintain a **real-time inventory** of third-party integrations, especially those connected via user consent (OAuth), and verify their legitimacy and security posture., Disable **orphaned or ghost NHIs** (credentials not tied to active workflows or users), as these are prime targets for attackers., Leverage **Dynamic SaaS Security Platforms** (e.g., Reco) to automate detection, response, and remediation for NHI-related risks, including token revocation and integration quarantine., Conduct **regular audits** of NHI permissions and usage context. Classify NHIs by type (e.g., integrations, AI assistants, RPA bots) to tailor risk controls appropriately., Educate teams on the risks of NHIs and integrate NHI security into broader **identity and access management (IAM)** strategies.Implement **unified visibility** of all non-human identities (OAuth apps, API keys, service accounts, bots) across SaaS applications using automated discovery tools., Enforce **least privilege** for NHIs by auditing and restricting overly permissive access scopes. Ensure integrations and tokens can only access the data they explicitly require., Deploy **continuous anomaly monitoring** to detect deviations in NHI behavior (e.g., unusual access times, data volumes, or locations). Baseline normal activity and flag anomalies in real time., Automate **credential rotation and expiration** for all NHIs. Use platforms that detect stale tokens, rotate secrets regularly, and disable unused credentials., Apply **compensating controls** for NHIs where MFA is not feasible (e.g., IP restrictions, scoped access, session monitoring)., Maintain a **real-time inventory** of third-party integrations, especially those connected via user consent (OAuth), and verify their legitimacy and security posture., Disable **orphaned or ghost NHIs** (credentials not tied to active workflows or users), as these are prime targets for attackers., Leverage **Dynamic SaaS Security Platforms** (e.g., Reco) to automate detection, response, and remediation for NHI-related risks, including token revocation and integration quarantine., Conduct **regular audits** of NHI permissions and usage context. Classify NHIs by type (e.g., integrations, AI assistants, RPA bots) to tailor risk controls appropriately., Educate teams on the risks of NHIs and integrate NHI security into broader **identity and access management (IAM)** strategies.Implement **unified visibility** of all non-human identities (OAuth apps, API keys, service accounts, bots) across SaaS applications using automated discovery tools., Enforce **least privilege** for NHIs by auditing and restricting overly permissive access scopes. Ensure integrations and tokens can only access the data they explicitly require., Deploy **continuous anomaly monitoring** to detect deviations in NHI behavior (e.g., unusual access times, data volumes, or locations). Baseline normal activity and flag anomalies in real time., Automate **credential rotation and expiration** for all NHIs. Use platforms that detect stale tokens, rotate secrets regularly, and disable unused credentials., Apply **compensating controls** for NHIs where MFA is not feasible (e.g., IP restrictions, scoped access, session monitoring)., Maintain a **real-time inventory** of third-party integrations, especially those connected via user consent (OAuth), and verify their legitimacy and security posture., Disable **orphaned or ghost NHIs** (credentials not tied to active workflows or users), as these are prime targets for attackers., Leverage **Dynamic SaaS Security Platforms** (e.g., Reco) to automate detection, response, and remediation for NHI-related risks, including token revocation and integration quarantine., Conduct **regular audits** of NHI permissions and usage context. Classify NHIs by type (e.g., integrations, AI assistants, RPA bots) to tailor risk controls appropriately., Educate teams on the risks of NHIs and integrate NHI security into broader **identity and access management (IAM)** strategies.Implement **unified visibility** of all non-human identities (OAuth apps, API keys, service accounts, bots) across SaaS applications using automated discovery tools., Enforce **least privilege** for NHIs by auditing and restricting overly permissive access scopes. Ensure integrations and tokens can only access the data they explicitly require., Deploy **continuous anomaly monitoring** to detect deviations in NHI behavior (e.g., unusual access times, data volumes, or locations). Baseline normal activity and flag anomalies in real time., Automate **credential rotation and expiration** for all NHIs. Use platforms that detect stale tokens, rotate secrets regularly, and disable unused credentials., Apply **compensating controls** for NHIs where MFA is not feasible (e.g., IP restrictions, scoped access, session monitoring)., Maintain a **real-time inventory** of third-party integrations, especially those connected via user consent (OAuth), and verify their legitimacy and security posture., Disable **orphaned or ghost NHIs** (credentials not tied to active workflows or users), as these are prime targets for attackers., Leverage **Dynamic SaaS Security Platforms** (e.g., Reco) to automate detection, response, and remediation for NHI-related risks, including token revocation and integration quarantine., Conduct **regular audits** of NHI permissions and usage context. Classify NHIs by type (e.g., integrations, AI assistants, RPA bots) to tailor risk controls appropriately., Educate teams on the risks of NHIs and integrate NHI security into broader **identity and access management (IAM)** strategies.Implement **unified visibility** of all non-human identities (OAuth apps, API keys, service accounts, bots) across SaaS applications using automated discovery tools., Enforce **least privilege** for NHIs by auditing and restricting overly permissive access scopes. Ensure integrations and tokens can only access the data they explicitly require., Deploy **continuous anomaly monitoring** to detect deviations in NHI behavior (e.g., unusual access times, data volumes, or locations). Baseline normal activity and flag anomalies in real time., Automate **credential rotation and expiration** for all NHIs. Use platforms that detect stale tokens, rotate secrets regularly, and disable unused credentials., Apply **compensating controls** for NHIs where MFA is not feasible (e.g., IP restrictions, scoped access, session monitoring)., Maintain a **real-time inventory** of third-party integrations, especially those connected via user consent (OAuth), and verify their legitimacy and security posture., Disable **orphaned or ghost NHIs** (credentials not tied to active workflows or users), as these are prime targets for attackers., Leverage **Dynamic SaaS Security Platforms** (e.g., Reco) to automate detection, response, and remediation for NHI-related risks, including token revocation and integration quarantine., Conduct **regular audits** of NHI permissions and usage context. Classify NHIs by type (e.g., integrations, AI assistants, RPA bots) to tailor risk controls appropriately., Educate teams on the risks of NHIs and integrate NHI security into broader **identity and access management (IAM)** strategies.Implement **unified visibility** of all non-human identities (OAuth apps, API keys, service accounts, bots) across SaaS applications using automated discovery tools., Enforce **least privilege** for NHIs by auditing and restricting overly permissive access scopes. Ensure integrations and tokens can only access the data they explicitly require., Deploy **continuous anomaly monitoring** to detect deviations in NHI behavior (e.g., unusual access times, data volumes, or locations). Baseline normal activity and flag anomalies in real time., Automate **credential rotation and expiration** for all NHIs. Use platforms that detect stale tokens, rotate secrets regularly, and disable unused credentials., Apply **compensating controls** for NHIs where MFA is not feasible (e.g., IP restrictions, scoped access, session monitoring)., Maintain a **real-time inventory** of third-party integrations, especially those connected via user consent (OAuth), and verify their legitimacy and security posture., Disable **orphaned or ghost NHIs** (credentials not tied to active workflows or users), as these are prime targets for attackers., Leverage **Dynamic SaaS Security Platforms** (e.g., Reco) to automate detection, response, and remediation for NHI-related risks, including token revocation and integration quarantine., Conduct **regular audits** of NHI permissions and usage context. Classify NHIs by type (e.g., integrations, AI assistants, RPA bots) to tailor risk controls appropriately., Educate teams on the risks of NHIs and integrate NHI security into broader **identity and access management (IAM)** strategies.Implement **unified visibility** of all non-human identities (OAuth apps, API keys, service accounts, bots) across SaaS applications using automated discovery tools., Enforce **least privilege** for NHIs by auditing and restricting overly permissive access scopes. Ensure integrations and tokens can only access the data they explicitly require., Deploy **continuous anomaly monitoring** to detect deviations in NHI behavior (e.g., unusual access times, data volumes, or locations). Baseline normal activity and flag anomalies in real time., Automate **credential rotation and expiration** for all NHIs. Use platforms that detect stale tokens, rotate secrets regularly, and disable unused credentials., Apply **compensating controls** for NHIs where MFA is not feasible (e.g., IP restrictions, scoped access, session monitoring)., Maintain a **real-time inventory** of third-party integrations, especially those connected via user consent (OAuth), and verify their legitimacy and security posture., Disable **orphaned or ghost NHIs** (credentials not tied to active workflows or users), as these are prime targets for attackers., Leverage **Dynamic SaaS Security Platforms** (e.g., Reco) to automate detection, response, and remediation for NHI-related risks, including token revocation and integration quarantine., Conduct **regular audits** of NHI permissions and usage context. Classify NHIs by type (e.g., integrations, AI assistants, RPA bots) to tailor risk controls appropriately., Educate teams on the risks of NHIs and integrate NHI security into broader **identity and access management (IAM)** strategies.Implement **unified visibility** of all non-human identities (OAuth apps, API keys, service accounts, bots) across SaaS applications using automated discovery tools., Enforce **least privilege** for NHIs by auditing and restricting overly permissive access scopes. Ensure integrations and tokens can only access the data they explicitly require., Deploy **continuous anomaly monitoring** to detect deviations in NHI behavior (e.g., unusual access times, data volumes, or locations). Baseline normal activity and flag anomalies in real time., Automate **credential rotation and expiration** for all NHIs. Use platforms that detect stale tokens, rotate secrets regularly, and disable unused credentials., Apply **compensating controls** for NHIs where MFA is not feasible (e.g., IP restrictions, scoped access, session monitoring)., Maintain a **real-time inventory** of third-party integrations, especially those connected via user consent (OAuth), and verify their legitimacy and security posture., Disable **orphaned or ghost NHIs** (credentials not tied to active workflows or users), as these are prime targets for attackers., Leverage **Dynamic SaaS Security Platforms** (e.g., Reco) to automate detection, response, and remediation for NHI-related risks, including token revocation and integration quarantine., Conduct **regular audits** of NHI permissions and usage context. Classify NHIs by type (e.g., integrations, AI assistants, RPA bots) to tailor risk controls appropriately., Educate teams on the risks of NHIs and integrate NHI security into broader **identity and access management (IAM)** strategies.Implement **unified visibility** of all non-human identities (OAuth apps, API keys, service accounts, bots) across SaaS applications using automated discovery tools., Enforce **least privilege** for NHIs by auditing and restricting overly permissive access scopes. Ensure integrations and tokens can only access the data they explicitly require., Deploy **continuous anomaly monitoring** to detect deviations in NHI behavior (e.g., unusual access times, data volumes, or locations). Baseline normal activity and flag anomalies in real time., Automate **credential rotation and expiration** for all NHIs. Use platforms that detect stale tokens, rotate secrets regularly, and disable unused credentials., Apply **compensating controls** for NHIs where MFA is not feasible (e.g., IP restrictions, scoped access, session monitoring)., Maintain a **real-time inventory** of third-party integrations, especially those connected via user consent (OAuth), and verify their legitimacy and security posture., Disable **orphaned or ghost NHIs** (credentials not tied to active workflows or users), as these are prime targets for attackers., Leverage **Dynamic SaaS Security Platforms** (e.g., Reco) to automate detection, response, and remediation for NHI-related risks, including token revocation and integration quarantine., Conduct **regular audits** of NHI permissions and usage context. Classify NHIs by type (e.g., integrations, AI assistants, RPA bots) to tailor risk controls appropriately., Educate teams on the risks of NHIs and integrate NHI security into broader **identity and access management (IAM)** strategies.Implement **unified visibility** of all non-human identities (OAuth apps, API keys, service accounts, bots) across SaaS applications using automated discovery tools., Enforce **least privilege** for NHIs by auditing and restricting overly permissive access scopes. Ensure integrations and tokens can only access the data they explicitly require., Deploy **continuous anomaly monitoring** to detect deviations in NHI behavior (e.g., unusual access times, data volumes, or locations). Baseline normal activity and flag anomalies in real time., Automate **credential rotation and expiration** for all NHIs. Use platforms that detect stale tokens, rotate secrets regularly, and disable unused credentials., Apply **compensating controls** for NHIs where MFA is not feasible (e.g., IP restrictions, scoped access, session monitoring)., Maintain a **real-time inventory** of third-party integrations, especially those connected via user consent (OAuth), and verify their legitimacy and security posture., Disable **orphaned or ghost NHIs** (credentials not tied to active workflows or users), as these are prime targets for attackers., Leverage **Dynamic SaaS Security Platforms** (e.g., Reco) to automate detection, response, and remediation for NHI-related risks, including token revocation and integration quarantine., Conduct **regular audits** of NHI permissions and usage context. Classify NHIs by type (e.g., integrations, AI assistants, RPA bots) to tailor risk controls appropriately., Educate teams on the risks of NHIs and integrate NHI security into broader **identity and access management (IAM)** strategies.

Recommendations: Immediate patching of CVE-2025-61882 for Oracle EBS versions 12.2.3–12.2.14, Monitor for indicators of compromise (IOCs) linked to Clop’s infrastructure (e.g., 96 IPs, support@pubstorm[.]com), Enhance authentication mechanisms for OA_HTML endpoints, Segment networks to limit lateral movement, Implement behavioral analysis for XSLT injection attemptsImmediate patching of CVE-2025-61882 for Oracle EBS versions 12.2.3–12.2.14, Monitor for indicators of compromise (IOCs) linked to Clop’s infrastructure (e.g., 96 IPs, support@pubstorm[.]com), Enhance authentication mechanisms for OA_HTML endpoints, Segment networks to limit lateral movement, Implement behavioral analysis for XSLT injection attemptsImmediate patching of CVE-2025-61882 for Oracle EBS versions 12.2.3–12.2.14, Monitor for indicators of compromise (IOCs) linked to Clop’s infrastructure (e.g., 96 IPs, support@pubstorm[.]com), Enhance authentication mechanisms for OA_HTML endpoints, Segment networks to limit lateral movement, Implement behavioral analysis for XSLT injection attemptsImmediate patching of CVE-2025-61882 for Oracle EBS versions 12.2.3–12.2.14, Monitor for indicators of compromise (IOCs) linked to Clop’s infrastructure (e.g., 96 IPs, support@pubstorm[.]com), Enhance authentication mechanisms for OA_HTML endpoints, Segment networks to limit lateral movement, Implement behavioral analysis for XSLT injection attemptsImmediate patching of CVE-2025-61882 for Oracle EBS versions 12.2.3–12.2.14, Monitor for indicators of compromise (IOCs) linked to Clop’s infrastructure (e.g., 96 IPs, support@pubstorm[.]com), Enhance authentication mechanisms for OA_HTML endpoints, Segment networks to limit lateral movement, Implement behavioral analysis for XSLT injection attempts

Recommendations: Immediate patching of critical vulnerabilities (e.g., CVE-2025-61882)., Adoption of zero-trust architectures and multi-factor authentication (MFA)., Enhanced vulnerability scanning and threat hunting capabilities., Network segmentation to limit lateral movement., Regular employee training on phishing and social engineering., Collaboration with vendors (e.g., Oracle) for out-of-band patches., Proactive dark web monitoring for leaked data., Investment in AI-driven anomaly detection systems., International cooperation for cross-border cybercrime investigations.Immediate patching of critical vulnerabilities (e.g., CVE-2025-61882)., Adoption of zero-trust architectures and multi-factor authentication (MFA)., Enhanced vulnerability scanning and threat hunting capabilities., Network segmentation to limit lateral movement., Regular employee training on phishing and social engineering., Collaboration with vendors (e.g., Oracle) for out-of-band patches., Proactive dark web monitoring for leaked data., Investment in AI-driven anomaly detection systems., International cooperation for cross-border cybercrime investigations.Immediate patching of critical vulnerabilities (e.g., CVE-2025-61882)., Adoption of zero-trust architectures and multi-factor authentication (MFA)., Enhanced vulnerability scanning and threat hunting capabilities., Network segmentation to limit lateral movement., Regular employee training on phishing and social engineering., Collaboration with vendors (e.g., Oracle) for out-of-band patches., Proactive dark web monitoring for leaked data., Investment in AI-driven anomaly detection systems., International cooperation for cross-border cybercrime investigations.Immediate patching of critical vulnerabilities (e.g., CVE-2025-61882)., Adoption of zero-trust architectures and multi-factor authentication (MFA)., Enhanced vulnerability scanning and threat hunting capabilities., Network segmentation to limit lateral movement., Regular employee training on phishing and social engineering., Collaboration with vendors (e.g., Oracle) for out-of-band patches., Proactive dark web monitoring for leaked data., Investment in AI-driven anomaly detection systems., International cooperation for cross-border cybercrime investigations.Immediate patching of critical vulnerabilities (e.g., CVE-2025-61882)., Adoption of zero-trust architectures and multi-factor authentication (MFA)., Enhanced vulnerability scanning and threat hunting capabilities., Network segmentation to limit lateral movement., Regular employee training on phishing and social engineering., Collaboration with vendors (e.g., Oracle) for out-of-band patches., Proactive dark web monitoring for leaked data., Investment in AI-driven anomaly detection systems., International cooperation for cross-border cybercrime investigations.Immediate patching of critical vulnerabilities (e.g., CVE-2025-61882)., Adoption of zero-trust architectures and multi-factor authentication (MFA)., Enhanced vulnerability scanning and threat hunting capabilities., Network segmentation to limit lateral movement., Regular employee training on phishing and social engineering., Collaboration with vendors (e.g., Oracle) for out-of-band patches., Proactive dark web monitoring for leaked data., Investment in AI-driven anomaly detection systems., International cooperation for cross-border cybercrime investigations.Immediate patching of critical vulnerabilities (e.g., CVE-2025-61882)., Adoption of zero-trust architectures and multi-factor authentication (MFA)., Enhanced vulnerability scanning and threat hunting capabilities., Network segmentation to limit lateral movement., Regular employee training on phishing and social engineering., Collaboration with vendors (e.g., Oracle) for out-of-band patches., Proactive dark web monitoring for leaked data., Investment in AI-driven anomaly detection systems., International cooperation for cross-border cybercrime investigations.Immediate patching of critical vulnerabilities (e.g., CVE-2025-61882)., Adoption of zero-trust architectures and multi-factor authentication (MFA)., Enhanced vulnerability scanning and threat hunting capabilities., Network segmentation to limit lateral movement., Regular employee training on phishing and social engineering., Collaboration with vendors (e.g., Oracle) for out-of-band patches., Proactive dark web monitoring for leaked data., Investment in AI-driven anomaly detection systems., International cooperation for cross-border cybercrime investigations.Immediate patching of critical vulnerabilities (e.g., CVE-2025-61882)., Adoption of zero-trust architectures and multi-factor authentication (MFA)., Enhanced vulnerability scanning and threat hunting capabilities., Network segmentation to limit lateral movement., Regular employee training on phishing and social engineering., Collaboration with vendors (e.g., Oracle) for out-of-band patches., Proactive dark web monitoring for leaked data., Investment in AI-driven anomaly detection systems., International cooperation for cross-border cybercrime investigations.

Recommendations: Apply Oracle security patches for CVE-2025-61882 and CVE-2025-21884 immediately., Implement supply chain risk management (SCRM) tools to assess third-party vendor vulnerabilities (e.g., Z2Data)., Enhance monitoring for unauthenticated HTTP requests targeting Oracle EBS components., Conduct regular audits of enterprise software for zero-day vulnerabilities., Develop and test incident response plans for ransomware attacks, including data exfiltration scenarios., Evaluate the need for network segmentation to limit lateral movement in case of breaches.Apply Oracle security patches for CVE-2025-61882 and CVE-2025-21884 immediately., Implement supply chain risk management (SCRM) tools to assess third-party vendor vulnerabilities (e.g., Z2Data)., Enhance monitoring for unauthenticated HTTP requests targeting Oracle EBS components., Conduct regular audits of enterprise software for zero-day vulnerabilities., Develop and test incident response plans for ransomware attacks, including data exfiltration scenarios., Evaluate the need for network segmentation to limit lateral movement in case of breaches.Apply Oracle security patches for CVE-2025-61882 and CVE-2025-21884 immediately., Implement supply chain risk management (SCRM) tools to assess third-party vendor vulnerabilities (e.g., Z2Data)., Enhance monitoring for unauthenticated HTTP requests targeting Oracle EBS components., Conduct regular audits of enterprise software for zero-day vulnerabilities., Develop and test incident response plans for ransomware attacks, including data exfiltration scenarios., Evaluate the need for network segmentation to limit lateral movement in case of breaches.Apply Oracle security patches for CVE-2025-61882 and CVE-2025-21884 immediately., Implement supply chain risk management (SCRM) tools to assess third-party vendor vulnerabilities (e.g., Z2Data)., Enhance monitoring for unauthenticated HTTP requests targeting Oracle EBS components., Conduct regular audits of enterprise software for zero-day vulnerabilities., Develop and test incident response plans for ransomware attacks, including data exfiltration scenarios., Evaluate the need for network segmentation to limit lateral movement in case of breaches.Apply Oracle security patches for CVE-2025-61882 and CVE-2025-21884 immediately., Implement supply chain risk management (SCRM) tools to assess third-party vendor vulnerabilities (e.g., Z2Data)., Enhance monitoring for unauthenticated HTTP requests targeting Oracle EBS components., Conduct regular audits of enterprise software for zero-day vulnerabilities., Develop and test incident response plans for ransomware attacks, including data exfiltration scenarios., Evaluate the need for network segmentation to limit lateral movement in case of breaches.Apply Oracle security patches for CVE-2025-61882 and CVE-2025-21884 immediately., Implement supply chain risk management (SCRM) tools to assess third-party vendor vulnerabilities (e.g., Z2Data)., Enhance monitoring for unauthenticated HTTP requests targeting Oracle EBS components., Conduct regular audits of enterprise software for zero-day vulnerabilities., Develop and test incident response plans for ransomware attacks, including data exfiltration scenarios., Evaluate the need for network segmentation to limit lateral movement in case of breaches.

Recommendations: Sign up for free IDX identity theft protection services, Monitor financial statements for suspicious activity, Request a fraud alert or credit report from major credit bureaus, Seek legal help to understand rights and pursue compensationSign up for free IDX identity theft protection services, Monitor financial statements for suspicious activity, Request a fraud alert or credit report from major credit bureaus, Seek legal help to understand rights and pursue compensationSign up for free IDX identity theft protection services, Monitor financial statements for suspicious activity, Request a fraud alert or credit report from major credit bureaus, Seek legal help to understand rights and pursue compensationSign up for free IDX identity theft protection services, Monitor financial statements for suspicious activity, Request a fraud alert or credit report from major credit bureaus, Seek legal help to understand rights and pursue compensation

Recommendations: Implement more centralized IT control to reduce vulnerabilities from decentralized departments., Enhance cybersecurity training and awareness programs, focusing on non-punitive approaches., Limit data retention to reduce the risk of exposure (e.g., avoid storing unnecessary sensitive data like Social Security numbers)., Foster partnerships between IT, security teams, and faculty to align research needs with cybersecurity protocols., Adopt adaptive security measures like behavioral WAFs and enhanced monitoring to detect and respond to threats more effectively.Implement more centralized IT control to reduce vulnerabilities from decentralized departments., Enhance cybersecurity training and awareness programs, focusing on non-punitive approaches., Limit data retention to reduce the risk of exposure (e.g., avoid storing unnecessary sensitive data like Social Security numbers)., Foster partnerships between IT, security teams, and faculty to align research needs with cybersecurity protocols., Adopt adaptive security measures like behavioral WAFs and enhanced monitoring to detect and respond to threats more effectively.Implement more centralized IT control to reduce vulnerabilities from decentralized departments., Enhance cybersecurity training and awareness programs, focusing on non-punitive approaches., Limit data retention to reduce the risk of exposure (e.g., avoid storing unnecessary sensitive data like Social Security numbers)., Foster partnerships between IT, security teams, and faculty to align research needs with cybersecurity protocols., Adopt adaptive security measures like behavioral WAFs and enhanced monitoring to detect and respond to threats more effectively.Implement more centralized IT control to reduce vulnerabilities from decentralized departments., Enhance cybersecurity training and awareness programs, focusing on non-punitive approaches., Limit data retention to reduce the risk of exposure (e.g., avoid storing unnecessary sensitive data like Social Security numbers)., Foster partnerships between IT, security teams, and faculty to align research needs with cybersecurity protocols., Adopt adaptive security measures like behavioral WAFs and enhanced monitoring to detect and respond to threats more effectively.Implement more centralized IT control to reduce vulnerabilities from decentralized departments., Enhance cybersecurity training and awareness programs, focusing on non-punitive approaches., Limit data retention to reduce the risk of exposure (e.g., avoid storing unnecessary sensitive data like Social Security numbers)., Foster partnerships between IT, security teams, and faculty to align research needs with cybersecurity protocols., Adopt adaptive security measures like behavioral WAFs and enhanced monitoring to detect and respond to threats more effectively.

Recommendations: Apply patches from Oracle's Critical Patch Update (CPU) and restrict network access to affected HTTP ports if immediate patching is not possible.

Recommendations: Implement mandatory cybersecurity training, strengthen defenses against future attacks

Recommendations: Secure exposed Docker APIs, Kubernetes clusters, and Ray dashboards, Implement strict access controls and secrets management, Monitor for leaked credentials and misconfigurations, Enhance detection of automated exploitation attempts, Segment cloud networks to limit lateral movementSecure exposed Docker APIs, Kubernetes clusters, and Ray dashboards, Implement strict access controls and secrets management, Monitor for leaked credentials and misconfigurations, Enhance detection of automated exploitation attempts, Segment cloud networks to limit lateral movementSecure exposed Docker APIs, Kubernetes clusters, and Ray dashboards, Implement strict access controls and secrets management, Monitor for leaked credentials and misconfigurations, Enhance detection of automated exploitation attempts, Segment cloud networks to limit lateral movementSecure exposed Docker APIs, Kubernetes clusters, and Ray dashboards, Implement strict access controls and secrets management, Monitor for leaked credentials and misconfigurations, Enhance detection of automated exploitation attempts, Segment cloud networks to limit lateral movementSecure exposed Docker APIs, Kubernetes clusters, and Ray dashboards, Implement strict access controls and secrets management, Monitor for leaked credentials and misconfigurations, Enhance detection of automated exploitation attempts, Segment cloud networks to limit lateral movement

Recommendations: Acknowledge breaches, implement security measures, collaborate with cybersecurity firms, and notify stakeholders proactively.

Recommendations: Immediate patch deployment (KB878741), upgrade to supported releases if running end-of-life software
Key Lessons Learned: The key lessons learned from past incidents are Malvertising is an effective initial access vector for targeted phishing campaigns.,MFA bypass techniques (e.g., real-time OTP capture) undermine traditional authentication methods.,Typosquatted domains and convincing phishing pages can evade user scrutiny.,Russian-speaking threat actors continue to leverage proxy infrastructure for anonymity.,Hospitality industry is a high-value target due to sensitive guest data and payment systems.Zero-day vulnerabilities in widely used enterprise software like Oracle E-Business Suite can lead to rapid, high-impact exploitation by multiple threat actors. Organizations must prioritize patch management and assume breach scenarios even after patching, given the likelihood of prior compromise during mass exploitation campaigns.Zero-day vulnerabilities in enterprise software like Oracle EBS are high-value targets for ransomware groups.,Public PoC disclosures accelerate exploitation by multiple threat actors.,Proactive patching and exposure management are critical for mitigating RCE risks.Zero-day vulnerabilities in widely used enterprise software can lead to large-scale data breaches. Proactive patch management and monitoring for unusual network activity are critical. Vendors must ensure transparent communication during ongoing incidents to avoid misinformation.Critical Importance of Timely Patching for Public-Facing Applications,Risks of Zero-Day Exploitation in Enterprise Software,Need for Enhanced Monitoring of Oracle EBS Instances,Potential for Mass Extortion Campaigns Leveraging Stolen CredentialsProactive vulnerability management is critical for enterprise software (Oracle).,Zero-day exploits underscore the need for rapid patch deployment (Microsoft).,Nation-state threats target high-value intellectual property (F5).,Misconfigurations in enterprise software remain a top attack vector (Adobe).,Certificate abuse highlights risks in software supply chains (Microsoft Teams).,Network device vulnerabilities can enable persistent rootkit infections (Cisco).,Cryptocurrency fraud operations require cross-agency coordination (DOJ).,IoT/robotics security lags behind espionage risks (Unitree G1).,Healthcare cybersecurity gaps directly impact patient safety (Proofpoint).Non-human identities (NHIs) such as OAuth tokens, API keys, and service accounts are high-value targets for attackers due to their broad privileges and lack of oversight. Organizations must extend identity security controls to include NHIs, not just human users.,Publicly exposed API tokens can act as unguarded backdoors, granting attackers direct access to sensitive systems without needing to bypass interactive login protections. Token hygiene (e.g., avoiding public exposure, enforcing least privilege) is critical.,Orphaned or unrotated service credentials can undermine incident response efforts. Even after rotating human credentials, overlooked NHIs can provide attackers with persistent access. Comprehensive credential rotation must include all identities—human and non-human.,Dynamic SaaS Security Platforms are essential for discovering, monitoring, and securing NHIs. Traditional identity controls are insufficient for the scale and complexity of machine identities in modern SaaS environments.Zero-day exploits in ERP systems pose severe risks due to their central role in operations.,Delayed detection (weeks between breach and discovery) exacerbates impact.,Supply chain vulnerabilities (e.g., Oracle software) require proactive patch management.,Ransomware-as-a-Service (RaaS) models enable scalable, sophisticated attacks.,Public disclosure strategies must balance transparency with investigative integrity.Supplier vulnerabilities in enterprise software (e.g., Oracle EBS) can cascade into large-scale breaches across industries. Proactive patch management and supply chain risk monitoring (e.g., via SCRM platforms like Z2Data) are critical to mitigating third-party risks. Cl0p’s delayed data leak strategy highlights the importance of rapid incident response to prevent public exposure of sensitive data.Universities are highly vulnerable to cyberattacks due to decentralized IT structures, lack of centralized control, and human error. Cybersecurity training and awareness are critical but not sufficient alone. There is a need for better collaboration between IT departments and faculty to balance security with academic freedom.Ransomware has evolved into a systemic risk with cascading impacts on supply chains, critical services, and industries. Initial access often relies on stolen credentials or social engineering, and supply chain vulnerabilities amplify the impact. Data theft and operational paralysis are primary damage drivers, with delayed consequences such as regulatory penalties or human harm.Limited scope of breach despite initial claims, need for improved cybersecurity measuresThe incident underscores the risks of unsecured cloud control planes, leaked credentials, and poor access controls, highlighting the need for robust cloud security practices.Highlights risks tied to third-party software vulnerabilities, particularly in widely used enterprise systems like Oracle EBSTransparent communication is increasingly seen as a corporate obligation for stakeholder trust and legal compliance.
Implemented Recommendations: The company has implemented the following recommendations to improve cybersecurity: International cooperation for cross-border cybercrime investigations., Collaboration with vendors (e.g., Oracle) for out-of-band patches., Monitor for Signs of Exploitation (e.g., Unusual Database Activity, Extortion Emails), Apply patches from Oracle's Critical Patch Update (CPU) and restrict network access to affected HTTP ports if immediate patching is not possible., Regular employee training on phishing and social engineering., Educate employees about phishing and extortion email tactics., Conduct regular security audits for enterprise software., Engage Third-Party Threat Intelligence for Indicators of Compromise (IOCs), Acknowledge breaches, implement security measures, collaborate with cybersecurity firms, and notify stakeholders proactively., Assess potential links to FIN11/Clop ransomware activity, Immediately apply Oracle's emergency patch for CVE-2025-61882., Apply Oracle Security Alerts and Critical Patch Updates Immediately, Investment in AI-driven anomaly detection systems., Immediately patch Oracle E-Business Suite to the latest version., Enhanced vulnerability scanning and threat hunting capabilities., Immediate patch deployment (KB878741), upgrade to supported releases if running end-of-life software, Monitor networks for indicators of compromise (IoCs) provided by Google., Investigate Oracle E-Business Suite environments for unusual access or compromise, Conduct forensic investigations to detect signs of prior exploitation., Review and Secure Default Password Reset Mechanisms, Implement multi-factor authentication (MFA) for all critical systems., Immediate patching of critical vulnerabilities (e.g., CVE-2025-61882)., Proactive dark web monitoring for leaked data., Segment Networks to Limit Lateral Movement, Network segmentation to limit lateral movement., Implement mandatory cybersecurity training, strengthen defenses against future attacks, Implement Multi-Factor Authentication (MFA) for Oracle EBS, Monitor for high-volume extortion email campaigns from compromised accounts, Review Mandiant's advisory for additional mitigation strategies., Adoption of zero-trust architectures and multi-factor authentication (MFA)., Enhance logging and network segmentation for Oracle EBS environments., Monitor for IoCs, including the listed IP addresses (200.107.207[.]26 and 185.181.60[.]11) and exploit artifacts..

Source: Cyber Incident Description

Source: California Office of the Attorney General

Source: Okta Threat Intelligence (contributor: Moussa Diallo)

Source: BleepingComputer

Source: Mandiant (Google Cloud) & GTIG Analysis

Source: U.S. State Department Rewards for Justice Program (Clop)

Source: CISA Advisory (January 2023 Oracle Incident)

Source: Emsisoft (MOVEit Impact Report)

Source: Mandiant (Google Cloud) Alert on Cl0p Campaign
Date Accessed: 2025-08

Source: LinkedIn Post by Charles Carmakal (Mandiant CTO)
Date Accessed: 2025-08

Source: Oracle Security Advisory (Rob Duhart, CSO)
Date Accessed: 2025-10-02

Source: Google Mandiant (Charles Carmakal, CTO) - LinkedIn Post
Date Accessed: 2025-10-02

Source: Oracle Security Alert (CVE-2025-61882)
Date Accessed: 2025-10-05

Source: watchTowr Labs (PoC Analysis)
Date Accessed: 2025-05-01

Source: U.S. State Department Reward Program

Source: TechCrunch
URL: https://techcrunch.com/2023/10/05/google-clop-oracle-zero-day-hack/
Date Accessed: 2023-10-05

Source: Google Blog Post
URL: https://blog.google/threat-analysis-group/clop-oracle-zero-day/
Date Accessed: 2023-10-05

Source: Oracle Security Advisory
URL: https://www.oracle.com/security-alerts/
Date Accessed: 2023-10-05

Source: SecurityAffairs
URL: https://securityaffairs.co/wordpress/150000/hacking/oracle-ebs-flaw-cve-2025-61884.html
Date Accessed: 2025-10-14

Source: Oracle Security Alert Advisory
Date Accessed: 2025-10-14

Source: Google Threat Intelligence & Mandiant Analysis
Date Accessed: 2025-10-03

Source: CrowdStrike Report on CVE-2025-61882 Exploitation
Date Accessed: 2025-10-03

Source: Microsoft Security Update Guide
URL: https://msrc.microsoft.com/update-guide
Date Accessed: 2025-10-01

Source: CISA KEV Catalog
URL: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Date Accessed: 2025-10-01

Source: Microsoft Security Blog (Vanilla Tempest)
Date Accessed: 2025-10-01

Source: Cisco Security Advisory (CVE-2025-20352)
Date Accessed: 2025-10-01

Source: U.S. Department of Justice Press Release
Date Accessed: 2025-10-01

Source: Alias Robotics Unitree G1 Analysis
Date Accessed: 2025-10-01

Source: Proofpoint 2025 Healthcare IT Report
Date Accessed: 2025-10-01

Source: Reco Blog: 'The Hidden Risk of Non-Human Identities in SaaS'

Source: Author: Gal Nakash (CPO and Cofounder, Reco)

Source: The Register

Source: THE RAVEN FILE Security Researchers

Source: Clop Ransomware Dark Web Leak Site

Source: Oracle Security Alert (October 2025)

Source: THE RAVEN FILE (Security Research)

Source: Clop Dark Web Leak Site

Source: Oracle Security Advisory (CVE-2025-61882)

Source: BleepingComputer

Source: Maine Attorney General’s Office (Breach Notification)

Source: IBM Cost of a Data Breach Report

Source: U.S. Cybersecurity and Infrastructure Security Agency (CISA)

Source: UK National Cyber Security Centre (NCSC)

Source: Mandiant (Google-owned cybersecurity firm)

Source: Oracle Security Alerts (CVE-2025-61882, CVE-2025-21884)

Source: Z2Data Supplier Risk Analysis

Source: Attorney General of the Commonwealth of Massachusetts

Source: BleepingComputer

Source: University of Phoenix Official Website

Source: SEC Filing (8-K)

Source: Shamis & Gentile P.A.

Source: The Independent

Source: Cybersecurity Ventures

Source: Chronicle of Higher Education

Source: Oracle Critical Patch Update (CPU)

Source: SOCRadar analysis

Source: Cybersecurity Ventures

Source: Cloudflare 2025 Q4 DDoS Threat Report

Source: Legal filing in U.S. Eastern District Court

Source: Incident disclosure by SUNY Research Foundation

Source: Flare (security firm)

Source: TeamPCP Telegram channel

Source: Maine Attorney General’s Office

Source: The Register

Source: Edelson Lechtzin LLP

Source: Lynch Carpenter, LLP

Source: Dark web post by CL0P ransomware group

Source: Distributed Denial of Secrets

Source: Michelin Public Statement

Source: DarkWeb Informer forum (threat actor 'igotafeeling')

Source: Loblaw Press Release (March 12)

Source: Hypertherm, Inc. Breach Notification

Source: Hypertherm breach notification

Source: Incident Report

Source: Oracle Security Alert
Additional Resources: Stakeholders can find additional resources on cybersecurity best practices at and Source: Cyber Incident Description, and Source: California Office of the Attorney General, and Source: Okta Threat Intelligence (contributor: Moussa Diallo), and Source: BleepingComputer, and Source: Mandiant (Google Cloud) & GTIG Analysis, and Source: U.S. State Department Rewards for Justice Program (Clop)Url: https://www.state.gov/rewards-for-justice-program/, and Source: Recorded Future NewsDate Accessed: 2023-10-04, and Source: Mandiant/GTIG WarningDate Accessed: 2023-10-04, and Source: CISA Advisory (January 2023 Oracle Incident)Url: https://www.cisa.gov/, and Source: Emsisoft (MOVEit Impact Report), and Source: Oracle Security AdvisoryDate Accessed: 2025-08, and Source: Mandiant (Google Cloud) Alert on Cl0p CampaignDate Accessed: 2025-08, and Source: LinkedIn Post by Charles Carmakal (Mandiant CTO)Date Accessed: 2025-08, and Source: Oracle Security Advisory (Rob Duhart, CSO)Date Accessed: 2025-10-02, and Source: Google Mandiant (Charles Carmakal, CTO) - LinkedIn PostDate Accessed: 2025-10-02, and Source: CrowdStrike BlogDate Accessed: 2025-10-07, and Source: BleepingComputer ArticleDate Accessed: 2025-10-06, and Source: Oracle Security Alert (CVE-2025-61882)Date Accessed: 2025-10-05, and Source: watchTowr Labs (PoC Analysis)Date Accessed: 2025-05-01, and Source: U.S. State Department Reward Program, and Source: TechCrunchUrl: https://techcrunch.com/2023/10/05/google-clop-oracle-zero-day-hack/Date Accessed: 2023-10-05, and Source: Google Blog PostUrl: https://blog.google/threat-analysis-group/clop-oracle-zero-day/Date Accessed: 2023-10-05, and Source: Oracle Security AdvisoryUrl: https://www.oracle.com/security-alerts/Date Accessed: 2023-10-05, and Source: SecurityAffairsUrl: https://securityaffairs.co/wordpress/150000/hacking/oracle-ebs-flaw-cve-2025-61884.htmlDate Accessed: 2025-10-14, and Source: Oracle Security Alert AdvisoryDate Accessed: 2025-10-14, and Source: Google Threat Intelligence & Mandiant AnalysisDate Accessed: 2025-10-03, and Source: CrowdStrike Report on CVE-2025-61882 ExploitationDate Accessed: 2025-10-03, and Source: Help Net SecurityDate Accessed: 2025-10-14, and Source: Oracle Security AlertDate Accessed: 2025-10-01, and Source: Microsoft Security Update GuideUrl: https://msrc.microsoft.com/update-guideDate Accessed: 2025-10-01, and Source: F5 Security AdvisoryDate Accessed: 2025-10-01, and Source: CISA KEV CatalogUrl: https://www.cisa.gov/known-exploited-vulnerabilities-catalogDate Accessed: 2025-10-01, and Source: Microsoft Security Blog (Vanilla Tempest)Date Accessed: 2025-10-01, and Source: Cisco Security Advisory (CVE-2025-20352)Date Accessed: 2025-10-01, and Source: U.S. Department of Justice Press ReleaseDate Accessed: 2025-10-01, and Source: Alias Robotics Unitree G1 AnalysisDate Accessed: 2025-10-01, and Source: Proofpoint 2025 Healthcare IT ReportDate Accessed: 2025-10-01, and Source: Reco Blog: 'The Hidden Risk of Non-Human Identities in SaaS', and Source: Author: Gal Nakash (CPO and Cofounder, Reco), and Source: The Register, and Source: THE RAVEN FILE Security Researchers, and Source: Clop Ransomware Dark Web Leak Site, and Source: Oracle Security Alert (October 2025), and Source: THE RAVEN FILE (Security Research), and Source: Clop Dark Web Leak Site, and Source: Oracle Security Advisory (CVE-2025-61882), and Source: BleepingComputerUrl: https://www.bleepingcomputer.com, and Source: SecurityWeekUrl: https://www.securityweek.com, and Source: The Hacker NewsUrl: https://thehackernews.com, and Source: TechRadarUrl: https://www.techradar.com, and Source: Bloomberg LawUrl: https://news.bloomberglaw.com, and Source: Maine Attorney General’s Office (Breach Notification), and Source: CISA AlertsUrl: https://www.cisa.gov, and Source: IBM Cost of a Data Breach ReportUrl: https://www.ibm.com/reports/data-breach, and Source: U.S. Cybersecurity and Infrastructure Security Agency (CISA), and Source: UK National Cyber Security Centre (NCSC), and Source: Mandiant (Google-owned cybersecurity firm), and Source: Oracle Security Alerts (CVE-2025-61882, CVE-2025-21884), and Source: Z2Data Supplier Risk AnalysisUrl: https://www.z2data.com, and Source: Attorney General of the Commonwealth of Massachusetts, and Source: BleepingComputer, and Source: University of Phoenix Official Website, and Source: SEC Filing (8-K), and Source: Shamis & Gentile P.A., and Source: The Independent, and Source: Cybersecurity Ventures, and Source: Chronicle of Higher Education, and Source: Oracle Critical Patch Update (CPU), and Source: SOCRadar analysis, and Source: Cybersecurity Ventures, and Source: Cloudflare 2025 Q4 DDoS Threat Report, and Source: Legal filing in U.S. Eastern District Court, and Source: Incident disclosure by SUNY Research Foundation, and Source: ComparitechDate Accessed: 2025, and Source: Flare (security firm), and Source: TeamPCP Telegram channel, and Source: Maine Attorney General’s Office, and Source: The Register, and Source: Edelson Lechtzin LLP, and Source: Lynch Carpenter, LLP, and Source: Dark web post by CL0P ransomware group, and Source: Distributed Denial of Secrets, and Source: Michelin Public Statement, and Source: DarkWeb Informer forum (threat actor 'igotafeeling'), and Source: Loblaw Press Release (March 12), and Source: Hypertherm, Inc. Breach Notification, and Source: Hypertherm breach notification, and Source: CL0P dark web postUrl: Tor network (dark web)Date Accessed: 2025-11-21, and Source: Incident Report, and Source: Oracle Security Alert.

Investigation Status: Ongoing

Investigation Status: ongoing (active campaign)

Investigation Status: Ongoing (early stages, claims unsubstantiated)

Investigation Status: Ongoing (Early Stages)

Investigation Status: Ongoing (developing story)

Investigation Status: Ongoing (Google Mandiant involved in analysis)

Investigation Status: Ongoing (CrowdStrike, Mandiant, GTIG)

Investigation Status: Ongoing (Active Exploitation Confirmed)

Investigation Status: Ongoing (Google, Mandiant, and CrowdStrike Investigating Extent of Exploitation)

Investigation Status: ['Ongoing (Oracle)', 'Closed (Microsoft Patches)', 'Ongoing (F5)', 'Ongoing (Adobe)', 'Closed (Certificates Revoked)', 'Ongoing (Cisco)', 'Closed (Assets Seized)', 'Ongoing (Unitree)', 'Ongoing (Healthcare Sector)']

Investigation Status: [None, None, None]

Investigation Status: ongoing (NHS cybersecurity team and NCSC investigating)

Investigation Status: Ongoing (infrastructure analysis links to prior MOVEit attacks)

Investigation Status: Ongoing (Clop’s claims under verification; Oracle’s internal investigation likely)

Investigation Status: Ongoing (forensic investigation, potential third-party involvement)

Investigation Status: Ongoing (Cl0p’s data leak timeline suggests delayed public exposure)

Investigation Status: Completed

Investigation Status: Ongoing

Investigation Status: Ongoing

Investigation Status: Ongoing (comprehensive review completed)

Investigation Status: Ongoing (forensic analysis completed, but full extent unclear)

Investigation Status: Under investigation

Investigation Status: Ongoing

Investigation Status: Ongoing

Investigation Status: Unverified (allegations under scrutiny)

Investigation Status: Ongoing

Investigation Status: Ongoing

Investigation Status: Ongoing
Communication of Investigation Status: The company communicates the status of incident investigations to stakeholders through Customer Advisory, Criticized For Lack Of Transparency, Private letters to customers, Outright Denial, Potentially Misleading Statements, Accusations Of Deleting Evidence Online, Customer Advisories About Impersonation Attempts, Industry-Wide Alerts, Public Warning Via Cybersecurity Firms (Mandiant, Gtig), Media Outreach (Recorded Future News), Public Advisory, Linkedin Post By Oracle Cso, Mandiant Technical Alert, Public Security Advisory By Oracle Cso Rob Duhart, Linkedin Post By Google Mandiant Cto Charles Carmakal, Oracle Customer Advisory, Public Disclosure Of Poc Risks, Public Advisory By Oracle, Blog Post By Google, Media Statements, Public Security Advisories, Direct Customer Notifications, Patch Tuesday Announcement, Public Breach Disclosure, Cisa Kev Catalog Update, Microsoft Security Blog, Cisco Security Advisory, Doj Press Release, Alias Robotics Advisory, Healthcare It Alerts, public statement issued (neither confirmed nor denied intrusion), Notification Letters To Affected Parties, Public Disclosure Via Maine Attorney General’S Office Filing, Oracle Security Alerts To Customers, Public Disclosure Via Media, Data breach notification letters mailed to impacted individuals, Public disclosure on official website, SEC filing, notification letters to affected individuals, Written notice to affected individuals on Dec. 22, 2025, Public statements to stakeholders, Public statement dismissing hackers' claims, notifications to affected individuals, Affected employees were notified last week, Notified impacted individuals via breach notification, Customer notifications via mail, Written notifications to affected individuals, Public disclosure and assurance of containment, Press release downplaying the breach and denying financial data compromise, Notification to affected individuals, Notification letters mailed to affected individuals, dedicated call center (844-403-4502), Lack of public disclosure from affected companies and Urgent security alert issued.

Customer Advisories: Oracle urged Micros customers to change their passwords and any passwords used by Micros representatives to access their on-premise systems.

Customer Advisories: Private letters to customers

Stakeholder Advisories: Warn Customers About Impersonation Attempts, Share Indicators Of Compromise (Iocs) With Industry Peers.
Customer Advisories: avoid clicking on sponsored search ads for hospitality servicesverify URLs before entering credentialsreport suspicious login pages

Customer Advisories: Recommended: Investigate Oracle E-Business Suite for compromise

Stakeholder Advisories: Mandiant/Gtig Warning To Corporate Executives.

Stakeholder Advisories: Oracle and Mandiant have issued public advisories urging immediate action.
Customer Advisories: Customers advised to patch and investigate potential compromise.

Stakeholder Advisories: Oracle Customers Urged To Patch Immediately, Executives Warned About Extortion Emails.
Customer Advisories: Patch installation guidanceIoCs for detecting compromise

Stakeholder Advisories: Oracle Urgent Patching Advisory, Crowdstrike Threat Assessment.
Customer Advisories: Extortion Emails from Clop to Executives

Stakeholder Advisories: Oracle and Google have issued advisories with technical details for detection and mitigation.
Customer Advisories: Organizations using Oracle E-Business Suite advised to apply patches and monitor for suspicious activity.

Stakeholder Advisories: Oracle Customers Urged To Patch Immediately, Executives Warned About Extortion Emails.
Customer Advisories: Apply Emergency Patches for CVE-2025-61884 and CVE-2025-61882Monitor for Suspicious Activity

Stakeholder Advisories: Oracle Customers Urged To Apply Patches Immediately., Microsoft Recommends Prioritizing Zero-Day Patches., F5 Advises Big-Ip Customers To Monitor For Suspicious Activity., Adobe Urges Aem Jee Users To Verify Configurations., Microsoft Teams Users Warned Of Malicious Installers., Cisco Issues Advisory For Ios/Ios Xe Users., Doj Warns Financial Institutions About Crypto Scam Indicators., Alias Robotics Recommends Disabling Bluetooth On Unitree G1., Hhs Issues Alert On Healthcare Cyberattack Surge..
Customer Advisories: Oracle: 'Apply CVE-2025-61884 patch within 48 hours.'Microsoft: 'October 2025 updates include critical zero-day fixes.'F5: 'No evidence of customer data exposure, but monitor systems.'Adobe: 'Audit AEM Forms configurations for CVE-2025-54253.'Microsoft: 'Verify Teams installer signatures.'Cisco: 'Update IOS/IOS XE devices to mitigate rootkit risk.'Unitree: 'Avoid public Wi-Fi; update robot firmware.'CDC: 'Healthcare orgs must treat cybersecurity as patient safety issue.'


Customer Advisories: Extortion emails sent to victims via support@pubstorm[.]com

Stakeholder Advisories: Notification Letters To Affected Individuals, Public Statements Via Regulatory Filings.
Customer Advisories: Free credit monitoring offered to affected parties

Stakeholder Advisories: Oracle Security Alerts Urging Immediate Patching, Mandiant’S Analysis Of Cl0P’S Modus Operandi.
Customer Advisories: Companies advised to monitor for data leaks on Cl0p’s blog or dark web marketplaces

Customer Advisories: 24 months of complimentary credit monitoring services provided to affected individuals

Stakeholder Advisories: Notification letters mailed to affected individuals, public disclosure on website
Customer Advisories: Free identity protection services offered (credit monitoring, identity theft recovery, dark web monitoring, $1 million fraud reimbursement policy)

Customer Advisories: Affected individuals notified via written notice on Dec. 22, 2025

Stakeholder Advisories: Universities have issued public statements to stakeholders about the breaches and steps taken to mitigate risks.

Customer Advisories: Notifications sent to affected individuals

Customer Advisories: Affected employees were notified last week

Customer Advisories: Notified impacted individuals

Customer Advisories: Notification via mail to affected customers

Customer Advisories: Written notifications sent to affected individuals on February 27, 2026

Customer Advisories: Loblaw customers with PC Optimum accounts, Shoppers Drug Mart loyalty cards, or prescription histories advised to monitor for potential fraud

Customer Advisories: Notification to affected individuals

Customer Advisories: One year of free identity monitoring through Kroll, including credit monitoring, fraud consultation, and identity theft restoration

Stakeholder Advisories: Oracle emphasizes the need for immediate patch deployment to secure identity management infrastructure
Advisories Provided: The company provides the following advisories to stakeholders and customers following an incident: were Oracle urged Micros customers to change their passwords and any passwords used by Micros representatives to access their on-premise systems., Private letters to customers, Warn Customers About Impersonation Attempts, Share Indicators Of Compromise (Iocs) With Industry Peers, Avoid Clicking On Sponsored Search Ads For Hospitality Services, Verify Urls Before Entering Credentials, Report Suspicious Login Pages, , Recommended: Investigate Oracle E-Business Suite for compromise, Mandiant/Gtig Warning To Corporate Executives, Oracle and Mandiant have issued public advisories urging immediate action., Customers advised to patch and investigate potential compromise., Oracle Customers Urged To Patch Immediately, Executives Warned About Extortion Emails, Patch Installation Guidance, Iocs For Detecting Compromise, , Oracle Urgent Patching Advisory, Crowdstrike Threat Assessment, Extortion Emails From Clop To Executives, , Oracle and Google have issued advisories with technical details for detection and mitigation., Organizations using Oracle E-Business Suite advised to apply patches and monitor for suspicious activity., Oracle Customers Urged To Patch Immediately, Executives Warned About Extortion Emails, Apply Emergency Patches For Cve-2025-61884 And Cve-2025-61882, Monitor For Suspicious Activity, , Oracle Customers Urged To Apply Patches Immediately., Microsoft Recommends Prioritizing Zero-Day Patches., F5 Advises Big-Ip Customers To Monitor For Suspicious Activity., Adobe Urges Aem Jee Users To Verify Configurations., Microsoft Teams Users Warned Of Malicious Installers., Cisco Issues Advisory For Ios/Ios Xe Users., Doj Warns Financial Institutions About Crypto Scam Indicators., Alias Robotics Recommends Disabling Bluetooth On Unitree G1., Hhs Issues Alert On Healthcare Cyberattack Surge., Oracle: 'Apply Cve-2025-61884 Patch Within 48 Hours.', Microsoft: 'October 2025 Updates Include Critical Zero-Day Fixes.', F5: 'No Evidence Of Customer Data Exposure, But Monitor Systems.', Adobe: 'Audit Aem Forms Configurations For Cve-2025-54253.', Microsoft: 'Verify Teams Installer Signatures.', Cisco: 'Update Ios/Ios Xe Devices To Mitigate Rootkit Risk.', Unitree: 'Avoid Public Wi-Fi; Update Robot Firmware.', Cdc: 'Healthcare Orgs Must Treat Cybersecurity As Patient Safety Issue.', , Extortion Emails Sent To Victims Via Support@Pubstorm[.]Com, , Notification Letters To Affected Individuals, Public Statements Via Regulatory Filings, Free credit monitoring offered to affected parties, Oracle Security Alerts Urging Immediate Patching, Mandiant’S Analysis Of Cl0P’S Modus Operandi, Companies Advised To Monitor For Data Leaks On Cl0P’S Blog Or Dark Web Marketplaces, , 24 months of complimentary credit monitoring services provided to affected individuals, Notification letters mailed to affected individuals, public disclosure on website, Free identity protection services offered (credit monitoring, identity theft recovery, dark web monitoring, $1 million fraud reimbursement policy), Affected individuals notified via written notice on Dec. 22, 2025, Universities have issued public statements to stakeholders about the breaches and steps taken to mitigate risks., Notifications sent to affected individuals, Affected employees were notified last week, Notified impacted individuals, Notification via mail to affected customers, Written notifications sent to affected individuals on February 27, 2026, Loblaw customers with PC Optimum accounts, Shoppers Drug Mart loyalty cards, or prescription histories advised to monitor for potential fraud, Notification to affected individuals, One year of free identity monitoring through Kroll, including credit monitoring, fraud consultation, and identity theft restoration and Oracle emphasizes the need for immediate patch deployment to secure identity management infrastructure.

Entry Point: CVE-2021-35587

Entry Point: Malvertising (Malicious Search Engine Ads), Typosquatted Domains,
High Value Targets: Cloud-Based Property Management Systems, Guest Messaging Platforms, Payment Processing Systems,
Data Sold on Dark Web: Cloud-Based Property Management Systems, Guest Messaging Platforms, Payment Processing Systems,

Entry Point: Compromised Email Accounts
High Value Targets: Executives at multiple companies
Data Sold on Dark Web: Executives at multiple companies

Entry Point: Compromised Email Accounts, Potential Exploitation Of Oracle E-Business Suite Vulnerabilities,
High Value Targets: Corporate Executives, Finance/Hr/Supply Chain Data,
Data Sold on Dark Web: Corporate Executives, Finance/Hr/Supply Chain Data,

Entry Point: Oracle E-Business Suite Concurrent Processing Component (via HTTP)
High Value Targets: Enterprise data within Oracle EBS environments
Data Sold on Dark Web: Enterprise data within Oracle EBS environments

Entry Point: CVE-2025-61882 (Oracle E-Business Suite zero-day)
Reconnaissance Period: Likely conducted prior to August 2025 (exploitation began in August)
High Value Targets: Corporate Executives' Personal Data,
Data Sold on Dark Web: Corporate Executives' Personal Data,

Entry Point: Cve-2025-61882 (Oracle Ebs Bi Publisher),
Reconnaissance Period: ['Potentially since early August 2025 (zero-day exploitation)']
High Value Targets: Sensitive Corporate Documents,
Data Sold on Dark Web: Sensitive Corporate Documents,

Entry Point: Zero-Day Vulnerability in Oracle E-Business Suite (Network-Based, No Authentication Required)
Reconnaissance Period: Since at least 2023-07-10
High Value Targets: Corporate Executives, Hr And Customer Data,
Data Sold on Dark Web: Corporate Executives, Hr And Customer Data,

Entry Point: Exploitation Of Oracle Ebs Vulnerabilities (Cve-2025-61882, Cve-2025-61884), Hacked User Emails, Default Password Reset Mechanisms,
Reconnaissance Period: Potentially Began on 2025-07-10 (Prior to July Patches)
High Value Targets: Company Executives (Extortion Emails), Oracle Ebs Databases,
Data Sold on Dark Web: Company Executives (Extortion Emails), Oracle Ebs Databases,

Entry Point: Misconfigured Aem Jee, Compromised Software Signing Certificates, Cve-2025-20352 (Ios/Ios Xe), Phishing/Social Engineering (Forced Labor Scam), Bluetooth Interface,
Reconnaissance Period: [None, None, None, None, None, None, 'Months (Scam)', None, None]
Backdoors Established: [None, None, None, None, None, 'Linux Rootkits', None, None, 'Likely (Ransomware)']
High Value Targets: Big-Ip Source Code, Microsoft Teams Distribution Channels, Cisco Network Devices, Cryptocurrency Wallets, Robot Sensor Data,
Data Sold on Dark Web: Big-Ip Source Code, Microsoft Teams Distribution Channels, Cisco Network Devices, Cryptocurrency Wallets, Robot Sensor Data,

Entry Point: Compromised Oauth Tokens (Drift-Salesforce Integration), Exposed Github Api Token (Public Repository), Orphaned Api Token (Okta Service Account),
Reconnaissance Period: [None, None, None]
Backdoors Established: ['Yes (via hijacked OAuth tokens)', 'Yes (via exposed API token)', 'Yes (via unrotated service token)']
High Value Targets: Salesforce Crm Data, Aws/Snowflake Credentials, Internal Source Code (270 Gb), Atlassian Suite (Jira, Confluence, Bitbucket),
Data Sold on Dark Web: Salesforce Crm Data, Aws/Snowflake Credentials, Internal Source Code (270 Gb), Atlassian Suite (Jira, Confluence, Bitbucket),

Entry Point: potential Oracle E-Business Suite (EBS) exploit
High Value Targets: patient data, critical healthcare systems
Data Sold on Dark Web: patient data, critical healthcare systems

Entry Point: OA_HTML/SyncServlet (Authentication Bypass) & OA_HTML/RF.jsp (XSLT Injection)
Reconnaissance Period: Observed as early as June 2025, active exploitation from August 2025
High Value Targets: Oracle E-Business Suite Erp Data, Financial Records, Personal Records,
Data Sold on Dark Web: Oracle E-Business Suite Erp Data, Financial Records, Personal Records,

Entry Point: Oracle E-Business Suite (Ebs) Syncservlet Endpoint,
Reconnaissance Period: Likely conducted prior to August 2025 (exploitation start date)
High Value Targets: Erp Data (Order Management, Procurement, Logistics), Customer Databases,
Data Sold on Dark Web: Erp Data (Order Management, Procurement, Logistics), Customer Databases,

Entry Point: Zero-day exploit (CVE-2025-61882) in Oracle E-Business Suite
Reconnaissance Period: Potentially since July 2025 (part of broader Cl0p campaign)
Backdoors Established: ['Multi-stage Java implants']
High Value Targets: Erp Databases, Hr Systems, Financial Records,
Data Sold on Dark Web: Erp Databases, Hr Systems, Financial Records,

Entry Point: Zero-Day Vulnerabilities In Oracle Ebs (Cve-2025-61882, Cve-2025-21884),
Reconnaissance Period: Since late September 2023 (pre-exploitation activity)
High Value Targets: Fortune 500 Companies (E.G., Broadcom, Estée Lauder), Multinational Corporations With Oracle Ebs Dependencies,
Data Sold on Dark Web: Fortune 500 Companies (E.G., Broadcom, Estée Lauder), Multinational Corporations With Oracle Ebs Dependencies,

Entry Point: Oracle E-Business Suite (EBS) zero-day vulnerability (CVE-2025-61882)

Entry Point: Phone-based phishing (social engineering)

Entry Point: Stolen Credentials, Social Engineering,

Entry Point: Exposed Docker Apis, Kubernetes Clusters, Ray Dashboards, Leaked Secrets,
Backdoors Established: True

Entry Point: Compromised employee credentials

Entry Point: Oracle EBS zero-day vulnerability

Entry Point: Oracle EBS vulnerability

Root Causes: Vulnerable software version, compromised subdomain

Root Causes: Over-Reliance On Traditional Mfa Methods Vulnerable To Real-Time Phishing., Lack Of Visibility Into Malvertising Campaigns Targeting Brand Impersonation., Insufficient Monitoring For Typosquatted Domains And Beaconing Activity.,
Corrective Actions: Replace Sms/Email-Based Mfa With Phishing-Resistant Alternatives., Proactively Register Defensive Domains To Prevent Typosquatting., Enhance Threat Intelligence Sharing Within The Hospitality Sector., Deploy Solutions To Detect And Block Malicious Ads In Search Results.,

Root Causes: Zero-Day Vulnerability (Cve-2025-61882) In Oracle E-Business Suite., Lack Of Authentication Requirements For Exploitation., High-Volume Email Campaign Leveraging Compromised Accounts (Per Mandiant).,
Corrective Actions: Emergency Patch Release By Oracle., Public Disclosure And Customer Advisories., Collaboration With Mandiant For Threat Intelligence Sharing.,

Root Causes: Zero-Day Vulnerability (Cve-2025-61882) In Oracle E-Business Suite, Insufficient Proactive Patching For Prior Vulnerabilities (July 2025 Patches Bypassed),
Corrective Actions: Patch Deployment, Customer Advisory For Ioc Monitoring,

Root Causes: Unpatched Oracle Ebs Vulnerability (Cve-2025-61882), Internet-Exposed Ebs Applications Without Authentication Safeguards, Delayed Patching Despite Active Exploitation,
Corrective Actions: Apply Oracle’S Security Patch For Cve-2025-61882., Implement Network Segmentation For Ebs Environments., Deploy Behavioral Detection For Rce Attempts (E.G., Crowdstrike Falcon)., Conduct Threat Hunting For Signs Of Clop Or Graceful Spider Activity.,

Root Causes: Unpatched Zero-Day Vulnerability In Oracle E-Business Suite, Inadequate Initial Response By Oracle (Premature Claim Of Patch Effectiveness), Lack Of Network Segmentation Or Access Controls To Limit Exploitation,
Corrective Actions: Oracle Released Emergency Patches And Advisories, Google Shared Detection Indicators For Affected Organizations, Recommended Enhanced Monitoring For Extortion Emails And Unusual Data Access,

Root Causes: Unpatched Vulnerabilities In Oracle E-Business Suite, Lack Of Authentication For Remote Exploitation, Potential Weaknesses In Default Password Reset Mechanisms, Delayed Patch Deployment By Some Customers,
Corrective Actions: Oracle Released Out-Of-Band Patches, Customers Advised To Apply Patches And Monitor Systems, Enhanced Threat Intelligence Sharing (E.G., Poc Disclosure As Ioc),

Root Causes: Unpatched Oracle Ebs Vulnerability., Zero-Day Exploitation Before Patches (Microsoft)., Insufficient Source Code Protection (F5)., Adobe Aem Misconfiguration Oversight., Certificate Authority Process Gaps (Microsoft)., Delayed Cisco Ios/Xe Patching., Lack Of Crypto Transaction Monitoring (Doj)., Insecure Bluetooth Implementation (Unitree).,
Corrective Actions: Oracle: Accelerate Vulnerability Disclosure Timelines., Microsoft: Expand Zero-Day Detection Capabilities., F5: Enhance Code Repository Security Controls., Adobe: Automate Configuration Audits For Aem., Microsoft: Implement Certificate Transparency Logging., Cisco: Harden Ios/Xe Against Rootkit Persistence., Fincen: Update Crypto Transaction Reporting Rules., Unitree: Partner With Security Firms For Firmware Audits.,

Root Causes: Lack Of Visibility And Oversight For Non-Human Identities (Oauth Tokens) With Excessive Privileges., Public Exposure Of A Github Api Token Due To Misconfiguration Or Lack Of Secret Management., Incomplete Incident Response: Human Credentials Were Rotated, But Non-Human Credentials (Api Tokens) Were Overlooked, Leaving A Backdoor Open., Overprivileged Nhis: Integrations And Tokens Had Broader Access Than Necessary, Increasing The Blast Radius Of Compromises.,
Corrective Actions: Adopt A **Dynamic Saas Security Platform** To Automate Discovery, Monitoring, And Remediation Of Nhis., Implement **Least Privilege Enforcement** For All Nhis, Auditing And Restricting Access Scopes To The Minimum Required., Deploy **Real-Time Anomaly Detection** For Nhi Behavior, With Automated Responses To Suspicious Activity (E.G., Token Revocation)., Establish **Automated Credential Rotation** For Nhis, Ensuring Tokens And Keys Are Regularly Refreshed And Unused Credentials Are Disabled., Conduct **Comprehensive Nhi Inventories** Across All Saas Applications, Classifying Identities By Type And Risk Level., Integrate **Nhi Security Into Iam Strategies**, Treating Machine Identities With The Same Rigor As Human Accounts., Enforce **Compensating Controls** For Nhis (E.G., Ip Restrictions, Session Monitoring) Where Mfa Is Not Applicable., Educate Security And Devops Teams On The Risks Of Nhis And The Importance Of Token Hygiene (E.G., Avoiding Hardcoding, Public Exposure).,

Root Causes: Zero-Day Exploit (Cve-2025-61882), Delayed Patch Release (Exploited For Months Pre-Patch), Reused Attack Infrastructure From Moveit (Cve-2023-34362),
Corrective Actions: Patch Deployment (October 2025), Infrastructure Monitoring For 96 Linked Ips (41 Subnets Reused From Moveit),

Root Causes: Unpatched Zero-Day Vulnerability (Cve-2025-61882) In Oracle Ebs, Lack Of Pre-Authentication Protections For Syncservlet Endpoint, Reuse Of Attack Infrastructure From Prior Campaigns (E.G., Moveit Cve-2023-34362),

Root Causes: Unpatched Zero-Day Vulnerability (Cve-2025-61882) In Oracle E-Business Suite., Delayed Detection (Weeks Between Intrusion And Discovery)., Lack Of Proactive Threat Hunting For Erp-Specific Attacks., Potential Gaps In Network Segmentation Or Access Controls.,
Corrective Actions: Applied Oracle’S Emergency Patch (2025-10-04)., Enhanced Monitoring For Erp Systems., Review Of Third-Party Software Patching Policies., Potential Restructuring Of Incident Response Protocols To Reduce Detection Lag.,

Root Causes: Unpatched Zero-Day Vulnerabilities In Oracle Ebs (Cve-2025-61882, Cve-2025-21884)., Lack Of Real-Time Monitoring For Unauthenticated Http Requests Targeting Critical Components (Bi Publisher, Configurator Ui)., Supplier Risk Blind Spots In Enterprise Software Supply Chains.,
Corrective Actions: Immediate Application Of Oracle-Provided Security Patches., Enhanced Supplier Risk Assessments Using Scrm Platforms (E.G., Z2Data)., Implementation Of Behavioral Wafs Or Anomaly Detection For Oracle Ebs Environments., Review Of Third-Party Software Dependencies For Similar Vulnerabilities.,

Root Causes: Exploitation of zero-day vulnerability in Oracle E-Business Suite (CVE-2025-61882)

Root Causes: Human Error (Falling For Phishing Attacks), Decentralized It Departments Creating Inconsistent Security Protocols, Lack Of Centralized Control Over Technology Use, Excessive Data Retention (E.G., Storing Social Security Numbers Unnecessarily), Faculty Resistance To It Policies Due To Perceived Restrictions On Academic Freedom,
Corrective Actions: Removing Hackers' Access To Systems, Stepping Up Security Protocols, Enhancing Cybersecurity Training For Faculty And Staff,

Root Causes: Flaw in how WebLogic Server Proxy Plug-ins process incoming requests
Corrective Actions: Patches released, network access restrictions recommended

Root Causes: Supply Chain Vulnerabilities, Stolen Credentials, Social Engineering, It-Ot Convergence Risks,

Root Causes: Compromised IoT devices and routers, primarily Android TVs

Corrective Actions: Mandatory cybersecurity training, strengthened defenses

Root Causes: Zero-day vulnerability in Oracle’s eBusiness Suite
Corrective Actions: Oracle released an urgent patch

Root Causes: Cloud Misconfigurations, Exposed Management Services, Leaked Credentials,

Root Causes: Exploitation of Oracle PeopleSoft vulnerability via compromised employee credentials

Root Causes: Vulnerability in Oracle eBusiness Suite (third-party vendor)

Root Causes: Exploited vulnerability in Oracle E-Business Suite (EBS)

Root Causes: Exploitation of Oracle EBS zero-day vulnerability
Corrective Actions: Vulnerability patched, containment measures implemented

Root Causes: Unpatched software vulnerability in Oracle EBS

Root Causes: Vulnerabilities in Oracle E-Business Suite

Root Causes: Critical RCE vulnerability in Oracle Identity Manager and Web Services Manager
Corrective Actions: Patch deployment, upgrade to supported versions
Post-Incident Analysis Process: The company's process for conducting post-incident analysis is described as Okta Threat Intelligence (Analysis By Moussa Diallo), , Real-Time Tracking Of Typosquatted Domains, Beaconing Detection, , Mandiant (Google Cloud), Gtig, , Recommended (for unusual access), Mandiant (Google Cloud), Google Threat Intelligence Group (Gtig), , Mandiant (Google Cloud), , Recommended for customers to detect prior compromise, Google Mandiant (Investigation And Advisory), , Crowdstrike (Detection And Analysis), Mandiant (Investigation), Google Threat Intelligence Group (Gtig), , Recommended For Oracle Ebs Environments, , Google Security Researchers, , Recommended (Google Provided Indicators for Detection), Google Threat Intelligence, Mandiant, Crowdstrike, , Recommended (Oracle Advised Customers to Monitor for Exploitation Attempts), Law Enforcement (Doj), , , , , , Security Researchers (The Raven File), , Potential Involvement Of Mandiant (Forensic Investigation), , Recommended (not explicitly confirmed), Mandiant (Google-Owned Cybersecurity Firm), , Cybersecurity specialists, Flare (security firm), Lynch Carpenter, LLP (investigation), Cybersecurity experts, Third-party cybersecurity experts, Kroll (identity monitoring), Oracle and cybersecurity experts.
Corrective Actions Taken: The company has taken the following corrective actions based on post-incident analysis: Replace Sms/Email-Based Mfa With Phishing-Resistant Alternatives., Proactively Register Defensive Domains To Prevent Typosquatting., Enhance Threat Intelligence Sharing Within The Hospitality Sector., Deploy Solutions To Detect And Block Malicious Ads In Search Results., , Emergency Patch Release By Oracle., Public Disclosure And Customer Advisories., Collaboration With Mandiant For Threat Intelligence Sharing., , Patch Deployment, Customer Advisory For Ioc Monitoring, , Apply Oracle’S Security Patch For Cve-2025-61882., Implement Network Segmentation For Ebs Environments., Deploy Behavioral Detection For Rce Attempts (E.G., Crowdstrike Falcon)., Conduct Threat Hunting For Signs Of Clop Or Graceful Spider Activity., , Oracle Released Emergency Patches And Advisories, Google Shared Detection Indicators For Affected Organizations, Recommended Enhanced Monitoring For Extortion Emails And Unusual Data Access, , Oracle Released Out-Of-Band Patches, Customers Advised To Apply Patches And Monitor Systems, Enhanced Threat Intelligence Sharing (E.G., Poc Disclosure As Ioc), , Oracle: Accelerate Vulnerability Disclosure Timelines., Microsoft: Expand Zero-Day Detection Capabilities., F5: Enhance Code Repository Security Controls., Adobe: Automate Configuration Audits For Aem., Microsoft: Implement Certificate Transparency Logging., Cisco: Harden Ios/Xe Against Rootkit Persistence., Fincen: Update Crypto Transaction Reporting Rules., Unitree: Partner With Security Firms For Firmware Audits., , Adopt A **Dynamic Saas Security Platform** To Automate Discovery, Monitoring, And Remediation Of Nhis., Implement **Least Privilege Enforcement** For All Nhis, Auditing And Restricting Access Scopes To The Minimum Required., Deploy **Real-Time Anomaly Detection** For Nhi Behavior, With Automated Responses To Suspicious Activity (E.G., Token Revocation)., Establish **Automated Credential Rotation** For Nhis, Ensuring Tokens And Keys Are Regularly Refreshed And Unused Credentials Are Disabled., Conduct **Comprehensive Nhi Inventories** Across All Saas Applications, Classifying Identities By Type And Risk Level., Integrate **Nhi Security Into Iam Strategies**, Treating Machine Identities With The Same Rigor As Human Accounts., Enforce **Compensating Controls** For Nhis (E.G., Ip Restrictions, Session Monitoring) Where Mfa Is Not Applicable., Educate Security And Devops Teams On The Risks Of Nhis And The Importance Of Token Hygiene (E.G., Avoiding Hardcoding, Public Exposure)., , Patch Deployment (October 2025), Infrastructure Monitoring For 96 Linked Ips (41 Subnets Reused From Moveit), , Applied Oracle’S Emergency Patch (2025-10-04)., Enhanced Monitoring For Erp Systems., Review Of Third-Party Software Patching Policies., Potential Restructuring Of Incident Response Protocols To Reduce Detection Lag., , Immediate Application Of Oracle-Provided Security Patches., Enhanced Supplier Risk Assessments Using Scrm Platforms (E.G., Z2Data)., Implementation Of Behavioral Wafs Or Anomaly Detection For Oracle Ebs Environments., Review Of Third-Party Software Dependencies For Similar Vulnerabilities., , Removing Hackers' Access To Systems, Stepping Up Security Protocols, Enhancing Cybersecurity Training For Faculty And Staff, , Patches released, network access restrictions recommended, Mandatory cybersecurity training, strengthened defenses, Oracle released an urgent patch, Vulnerability patched, containment measures implemented, Patch deployment, upgrade to supported versions.
Ransom Payment History: The company has Paid ransoms in the past.
Last Ransom Demanded: The amount of the last ransom demanded was Yes (extortion emails sent to executives).
Last Attacking Group: The attacking group in the last incident were an Russian Cybercrime Group, rose87168, 'rose87168', rose87168, Unauthorized Individual, Russian-speaking cybercriminalsunknown APT/group (potential initial access brokers), FIN11 (suspected)Clop Ransomware Gang (potential link), Clop (FIN11)Potentially Impersonating Clop, Cl0p Ransomware GroupScattered LAPSUS$ Hunters, Clop (hacking group linked to ransomware and extortion), Clop Ransomware GangGRACEFUL SPIDER (moderate confidence), Clop Ransomware/Extortion Gang, Cl0p Ransomware Group (Graceful Spider)FIN11Potential involvement of Scattered Spider, Slippy Spider (Lapsus$), ShinyHunters, Nation-State AttackersVanilla Tempest (Ransomware Group)Cryptocurrency Fraud Syndicate, , Clop (extortion crew), Clop Ransomware Gang (Graceful Spider), Name: ['Clop Ransomware Gang', 'Graceful Spider']Origin: Russian-linkedConfirmed Victims: 1025Ransom Extracted: $500 million (since 2019)Associated Infrastructure: {'ip_addresses': 96, 'reused_ips_from_moveit': 41, 'geographic_distribution': [{'country': 'Germany', 'ip_count': 16}, {'country': 'Brazil', 'ip_count': 13}, {'country': 'Panama', 'ip_count': 12}], 'service_providers': ['Russian-based']}, Cl0p Ransomware Group (alleged), Cl0p (Clop), Unauthorized third party, Clop ransomware gang, CL0P ransomware group, Aisuru/Kimwolf Botnet, Anonymous Hackers, QilinAkiraSafePayClopInterlockDragonForce, TeamPCP (aka PCPcat, ShellForce), Clop ransomware gang, ShinyHunters, CL0P ransomware group, Department of Peace, Cl0p (FIN11), igotafeeling and CL0P.
Most Recent Incident Detected: The most recent incident detected was on 2013-07-10.
Most Recent Incident Publicly Disclosed: The most recent incident publicly disclosed was on 2026-03-13.
Most Recent Incident Resolved: The most recent incident resolved was on [None, '2025-10-01 (Patches Released)', None, None, '2025-10-01 (Certificates Revoked)', None, '2025-10-01 (Seizure)', None, None].
Highest Financial Loss: The highest financial loss from an incident was ['£206 million ($276 million) in lost revenue (Co-operative Group)', '$276 million (Co-operative Group)'].
Most Significant Data Compromised: The most significant data compromised in an incident were Credit Card Payment Information, , SSO passwords, Java Keystore files, Key files, JPS keys, , JKS files, Encrypted SSO passwords, Key files, JPS keys, , Electronic Health Records (EHR), , Personal Information, usernames, email addresses, hashed passwords, SSO credentials, LDAP credentials, JKS files, Enterprise Manager JPS keys, , Names, Social Security Numbers, , guest personal information, payment data, booking system credentials, operational data, , Potentially Finance, HR, and Supply Chain Data (Oracle E-Business Suite), , Large amounts of data (exact scope undisclosed), Personal information of corporate executives, Customer data, Employee HR files, , Sensitive Documents, Potentially PII or Corporate Data, , Corporate Executive Data, Customer Data, Employee HR Files, Sensitive Corporate Data, , Sensitive Resources, Potential Oracle E-Business Suite Data (as claimed in extortion emails), , BIG-IP Source Code & Vulnerability Info, Robot Sensor/Data Leaks, , Salesforce CRM data (including AWS keys and Snowflake tokens from support case attachments), 270 GB of internal source code and data, Access to Cloudflare's Atlassian suite (Jira, Confluence, Bitbucket), , Financial Records, Personal Records, ERP Data, , Internal Corporate Data, Customer Information, Financial Records, Personal Data, , Names, Addresses, Dates of Birth, Social Security Numbers, Personal Identifiers, Internal Documents, Employee Records, Customer Details, , , Sensitive personal identifiable information, 3,489,274 records, Sensitive personally identifiable information, Personal data of students, faculty, and staff, Sensitive data, , Personal data of fewer than 10 individuals, Personnel files containing sensitive employee information, including Social Security numbers, 59.2 million records (confirmed), 31.2 petabytes (Qilin), Over two million records (personal IDs, employment records, résumés), Sensitive customer data, 800,000 employee records, Names, addresses, Social Security numbers, Personal Identifiable Information (PII), Sensitive data, including names, Social Security numbers, and financial account information, Sensitive contract details, company names, URLs, employee details, addresses, tax ID numbers, government contractor identifiers, internal DHS staff comments, awarded contracts, 315GB of files, Over 1.8 billion records allegedly exposed, Sensitive information, database tables, Names, Social Security numbers, Sensitive corporate and customer data and Sensitive corporate identity data.
Most Significant System Affected: The most significant system affected in an incident were MICROS Point-of-Sale Systems and and Legacy Servers and legacy Cerner data migration servers and Login ServersLegacy Cerner Data and Gen 1 serverslegacy systems and cloud-based property management systemsguest messaging platformsauthentication systems and Oracle E-Business Suite (potential) and Oracle E-Business Suite and and Oracle E-Business Suite and Oracle E-Business Suite (EBS) with unpatched BI Publisher Integration and Oracle E-Business Suite and Oracle E-Business Suite (Versions 12.2.3–12.2.14)Runtime UI ComponentBI Publisher IntegrationConcurrent Processing Component and Oracle E-Business SuiteMicrosoft Products (Multiple)F5 BIG-IP Networking/Security ProductsAdobe Experience Manager (JEE)Microsoft Teams (Malicious Installers)Cisco Network Switches (IOS/IOS XE)Cryptocurrency Wallets/ExchangesUnitree G1 Humanoid RobotsHealthcare IT Systems, Cloud Accounts, Medical Devices and Salesforce CRM (via Drift integration)GitHub (New York Times' cloud code repository)Atlassian Suite (Jira, Confluence, Bitbucket) and Oracle E-Business Suite (Versions 12.2.3–12.2.14)Internal Corporate Systems and Oracle E-Business Suite (EBS) ServersEnterprise Resource Planning (ERP) Systems and Oracle E-Business SuiteERP SystemsDatabases and Oracle E-Business Suite (EBS) versions 12.2.3–12.2.14 and and and and and and SaaS platformsIT distribution networksHealthcare infrastructureManufacturing OT systemsAviation systems and Telecommunications providersIT organizationsCloudflare infrastructure and and and and and and and and SalesforceShoppers Drug Mart systemsGitLab projectsOracle identity systemsE-commerce platforms and and and and and .
Third-Party Assistance in Most Recent Incident: The third-party assistance involved in the most recent incident was okta threat intelligence (analysis by moussa diallo), , mandiant (google cloud), gtig, , mandiant (google cloud), google threat intelligence group (gtig), , mandiant (google cloud), , google mandiant (investigation and advisory), , crowdstrike (detection and analysis), mandiant (investigation), google threat intelligence group (gtig), , google security researchers, , google threat intelligence, mandiant, crowdstrike, , law enforcement (doj), , , , security researchers (the raven file), , potential involvement of mandiant (forensic investigation), , mandiant (google-owned cybersecurity firm), , Cybersecurity specialists, Flare (security firm), Lynch Carpenter, LLP (investigation), Cybersecurity experts, Third-party cybersecurity experts, Kroll (identity monitoring), Oracle and cybersecurity experts.
Containment Measures in Most Recent Incident: The containment measures taken in the most recent incident were Password Change Recommendation, monitoring for suspicious domain registrationsblocking known malicious domains, Emergency Patch Release (CVE-2025-61882)Advisory for Customer Mitigation, Patch release (CVE-2025-61882)Indicators of Compromise (IoCs) shared with customers, Patching CVE-2025-61882Disabling Exposed EBS Components, Emergency Patching (CVE-2025-61884 & CVE-2025-61882)Urgent Advisory for Customers to Apply Updates, Patches ReleasedCertificate RevocationAsset Seizure, Token revocation (post-incident)Token revocation (post-discovery of compromise), Patch application (Oracle emergency patch on 2025-10-04)Network segmentation (assumed), Oracle security patches (CVE-2025-61882, CVE-2025-21884), Removed hackers' access to internal systems, Restricted network access to affected HTTP ports, Automated systems mitigated attacks without triggering internal alerts, Oracle released an urgent patch for the zero-day vulnerability, Corrective actions taken and vulnerability patched.
Most Sensitive Data Compromised: The most sensitive data compromised in a breach were Employee HR Files, Social Security Numbers, Sensitive Documents, usernames, Addresses, Encrypted SSO passwords, BIG-IP Source Code & Vulnerability Info, SSO passwords, hashed passwords, Personnel files containing sensitive employee information, including Social Security numbers, Enterprise Manager JPS keys, Personal data of students, faculty, and staff, Sensitive contract details, company names, URLs, employee details, addresses, tax ID numbers, government contractor identifiers, internal DHS staff comments, awarded contracts, Sensitive personal identifiable information, Customer data, Personal data of fewer than 10 individuals, Sensitive corporate identity data, Personal Information, Customer Data, Java Keystore files, 270 GB of internal source code and data, Sensitive customer data, Personal Records, Personal Identifiable Information (PII), Sensitive Resources, Large amounts of data (exact scope undisclosed), SSO credentials, Robot Sensor/Data Leaks, Names, addresses, Social Security numbers, Access to Cloudflare's Atlassian suite (Jira, Confluence, Bitbucket), Employee Records, Sensitive corporate and customer data, Potential Oracle E-Business Suite Data (as claimed in extortion emails), Salesforce CRM data (including AWS keys and Snowflake tokens from support case attachments), Internal Corporate Data, Personal Data, ERP Data, booking system credentials, Sensitive data, Over two million records (personal IDs, employment records, résumés), Corporate Executive Data, Personal information of corporate executives, Sensitive Corporate Data, Credit Card Payment Information, email addresses, guest personal information, Customer Information, 59.2 million records (confirmed), 31.2 petabytes (Qilin), Sensitive data, including names, Social Security numbers, and financial account information, Financial Records, payment data, Internal Documents, 3,489,274 records, Names, Customer Details, Dates of Birth, Potentially PII or Corporate Data, Sensitive information, database tables, 800,000 employee records, Names, Social Security numbers, Over 1.8 billion records allegedly exposed, 315GB of files, Electronic Health Records (EHR), Sensitive personally identifiable information, Employee HR files, Personal Identifiers, operational data, JKS files, LDAP credentials, Potentially Finance, HR, and Supply Chain Data (Oracle E-Business Suite), Key files and JPS keys.
Number of Records Exposed in Most Significant Breach: The number of records exposed in the most significant breach was 1.9B.
Highest Ransom Demanded: The highest ransom demanded in a ransomware incident was 23.34 Bitcoin (≈$1.55 million).
Highest Ransom Paid: The highest ransom paid in a ransomware incident was no (NHS policy is to not pay ransoms).
Most Significant Legal Action: The most significant legal action taken for a regulatory violation was None, None, None, None, None, None, Criminal Prosecution (Forced Labor), None, Potential HIPAA Enforcement, , None, None, None, , Potential lawsuits (e.g., against Oracle for delayed patching), , Class-action lawsuit (consolidated), Class action investigation by Edelson Lechtzin LLP, Potential (under investigation by Lynch Carpenter, LLP), Legal investigations underway for potential compensation claims, Class action investigation by Edelson Lechtzin LLP.
Most Significant Lesson Learned: The most significant lesson learned from past incidents was Public disclosure strategies must balance transparency with investigative integrity., Supplier vulnerabilities in enterprise software (e.g., Oracle EBS) can cascade into large-scale breaches across industries. Proactive patch management and supply chain risk monitoring (e.g., via SCRM platforms like Z2Data) are critical to mitigating third-party risks. Cl0p’s delayed data leak strategy highlights the importance of rapid incident response to prevent public exposure of sensitive data., Universities are highly vulnerable to cyberattacks due to decentralized IT structures, lack of centralized control, and human error. Cybersecurity training and awareness are critical but not sufficient alone. There is a need for better collaboration between IT departments and faculty to balance security with academic freedom., Ransomware has evolved into a systemic risk with cascading impacts on supply chains, critical services, and industries. Initial access often relies on stolen credentials or social engineering, and supply chain vulnerabilities amplify the impact. Data theft and operational paralysis are primary damage drivers, with delayed consequences such as regulatory penalties or human harm., Limited scope of breach despite initial claims, need for improved cybersecurity measures, The incident underscores the risks of unsecured cloud control planes, leaked credentials, and poor access controls, highlighting the need for robust cloud security practices., Highlights risks tied to third-party software vulnerabilities, particularly in widely used enterprise systems like Oracle EBS, Transparent communication is increasingly seen as a corporate obligation for stakeholder trust and legal compliance.
Most Significant Recommendation Implemented: The most significant recommendation implemented to improve cybersecurity was Apply Oracle security patches for CVE-2025-61882 and CVE-2025-21884 immediately., Implement supply chain risk management (SCRM) tools to assess third-party vendor vulnerabilities (e.g., Z2Data)., Audit Adobe Experience Manager configurations for CVE-2025-54253., Monitor for Signs of Exploitation (e.g., Unusual Database Activity, Extortion Emails), Disable **orphaned or ghost NHIs** (credentials not tied to active workflows or users), as these are prime targets for attackers., Monitor for suspicious domain registrations (e.g., typosquatting)., Conduct regular security audits for enterprise software., Implement strict access controls and secrets management, Monitor financial statements for suspicious activity, Deploy **continuous anomaly monitoring** to detect deviations in NHI behavior (e.g., unusual access times, data volumes, or locations). Baseline normal activity and flag anomalies in real time., Engage Third-Party Threat Intelligence for Indicators of Compromise (IOCs), Prepare for extortion attempts if using Oracle EBS, given Clop’s history of targeting such vulnerabilities., Acknowledge breaches, implement security measures, collaborate with cybersecurity firms, and notify stakeholders proactively., Develop and test incident response plans for ransomware attacks, including data exfiltration scenarios., Monitor for indicators of compromise (IOCs) linked to Clop’s infrastructure (e.g., 96 IPs, support@pubstorm[.]com), Enhanced vulnerability scanning and threat hunting capabilities., Automate **credential rotation and expiration** for all NHIs. Use platforms that detect stale tokens, rotate secrets regularly, and disable unused credentials., Conduct forensic investigations to detect signs of prior exploitation., Sign up for free IDX identity theft protection services, Request a fraud alert or credit report from major credit bureaus, Enhance authentication mechanisms for OA_HTML endpoints, Monitor for high-volume extortion email campaigns from compromised accounts, Implement Multi-Factor Authentication (MFA) for Oracle EBS, Review third-party vulnerability disclosures for proactive patching, Segment networks to limit lateral movement, Conduct regular audits of enterprise software for zero-day vulnerabilities., Monitor systems for Indicators of Compromise (IoCs) provided by Oracle, Educate employees and customers about malvertising and phishing risks., Immediately patch CVE-2025-61882 in Oracle E-Business Suite environments., Implement more centralized IT control to reduce vulnerabilities from decentralized departments., Conduct **regular audits** of NHI permissions and usage context. Classify NHIs by type (e.g., integrations, AI assistants, RPA bots) to tailor risk controls appropriately., Assess potential links to FIN11/Clop ransomware activity, Immediately apply Oracle's emergency patch for CVE-2025-61882., Apply Oracle Security Alerts and Critical Patch Updates Immediately, Deploy network traffic anomaly detection for Cisco devices (CVE-2025-20352)., Monitor networks for indicators of compromise (IoCs) provided by Google., Review and Secure Default Password Reset Mechanisms, Prioritize patching for remotely exploitable vulnerabilities (Oracle EBS)., Maintain a **real-time inventory** of third-party integrations, especially those connected via user consent (OAuth), and verify their legitimacy and security posture., Implement certificate transparency monitoring (Microsoft Teams)., Immediate patching of critical vulnerabilities (e.g., CVE-2025-61882)., Proactive dark web monitoring for leaked data., Network segmentation to limit lateral movement., Implement mandatory cybersecurity training, strengthen defenses against future attacks, Implement **unified visibility** of all non-human identities (OAuth apps, API keys, service accounts, bots) across SaaS applications using automated discovery tools., Review Mandiant's advisory for additional mitigation strategies., Enhance monitoring for unauthenticated HTTP requests targeting Oracle EBS components., Monitor for signs of data exfiltration, especially via BI Publisher components., Enforce **least privilege** for NHIs by auditing and restricting overly permissive access scopes. Ensure integrations and tokens can only access the data they explicitly require., International cooperation for cross-border cybercrime investigations., Collaboration with vendors (e.g., Oracle) for out-of-band patches., Hardware vendors must adopt secure-by-design principles (Unitree)., Apply patches from Oracle's Critical Patch Update (CPU) and restrict network access to affected HTTP ports if immediate patching is not possible., Limit data retention to reduce the risk of exposure (e.g., avoid storing unnecessary sensitive data like Social Security numbers)., Monitor for leaked credentials and misconfigurations, Educate teams on the risks of NHIs and integrate NHI security into broader **identity and access management (IAM)** strategies., Adopt phishing-resistant authentication (e.g., passkeys, FIDO2 WebAuthn)., Restrict internet exposure of EBS applications and enforce authentication controls., Implement adaptive risk assessments to detect anomalous access patterns., Enhance cybersecurity training and awareness programs, focusing on non-punitive approaches., Enhance AML controls for cryptocurrency transactions (DOJ)., Investment in AI-driven anomaly detection systems., Collaborate with threat intelligence providers (e.g., Okta) for IOCs., Implement multi-factor authentication (MFA) for all critical systems., Secure exposed Docker APIs, Kubernetes clusters, and Ray dashboards, Enhance security for executive personal data, Evaluate the need for network segmentation to limit lateral movement in case of breaches., Segment Networks to Limit Lateral Movement, Enhance logging and network segmentation for Oracle EBS environments., Monitor for IoCs, including the listed IP addresses (200.107.207[.]26, 185.181.60[.]11) and exploit artifacts., Foster partnerships between IT, security teams, and faculty to align research needs with cybersecurity protocols., Change Passwords, Regular employee training on phishing and social engineering., Educate employees about phishing and extortion email tactics., Apply **compensating controls** for NHIs where MFA is not feasible (e.g., IP restrictions, scoped access, session monitoring)., Engage threat intelligence services (e.g., CrowdStrike, Mandiant) for proactive detection., Immediately patch Oracle E-Business Suite to the latest version., Immediate patch deployment (KB878741), upgrade to supported releases if running end-of-life software, Enhance Security Measures, Investigate Oracle E-Business Suite environments for unusual access or compromise, Adopt adaptive security measures like behavioral WAFs and enhanced monitoring to detect and respond to threats more effectively., Segment cloud networks to limit lateral movement, Deploy behavioral analytics to detect beaconing and tracking scripts., Enhance detection of automated exploitation attempts, Accelerate zero-day response timelines with automated patch management (Microsoft)., Immediate patching of CVE-2025-61882 for Oracle EBS versions 12.2.3–12.2.14, Install Oracle's patch for CVE-2025-61882 immediately, Leverage **Dynamic SaaS Security Platforms** (e.g., Reco) to automate detection, response, and remediation for NHI-related risks, including token revocation and integration quarantine., Implement behavioral analysis for XSLT injection attempts, Seek legal help to understand rights and pursue compensation, Adoption of zero-trust architectures and multi-factor authentication (MFA)., Restrict access to property management systems with zero-trust principles. and Isolate and monitor high-value code repositories (F5)..
Most Recent Source: The most recent source of information about an incident are The Register, Alias Robotics Unitree G1 Analysis, BleepingComputer Article, Shamis & Gentile P.A., Google Blog Post, LinkedIn Post by Charles Carmakal (Mandiant CTO), Bloomberg Law, Oracle Security Alerts (CVE-2025-61882, CVE-2025-21884), Recorded Future News, TeamPCP Telegram channel, Oracle Security Advisory, DarkWeb Informer forum (threat actor 'igotafeeling'), Mandiant (Google Cloud) Alert on Cl0p Campaign, SEC Filing (8-K), Lynch Carpenter, LLP, SOCRadar analysis, Loblaw Press Release (March 12), CISA KEV Catalog, TechRadar, U.S. Department of Justice Press Release, Oracle Security Advisory (Rob Duhart, CSO), Microsoft Security Blog (Vanilla Tempest), Dark web post by CL0P ransomware group, Google Threat Intelligence & Mandiant Analysis, Attorney General of the Commonwealth of Massachusetts, Reco Blog: 'The Hidden Risk of Non-Human Identities in SaaS', Hypertherm breach notification, THE RAVEN FILE (Security Research), Z2Data Supplier Risk Analysis, Oracle Critical Patch Update (CPU), The Hacker News, CISA Advisory (January 2023 Oracle Incident), THE RAVEN FILE Security Researchers, Comparitech, Mandiant (Google Cloud) & GTIG Analysis, IBM Cost of a Data Breach Report, Hypertherm, Inc. Breach Notification, Cyber Incident Description, Clop Dark Web Leak Site, The Independent, Cybersecurity Ventures, Michelin Public Statement, Oracle Security Alert (CVE-2025-61882), CISA Alerts, University of Phoenix Official Website, Mandiant (Google-owned cybersecurity firm), Edelson Lechtzin LLP, CL0P dark web post, SecurityWeek, Oracle Security Alert, Flare (security firm), Cisco Security Advisory (CVE-2025-20352), Oracle Security Advisory (CVE-2025-61882), F5 Security Advisory, Legal filing in U.S. Eastern District Court, Maine Attorney General’s Office, UK National Cyber Security Centre (NCSC), watchTowr Labs (PoC Analysis), Oracle Security Alert (October 2025), BleepingComputer, Oracle Security Alert Advisory, Microsoft Security Update Guide, Clop Ransomware Dark Web Leak Site, Incident disclosure by SUNY Research Foundation, U.S. State Department Rewards for Justice Program (Clop), Okta Threat Intelligence (contributor: Moussa Diallo), Mandiant/GTIG Warning, Author: Gal Nakash (CPO and Cofounder, Reco), Incident Report, SecurityAffairs, Help Net Security, Chronicle of Higher Education, Proofpoint 2025 Healthcare IT Report, California Office of the Attorney General, TechCrunch, U.S. Cybersecurity and Infrastructure Security Agency (CISA), Distributed Denial of Secrets, CrowdStrike Report on CVE-2025-61882 Exploitation, U.S. State Department Reward Program, Emsisoft (MOVEit Impact Report), Google Mandiant (Charles Carmakal, CTO) - LinkedIn Post, Cloudflare 2025 Q4 DDoS Threat Report, CrowdStrike Blog and Maine Attorney General’s Office (Breach Notification).
Most Recent URL for Additional Resources: The most recent URL for additional resources on cybersecurity best practices is https://www.state.gov/rewards-for-justice-program/, https://www.cisa.gov/, https://techcrunch.com/2023/10/05/google-clop-oracle-zero-day-hack/, https://blog.google/threat-analysis-group/clop-oracle-zero-day/, https://www.oracle.com/security-alerts/, https://securityaffairs.co/wordpress/150000/hacking/oracle-ebs-flaw-cve-2025-61884.html, https://msrc.microsoft.com/update-guide, https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://www.bleepingcomputer.com, https://www.securityweek.com, https://thehackernews.com, https://www.techradar.com, https://news.bloomberglaw.com, https://www.cisa.gov, https://www.ibm.com/reports/data-breach, https://www.z2data.com, Tor network (dark web) .
Current Status of Most Recent Investigation: The current status of the most recent investigation is Ongoing.
Most Recent Stakeholder Advisory: The most recent stakeholder advisory issued was warn customers about impersonation attempts, share indicators of compromise (IOCs) with industry peers, Mandiant/GTIG Warning to Corporate Executives, Oracle and Mandiant have issued public advisories urging immediate action., Oracle customers urged to patch immediately, Executives warned about extortion emails, Oracle Urgent Patching Advisory, CrowdStrike Threat Assessment, Oracle and Google have issued advisories with technical details for detection and mitigation., Oracle Customers Urged to Patch Immediately, Executives Warned About Extortion Emails, Oracle customers urged to apply patches immediately., Microsoft recommends prioritizing zero-day patches., F5 advises BIG-IP customers to monitor for suspicious activity., Adobe urges AEM JEE users to verify configurations., Microsoft Teams users warned of malicious installers., Cisco issues advisory for IOS/IOS XE users., DOJ warns financial institutions about crypto scam indicators., Alias Robotics recommends disabling Bluetooth on Unitree G1., HHS issues alert on healthcare cyberattack surge., Notification letters to affected individuals, Public statements via regulatory filings, Oracle security alerts urging immediate patching, Mandiant’s analysis of Cl0p’s modus operandi, Notification letters mailed to affected individuals, public disclosure on website, Universities have issued public statements to stakeholders about the breaches and steps taken to mitigate risks., Oracle emphasizes the need for immediate patch deployment to secure identity management infrastructure, .
Most Recent Customer Advisory: The most recent customer advisory issued were an Oracle urged Micros customers to change their passwords and any passwords used by Micros representatives to access their on-premise systems., Private letters to customers, avoid clicking on sponsored search ads for hospitality servicesverify URLs before entering credentialsreport suspicious login pages, Recommended: Investigate Oracle E-Business Suite for compromise, Customers advised to patch and investigate potential compromise., Patch installation guidanceIoCs for detecting compromise, Extortion Emails from Clop to Executives, Organizations using Oracle E-Business Suite advised to apply patches and monitor for suspicious activity., Apply Emergency Patches for CVE-2025-61884 and CVE-2025-61882Monitor for Suspicious Activity, Oracle: 'Apply CVE-2025-61884 patch within 48 hours.'Microsoft: 'October 2025 updates include critical zero-day fixes.'F5: 'No evidence of customer data exposure, but monitor systems.'Adobe: 'Audit AEM Forms configurations for CVE-2025-54253.'Microsoft: 'Verify Teams installer signatures.'Cisco: 'Update IOS/IOS XE devices to mitigate rootkit risk.'Unitree: 'Avoid public Wi-Fi; update robot firmware.'CDC: 'Healthcare orgs must treat cybersecurity as patient safety issue.', , Extortion emails sent to victims via support@pubstorm[.]com, Free credit monitoring offered to affected parties, Companies advised to monitor for data leaks on Cl0p’s blog or dark web marketplaces, 24 months of complimentary credit monitoring services provided to affected individuals, Free identity protection services offered (credit monitoring, identity theft recovery, dark web monitoring, $1 million fraud reimbursement policy), Affected individuals notified via written notice on Dec. 22, 2025, Notifications sent to affected individuals, Affected employees were notified last week, Notified impacted individuals, Notification via mail to affected customers, Written notifications sent to affected individuals on February 27, 2026, Loblaw customers with PC Optimum accounts, Shoppers Drug Mart loyalty cards, or prescription histories advised to monitor for potential fraud, Notification to affected individuals, One year of free identity monitoring through Kroll, including credit monitoring, fraud consultation and and identity theft restoration.
Most Recent Entry Point: The most recent entry point used by an initial access broker were an CVE-2025-61882 (Oracle E-Business Suite zero-day), Oracle E-Business Suite (EBS) zero-day vulnerability (CVE-2025-61882), Compromised employee credentials, CVE-2021-35587, Oracle EBS zero-day vulnerability, Oracle E-Business Suite Concurrent Processing Component (via HTTP), Zero-Day Vulnerability in Oracle E-Business Suite (Network-Based, No Authentication Required), Compromised Email Accounts, Oracle EBS vulnerability, Zero-day exploit (CVE-2025-61882) in Oracle E-Business Suite, potential Oracle E-Business Suite (EBS) exploit, OA_HTML/SyncServlet (Authentication Bypass) & OA_HTML/RF.jsp (XSLT Injection) and Phone-based phishing (social engineering).
Most Recent Reconnaissance Period: The most recent reconnaissance period for an incident was Likely conducted prior to August 2025 (exploitation began in August), Potentially since early August 2025 (zero-day exploitation), Since at least 2023-07-10, Potentially Began on 2025-07-10 (Prior to July Patches), Months (Scam), , Observed as early as June 2025, active exploitation from August 2025, Likely conducted prior to August 2025 (exploitation start date), Potentially since July 2025 (part of broader Cl0p campaign), Since late September 2023 (pre-exploitation activity).
Most Significant Root Cause: The most significant root cause identified in post-incident analysis was Vulnerable software version, compromised subdomain, Over-reliance on traditional MFA methods vulnerable to real-time phishing.Lack of visibility into malvertising campaigns targeting brand impersonation.Insufficient monitoring for typosquatted domains and beaconing activity., Zero-day vulnerability (CVE-2025-61882) in Oracle E-Business Suite.Lack of authentication requirements for exploitation.High-volume email campaign leveraging compromised accounts (per Mandiant)., Zero-day vulnerability (CVE-2025-61882) in Oracle E-Business SuiteInsufficient proactive patching for prior vulnerabilities (July 2025 patches bypassed), Unpatched Oracle EBS vulnerability (CVE-2025-61882)Internet-exposed EBS applications without authentication safeguardsDelayed patching despite active exploitation, Unpatched Zero-Day Vulnerability in Oracle E-Business SuiteInadequate Initial Response by Oracle (Premature Claim of Patch Effectiveness)Lack of Network Segmentation or Access Controls to Limit Exploitation, Unpatched Vulnerabilities in Oracle E-Business SuiteLack of Authentication for Remote ExploitationPotential Weaknesses in Default Password Reset MechanismsDelayed Patch Deployment by Some Customers, Unpatched Oracle EBS vulnerability.Zero-day exploitation before patches (Microsoft).Insufficient source code protection (F5).Adobe AEM misconfiguration oversight.Certificate authority process gaps (Microsoft).Delayed Cisco IOS/XE patching.Lack of crypto transaction monitoring (DOJ).Insecure Bluetooth implementation (Unitree)., Lack of visibility and oversight for non-human identities (OAuth tokens) with excessive privileges.Public exposure of a GitHub API token due to misconfiguration or lack of secret management.Incomplete incident response: human credentials were rotated, but non-human credentials (API tokens) were overlooked, leaving a backdoor open.Overprivileged NHIs: integrations and tokens had broader access than necessary, increasing the blast radius of compromises., Zero-Day Exploit (CVE-2025-61882)Delayed Patch Release (exploited for months pre-patch)Reused Attack Infrastructure from MOVEit (CVE-2023-34362), Unpatched zero-day vulnerability (CVE-2025-61882) in Oracle EBSLack of pre-authentication protections for SyncServlet endpointReuse of attack infrastructure from prior campaigns (e.g., MOVEit CVE-2023-34362), Unpatched zero-day vulnerability (CVE-2025-61882) in Oracle E-Business Suite.Delayed detection (weeks between intrusion and discovery).Lack of proactive threat hunting for ERP-specific attacks.Potential gaps in network segmentation or access controls., Unpatched zero-day vulnerabilities in Oracle EBS (CVE-2025-61882, CVE-2025-21884).Lack of real-time monitoring for unauthenticated HTTP requests targeting critical components (BI Publisher, Configurator UI).Supplier risk blind spots in enterprise software supply chains., Exploitation of zero-day vulnerability in Oracle E-Business Suite (CVE-2025-61882), Human error (falling for phishing attacks)Decentralized IT departments creating inconsistent security protocolsLack of centralized control over technology useExcessive data retention (e.g., storing Social Security numbers unnecessarily)Faculty resistance to IT policies due to perceived restrictions on academic freedom, Flaw in how WebLogic Server Proxy Plug-ins process incoming requests, Supply chain vulnerabilitiesStolen credentialsSocial engineeringIT-OT convergence risks, Compromised IoT devices and routers, primarily Android TVs, Zero-day vulnerability in Oracle’s eBusiness Suite, Cloud misconfigurationsExposed management servicesLeaked credentials, Exploitation of Oracle PeopleSoft vulnerability via compromised employee credentials, Vulnerability in Oracle eBusiness Suite (third-party vendor), Exploited vulnerability in Oracle E-Business Suite (EBS), Exploitation of Oracle EBS zero-day vulnerability, Unpatched software vulnerability in Oracle EBS, Vulnerabilities in Oracle E-Business Suite, Critical RCE vulnerability in Oracle Identity Manager and Web Services Manager.
Most Significant Corrective Action: The most significant corrective action taken based on post-incident analysis was Replace SMS/email-based MFA with phishing-resistant alternatives.Proactively register defensive domains to prevent typosquatting.Enhance threat intelligence sharing within the hospitality sector.Deploy solutions to detect and block malicious ads in search results., Emergency patch release by Oracle.Public disclosure and customer advisories.Collaboration with Mandiant for threat intelligence sharing., Patch deploymentCustomer advisory for IoC monitoring, Apply Oracle’s security patch for CVE-2025-61882.Implement network segmentation for EBS environments.Deploy behavioral detection for RCE attempts (e.g., CrowdStrike Falcon).Conduct threat hunting for signs of Clop or GRACEFUL SPIDER activity., Oracle Released Emergency Patches and AdvisoriesGoogle Shared Detection Indicators for Affected OrganizationsRecommended Enhanced Monitoring for Extortion Emails and Unusual Data Access, Oracle Released Out-of-Band PatchesCustomers Advised to Apply Patches and Monitor SystemsEnhanced Threat Intelligence Sharing (e.g., POC Disclosure as IOC), Oracle: Accelerate vulnerability disclosure timelines.Microsoft: Expand zero-day detection capabilities.F5: Enhance code repository security controls.Adobe: Automate configuration audits for AEM.Microsoft: Implement certificate transparency logging.Cisco: Harden IOS/XE against rootkit persistence.FinCEN: Update crypto transaction reporting rules.Unitree: Partner with security firms for firmware audits., Adopt a **Dynamic SaaS Security Platform** to automate discovery, monitoring, and remediation of NHIs.Implement **least privilege enforcement** for all NHIs, auditing and restricting access scopes to the minimum required.Deploy **real-time anomaly detection** for NHI behavior, with automated responses to suspicious activity (e.g., token revocation).Establish **automated credential rotation** for NHIs, ensuring tokens and keys are regularly refreshed and unused credentials are disabled.Conduct **comprehensive NHI inventories** across all SaaS applications, classifying identities by type and risk level.Integrate **NHI security into IAM strategies**, treating machine identities with the same rigor as human accounts.Enforce **compensating controls** for NHIs (e.g., IP restrictions, session monitoring) where MFA is not applicable.Educate security and DevOps teams on the risks of NHIs and the importance of token hygiene (e.g., avoiding hardcoding, public exposure)., Patch deployment (October 2025)Infrastructure monitoring for 96 linked IPs (41 subnets reused from MOVEit), Applied Oracle’s emergency patch (2025-10-04).Enhanced monitoring for ERP systems.Review of third-party software patching policies.Potential restructuring of incident response protocols to reduce detection lag., Immediate application of Oracle-provided security patches.Enhanced supplier risk assessments using SCRM platforms (e.g., Z2Data).Implementation of behavioral WAFs or anomaly detection for Oracle EBS environments.Review of third-party software dependencies for similar vulnerabilities., Removing hackers' access to systemsStepping up security protocolsEnhancing cybersecurity training for faculty and staff, Patches released, network access restrictions recommended, Mandatory cybersecurity training, strengthened defenses, Oracle released an urgent patch, Vulnerability patched, containment measures implemented, Patch deployment, upgrade to supported versions.
.png)
A security flaw has been discovered in itsourcecode Payroll Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /manage_user.php of the component Parameter Handler. Performing a manipulation of the argument ID results in sql injection. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks.
A vulnerability was identified in Axiomatic Bento4 up to 1.6.0-641. Affected is the function AP4_BitReader::SkipBits of the file Ap4Dac4Atom.cpp of the component DSI v1 Parser. Such manipulation of the argument n_presentations leads to heap-based buffer overflow. The attack needs to be performed locally. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.
A vulnerability was determined in Axiomatic Bento4 up to 1.6.0-641. This impacts the function AP4_BitReader::ReadCache of the file Ap4Dac4Atom.cpp of the component MP4 File Parser. This manipulation causes heap-based buffer overflow. The attack needs to be launched locally. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.
iccDEV provides a set of libraries and tools for working with ICC color management profiles. Prior to version 2.3.1.6, there is a heap-buffer-overflow (HBO) in icAnsiToUtf8() in the XML conversion path. The issue is triggered by a crafted ICC profile which causes icAnsiToUtf8(std::string&, char const*) to treat an input buffer as a C-string and call operations that rely on strlen()/null-termination. AddressSanitizer reports an out-of-bounds READ of size 115 past a 114-byte heap allocation, with the failure observed while running the iccToXml tool. This issue has been patched in version 2.3.1.6.
iccDEV provides a set of libraries and tools for working with ICC color management profiles. Prior to version 2.3.1.6, there is a stack-buffer-overflow (SBO) in CIccTagFixedNum<>::GetValues() and a related bug chain. The primary crash is an AddressSanitizer-reported WRITE of size 4 that overflows a 4-byte stack variable (rv) via the call chain CIccTagFixedNum::GetValues() -> CIccTagStruct::GetElemNumberValue(). This issue has been patched in version 2.3.1.6.

Get company history
Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.
Identify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.
Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.
Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.
Leverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.