company logo

Product

Our Product

We are Reshaping the way Developers find and fix vulnerabilities before they get exploited.

Solutions

By Industry

BFSI

Healthcare

Education

IT & Telecom

Government

By Role

CISO

Application Security Engineer

DevsecOps Engineer

IT Manager

Resources

Resource Library

Get actionable insight straight from our threat Intel lab to keep you informed about the ever-changing Threat landscape.

Subscribe to Our Weekly Threat Digest

Company

Contact Us

Have queries, feedback or prospects? Get in touch and we shall be with you shortly.

loading..
loading..
loading..
Loading...

Data Breach

LAUSD

Vice Society

loading..
loading..
loading..

500 GB of LAUSD data stolen claims to be act of Vice Society group

LAUSD ransomware attack resulted in the theft of 500GB data of nearly 650,000 students claiming to be an act of the Vice Society group…

10-Sep-2022
4 min read

No content available.

Related Articles

loading..

Clop Ransomware

Clop hackers demand $50M in Oracle EBS breach. Oracle confirms unpatched July 20...

A notorious ransomware gang has launched a digital siege on corporate America, and the bullseye is on one of the world's most critical business platforms: **Oracle E-Business Suite (EBS)**. Forget vague threats—this is a high-stakes, personalized shakedown. The group, widely linked to the infamous **Clop** ransomware cartel, is sending direct extortion emails to C-level executives, claiming to have already stolen their most sensitive corporate data. The demand? In one confirmed case, a chilling **$50 million**. The most alarming part? Oracle has confirmed the attack and directly links it to known security holes that they patched back in **July 2025**. This means every company that delayed this critical update is now exposed and actively in the crosshairs. ### **Attack Blueprint: How the Hackers Are Breaking In** This isn't a sophisticated zero-day mystery. Oracle's Chief Security Officer, Rob Duhart, has publicly stated their investigation points to the "**potential use of previously identified vulnerabilities that are addressed in the July 2025 Critical Patch Update**." **The keys to the kingdom were left under the mat, and the burglars are now inside.** The July patch fixed a total of **309 vulnerabilities** across Oracle's products. But for EBS users, these nine are your nightmare. Three of them are particularly dangerous because attackers can exploit them **without needing a username or password.** | **CVE ID** | **CVSS Score** | **Component** | **Remote Exploit?** | **Why It's Dangerous** | | :--- | :--- | :--- | :--- | :--- | | CVE-2025-30746 | 6.1 | Oracle iStore | **YES** | Public-facing, no login required for attack. | | CVE-2025-30745 | 6.1 | MES for Process Manufacturing| **YES** | Critical supply chain system exposed. | | CVE-2025-50107 | 6.1 | Universal Work Queue | **YES** | Core operational dashboard is vulnerable. | | CVE-2025-30743 | 8.1 | Lease and Finance Management | No | High-severity flaw in financial data. | | CVE-2025-30744 | 8.1 | Mobile Field Service | No | High-severity flaw in mobile operations. | **Hacker's Playbook is Simple:** 1. **Scan** for unpatched, internet-facing Oracle EBS systems. 2. **Exploit** one of the vulnerabilities above to gain access. 3. **Exfiltrate** gigabytes of financial, HR, and operational data. 4. **Extort** by emailing the CEO with a multi-million dollar demand and "proof" of the theft. ### **Trail of Extortion Email** The emails are designed to trigger panic in the boardroom. They don't sound like a typical spammer; they sound like a ruthless business partner. * **"We are the CL0P team."** They immediately establish their feared brand identity. * **"We have copied your company's documents and databases."** A direct claim of total compromise. * **"We offer you a chance to get out of this situation."** Framing the ransom as a "business solution." * **"We can provide you with 3-5 files or 50-100 lines from any database as proof."** This is the masterstroke that turns fear into certainty, forcing executives to take the threat seriously. Security firm Mandiant has confirmed the infrastructure and email addresses used in this campaign are directly tied to the **FIN11 group**, a known affiliate of Clop, famous for its massive attacks on file-transfer tools like MOVEit. ### **How to Avoid Being the Next Victim** If your company runs Oracle EBS, this is not a drill. Your action plan is straightforward but non-negotiable. 1. **PATCH. NOW.** Apply the **July 2025 Critical Patch Update (CPU)** immediately. This is the single most important action you can take. Delay is an invitation for catastrophe. 2. **Assume You're Breached.** Don't wait for the extortion email. Initiate threat hunting in your EBS environment *now*. Look for unusual logins, large data exports, and any signs of the IOCs linked to this campaign. 3. **Lock Down Access.** Immediately review and secure all internet-facing EBS logins. Implement **Multi-Factor Authentication (MFA)** everywhere possible to stop credential-based attacks. 4. **Train Your Executives.** Ensure your C-suite knows these emails are circulating and has a clear protocol to report them directly to security teams—not to panic and pay. For thousands of organizations, applying a patch from three months ago is the only thing standing between them and a multi-million dollar shakedown. The time for action was yesterday. The next best time is right now.

loading..   03-Oct-2025
loading..   4 min read
loading..

GitLab

Red Hat's GitLab breach exposes customer network blueprints, posing a widespread...

A cyberattack on Red Hat's consulting division stole sensitive customer documents containing network configurations and credentials, creating potential downstream security risks for thousands of organisations. ## Incident Overview Red Hat, the open-source software giant now owned by IBM, has confirmed a significant security breach. The incident involved unauthorized access to a self-managed **GitLab instance** used exclusively by its internal **Red Hat Consulting** team . Upon detecting the intrusion, Red Hat's security team took action by removing the threat actor's access, isolating the compromised instance, and launching an investigation . The company has stated that the breach is contained and does not impact its core products or software supply chain . ## Scope of the Data Breach A cybercrime group calling itself **"Crimson Collective"** has claimed responsibility for the attack. While Red Hat has confirmed data was copied, it has not verified the attackers' specific claims . The table below summarizes the key details of the stolen data based on public claims and Red Hat's statements: | Aspect | Details | | :--- | :--- | | **Claimed Data Volume** | Nearly **570 GB** of compressed data . | | **Claimed Repositories** | Approximately **28,000** internal development repositories . | | **Key Data Type** | Roughly **800 Customer Engagement Reports (CERs)** from 2020-2025 . | | **Red Hat's Confirmation** | The instance housed consulting data like project specs, code snippets, and internal communications . | ## Understanding Customer Engagement Reports (CERs) The most significant threat from this breach stems from the exposure of Customer Engagement Reports (CERs). These are not standard marketing documents but **detailed technical and architectural blueprints** created by Red Hat's consultants . According to cybersecurity advisories and analysis, these CERs can contain : - **Infrastructure details:** Comprehensive network topologies and system configurations. - **Authentication tokens and keys:** Credentials that could grant access to customer systems. - **Configuration data:** Sensitive settings for platforms and applications. The Centre for Cybersecurity Belgium (CCB) has assessed this breach as a **"high risk"** because this information could be weaponized to breach customer networks directly . The stolen data allegedly pertains to a wide range of high-profile organizations, including telecoms, financial institutions, and government agencies . ## Essential Steps for Potential Impacted Organisations If your organisation is or has been a Red Hat Consulting customer, you should take immediate proactive measures. The following checklist outlines critical actions to protect your environment. ![deepseek_mermaid_20251003_d8a99a.png](https://sb-cms.s3.ap-south-1.amazonaws.com/deepseek_mermaid_20251003_d8a99a_b41f12958c.png) ## Ongoing Investigation Key details about the breach remain unclear, leaving customers with unresolved concerns: - **Initial Access Vector:** The specific vulnerability or method the attackers used to breach the GitLab instance has not been disclosed . - **Dwell Time:** It is unknown how long the attackers had access to the system before detection. The hackers claim the intrusion occurred roughly two weeks before Red Hat's announcement . - **Extortion Demands:** Crimson Collective has stated it is an "extortion ransomware group" . Red Hat has not commented on whether it received or is negotiating with any extortion demands. ## Responsible Reporting This incident highlights the sophisticated threats facing software supply chains and the critical importance of securing development and collaboration environments. Red Hat's core product integrity remains intact, but the breach shows that **attack surfaces extend beyond code to include internal documents and communications** . It is also crucial to note that **GitLab's own platform and infrastructure were not compromised** . This incident involved Red Hat's self-managed instance of GitLab Community Edition, for which the customer is responsible for security, maintenance, and applying patches . This is a developing story. As the investigation continues, more specific guidance for affected customers is expected from Red Hat. For the latest official information, monitor the **[Red Hat security blog](https://access.redhat.com/articles/7132207)** .

loading..   03-Oct-2025
loading..   3 min read
loading..

Deepfake

Telecom

Near-monthly breaches rocked South Korea in 2025—deepfakes, rogue base stations,...

South Korea’s world-class internet and tech prowess collided with a relentless wave of near-monthly cyber incidents in 2025, exposing a reactive, fragmented defense posture unfit for a nation at the core of global digital supply chains. From telecom giants and financial institutions to government-adjacent targets, the impacts were sweeping—forcing an urgent rethink at the highest levels of power. ### Key revelations - A near-monthly drumbeat of major incidents spotlighted systemic coordination gaps and the absence of a clear cyber “first responder,” amplifying risk across critical sectors. - Experts warned that reactive governance, siloed agencies, and a deep talent shortage created a vicious cycle where quick fixes replaced durable resilience. - A late-year pivot toward interagency centralization from the presidential office aims to accelerate response—while raising new debates over oversight and accountability. ### 2025 timeline at a glance - January: GS Retail breach exposed about 90,000 customers’ personal data after sustained website attacks straddling the New Year period. - February: Wemix (Wemade) lost $6.2 million to a hack on Feb. 28, with disclosure delayed until March, fueling investor anxiety. - April–May: SK Telecom’s mega-breach compromised data for roughly 23 million customers, triggering mass SIM replacements and a protracted fallout. - June: Yes24 was crippled by ransomware on June 9, with services down for days before restoration by mid-month. - July: North Korea–linked Kimsuky used AI-generated deepfake images in spear-phishing against defense-related entities, marking a chilling escalation in tradecraft. - July: Seoul Guarantee Insurance suffered ransomware that paralyzed core guarantee services, stranding customers and markets in uncertainty. - August: Yes24 was hit again; Lotte Card lost around 200GB of data affecting roughly 3 million customers over 17 undetected days; a Welcome Financial affiliate faced Russian-linked claims of over 1TB exfiltration. - September: KT disclosed a breach via illegal “fake base stations,” exposing thousands to IMSI/IMEI capture and unauthorized micro-payments—a first-of-its-kind shock to telecom trust. ### Why the defenses cracked South Korea’s cyber governance spanned multiple ministries and regulators that too often scrambled in parallel, deferring to one another instead of operating as a single, empowered crisis unit. The result was slower containment, mixed messaging, and a pattern of incident-driven fixes rather than systemic hardening aligned to national critical infrastructure priorities. ### Expert Alarm Industry leaders argue the nation treats cybersecurity as episodic crisis management, not as a cornerstone of national resilience, starving long-term investments in architecture and skills. The chronic shortage of trained defenders compounds exposure—without skilled talent, proactive defenses and sustained threat hunting simply cannot scale. ### A government pivot Responding to the compounding shocks, the National Security Office advanced a “comprehensive” interagency cyber plan led from the presidential office to cut through silos and accelerate incident response. Regulators also signaled new legal powers to investigate at the first hint of compromise—even absent a company report—to finally close the first-responder gap. ### Oversight Debate Central control promises speed, but concentrating authority risks politicization and overreach if not paired with independent checks, experts caution. A hybrid model—central strategy and crisis coordination with technical execution by specialist agencies like KISA under clearer rules—emerges as the balanced path forward. ### Threats redefining the battlefield - AI-powered deception: Kimsuky’s deepfake military IDs supercharge spear-phishing, fusing social engineering with synthetic media to breach high-trust environments. - Telecom edge abuse: From mass data theft at SK Telecom to KT’s rogue base-station exploitation, attackers are increasingly weaponizing the seams between IT, subscriber identity, and network access. - Ransomware resiliency gaps: Repeat hits against Yes24 and disruptive attacks on financial rails like SGI reveal operational weak points and recovery shortfalls under sustained pressure. ### What must change now - Establish a single operational first responder with clear legal authority to coordinate, compel action, and communicate consistently across ministries and sectors in real time. - Fund workforce pipelines and retainers for surge capacity, ending the quick-fix cycle and enabling continuous threat hunting and architecture hardening in telecom and finance. - Mandate fast, standardized disclosure and post-incident audits to drive sector-wide learnings and public trust following large-scale breaches.

loading..   02-Oct-2025
loading..   4 min read