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...

ComCast

loading..
loading..
loading..

Massive Comcast Data Breach Exposes 230,000+ Customers' Personal Info!

Over 230,000 Comcast customers' personal data exposed in a massive ransomware attack on a third-party vendor. Learn more about the breach and its impact.

07-Oct-2024
6 min read

No content available.

Related Articles

loading..

SitusAMC

Data breach at SitusAMC, a financial services vendor, exposed homeowner and empl...

For millions of Americans, their mortgage is a deeply personal, often stressful, cornerstone of their financial life. They deal with their bank, make their payments, and trust that the complex machinery behind the scenes is secure. That trust was fractured earlier this year when SitusAMC, a powerhouse in the commercial and residential real estate finance industry, announced it had been the victim of a massive ransomware attack, exposing the sensitive data of over 1.5 million individuals. But the breach of SitusAMC is more than just another entry in the long list of corporate cyberattacks. A deeper investigation reveals a story of critical contextual nuances: it’s a breach not of a consumer-facing company, but of a critical, invisible linchpin in the financial system; an attack that highlights the profound risks of third-party service providers; and an event whose fallout lands disproportionately on individuals who never knew the company's name. **The "Invisible" Target with a Treasure Trove of Data** Unlike a breach at a retailer or a social media platform, SitusAMC operates deep in the background. Most consumers have never heard of them, yet the company provides "servicing" and "sub-servicing" for a vast portfolio of mortgages. This means they are responsible for the administrative backbone of loans—processing payments, managing escrow accounts, handling foreclosures, and, crucially, storing the immense volumes of documentation required by these processes. _"This is the critical nuance that makes this breach so severe,"_ explains Dr. Aris Thorne, a cybersecurity professor at Georgetown University. "SitusAMC is what's known as a 'target-rich environment.' They don't just have one type of data; they have *all* of it. For a single individual, an attacker could potentially get their Social Security number, mortgage application, tax returns, credit history, bank account details, and driver's license copy—all from one place. It's a one-stop shop for identity theft." The attackers, the notorious ALPHV/BlackCat ransomware cartel, knew exactly what they were targeting. They didn't just lock files; they exfiltrated over 2 terabytes of data, holding it for ransom with the threat of releasing it onto the dark web. **The Ripple Effect: When a "Vendor" Breach Becomes "Your" Breach** The second critical nuance lies in the chain of responsibility. Many of the affected individuals did not have a direct relationship with SitusAMC. Their loan was with a local bank or a major lender, which had contracted SitusAMC to handle the back-office work. "This creates a confusing and fragmented response for the victim," says Maria Flores, a consumer advocate with the National Fair Housing Alliance. "You get a letter from a company you've never heard of, about a loan you have with your bank. It erodes trust and creates immense confusion. Who is ultimately responsible? Your bank will often point to the vendor, and the vendor points to the fact that they are acting on the bank's behalf. The consumer is left in the middle." This "supply chain" attack vector is a growing nightmare for regulators. The breach didn't happen at the point of sale (the bank), but at a critical support node. It underscores a harsh reality: a company's cybersecurity is only as strong as the weakest link in its extended network of partners and vendors. **The Human Impact: A Legacy of Vulnerability** The data exposed isn't just current information. The breach includes data from "former homeowners," a phrase that carries its own heavy weight. "For individuals who went through a foreclosure, a short sale, or even those who simply paid off their loan years ago, this breach reopens old wounds," Flores notes. "Their financial situation may have been precarious during that time, and this data provides a snapshot of their most vulnerable moment. To have that exposed adds a layer of psychological distress to the financial risk." Furthermore, for current homeowners, the breach creates a unique form of anxiety. The theft of ongoing mortgage and financial account information means the threat isn't just about a new credit card being opened fraudulently; it's about the potential for sophisticated fraud targeting their largest asset—their home. **A Tepid Response in a High-Stakes Environment** SitusAMC's response, while following standard protocol, has been criticized for not matching the severity of the exposed data. The offer of 24 months of credit monitoring, while standard, is seen by experts as a band-aid on a gaping wound. "Credit monitoring is reactive; it tells you *after* something bad has happened," says Dr. Thorne. "With the depth of information stolen—including SSNs and driver's licenses—the threat of identity theft is lifelong. The criminals can sit on this data for years before using it. Two years of monitoring is insufficient for a breach of this sensitivity." The incident has prompted calls for stricter regulations governing third-party vendors in the financial sector and for mandatory, long-term identity restoration services, rather than temporary monitoring, in cases involving core identity documents. As the investigation continues and lawsuits mount, the SitusAMC breach serves as a stark lesson. It’s a reminder that in our interconnected financial ecosystem, risk is not always visible, and trust in one company often means implicit trust in a dozen others behind the curtain. For the millions affected, the event is a jarring introduction to a company they never knew held the keys to their financial identity.

loading..   26-Nov-2025
loading..   5 min read
loading..

Scattered Lapsus$

Google reveals a catastrophic supply-chain breach: 200+ companies hacked through...

Google's Threat Intelligence Group (GTIG) has confirmed a catastrophic supply chain attack with a staggering initial scope: data stolen from over 200 companies. The breach vector? Compromised applications from **Gainsight**, a customer success platform, published on the **[Salesforce](https://www.secureblink.com/cyber-security-news/inside-the-billion-record-extortion-blitz-hitting-salesforce-tenants)** ecosystem. But this is far more than a single incident. This is the latest, highly sophisticated maneuver in a sustained campaign by the threat collective **UNC6240** (tracked by Google), also known as **"_[Scattered Lapsus$ Hunters](https://www.secureblink.com/cyber-security-news/lapsus-hackers-elevate-sim-swapping-attacks-to-unprecedented-heights)."_** This group, which includes members of the infamous **ShinyHunters**, is systematically targeting the very connective tissue of the modern enterprise: the trusted integrations between SaaS platforms. ## **Deconstructing Attack Chain - A Timeline of Trust Exploited** The attack demonstrates a chilling understanding of the modern cloud environment. This was not a smash-and-grab; it was a patient, multi-stage operation. | Phase | Tactic & Technique | Context & Insight | | :--- | :--- | :--- | | **1. Initial Access** | **Compromise of [Gainsight](http://gainsight.com/security/) (c. August 2025)** | The group first breached Gainsight's internal systems nearly three months ago. They allegedly gained this initial foothold through a **prior, identical attack on the Salesloft Drift application**. This indicates a **software supply chain cascade**—one breached vendor becomes the stepping stone to the next. | | **2. Persistence & Weaponization** | **Modification of Legitimate Apps** | From within Gainsight's environment, the actors targeted the company's legitimate applications on the Salesforce AppExchange. By compromising these apps, they turned a tool of business operations into a weapon. | | **3. Lateral Movement & Privilege Escalation** | **Abusing OAuth and Trust Relationships** | When a company installs a Gainsight app, it grants the app certain permissions (OAuth tokens) to access Salesforce data. The attackers inherited these permissions. The critical failure? Many companies had granted these apps **excessive, broad-ranging data access (e.g., "Read/Write All")**, far beyond what was necessary for their function. | | **4. Data Exfiltration** | **API-Based Data Harvesting** | Using the compromised apps' legitimate access, the attackers performed automated, large-scale data queries and exports via Salesforce APIs. Because this traffic came from a trusted, whitelisted source, it was incredibly difficult to distinguish from legitimate business activity. | > **Technical Insight:** _"This attack completely bypasses traditional network security controls,"_ [explains](https://status.salesforce.com/generalmessages/20000233) a senior security engineer at a affected firm (who spoke on condition of anonymity). _"The traffic never hits your firewall. It's a trusted entity inside your perimeter, making authorized API calls to your most sensitive data repository. Your SIEM might see it, but without extremely granular behavioral baselines, it just looks like business as usual."_ ## **UNC6240 & "Scattered Lapsus$" Playbook** Understanding the "who" is key to understanding the "why." UNC6240 is not a typical nation-state actor. Their profile points to a financially motivated cybercrime group with a distinct modus operandi, heavily inspired by the original Lapsus$ group. **Key Adversary Characteristics:** * **Motivation:** **Financial Gain**. Their end goal is likely to extort the victim companies, sell the stolen data on dark web forums, or both. * **Tactics:** **Social Engineering & MFA Fatigue**. They are known to use sophisticated phishing and SIM-swapping attacks to compromise employee credentials, often bombarding victims with MFA push notifications until one is accidentally approved. * **Signature:** **Brazen Extortion & Public Shaming**. Like Lapsus$, they publicly name their victims on platforms like Telegram to maximize pressure for ransom payments. Their claims against giants like **CrowdStrike, DocuSign, GitLab, and LinkedIn** fit this pattern perfectly. * **Strategic Focus:** **Software Supply Chains**. They are repeatedly targeting B2B SaaS providers (such as Gainsight and Salesloft) to amplify the impact of their attacks. ## **Not an Isolated Event** To view the Gainsight breach in isolation is to miss the entire story. It is the second central act in a play that began months ago. * **The Precedent: The Salesloft/Drift Breach (August 2025):** The exact same threat actors executed a nearly identical attack through Salesloft's Drift application. **Gainsight was itself a victim of that earlier breach**, which provided the springboard for this current, wider attack. * **The Pattern:** This campaign reveals a deliberate strategy: identify widely used SaaS platforms that have high-level integrations with other critical systems, compromise one, and use it to attack its entire customer base. The attack surface is not a company's own infrastructure, but its web of trusted partners. ## **Moving Beyond "Check the Box" Security** The standard advice of "patch your systems" is meaningless here. The defense requires a fundamental shift in strategy. **Immediate Actions (This Week):** 1. **Conduct a Brutal Third-Party App Audit:** In your Salesforce, M365, Slack, and Snowflake environments, review every connected application. **Immediately revoke access for any that are non-essential or unfamiliar.** Do not delay. 2. **Scrutinize API Logs for Anomalies:** Look for patterns of data access that are abnormal in volume, frequency, or timing. Focus on large data queries and exports, especially from service accounts associated with third-party apps. **Strategic Shifts (Long-Term):** 1. **Embrace Zero Trust for SaaS Integrations:** Apply the principle of **"Least Privilege Access"** ruthlessly. An app like Gainsight, used for customer analytics, should never have blanket "Read All" permissions. Its access should be scoped to specific data objects and fields only. 2. **Implement a CASB or SSPM:** A **Cloud Access Security Broker (CASB)** or **SaaS Security Posture Management (SSPM)** tool can automatically discover shadow IT, enforce security policies on sanctioned apps, and detect anomalous activity across your cloud portfolio. 3. **Assume Breach, Even with Vendors:** Your security model must now account for the compromise of your most trusted vendors. Segment data access, encrypt sensitive fields, and have an incident response plan that includes a "third-party vendor breach" scenario. ### **End of Innocence in the Interconnected Cloud** The Gainsight breach is a watershed moment. It proves that the efficiency and connectivity of the modern SaaS ecosystem have created a systemic risk that we are only beginning to quantify. The perimeter is no longer your network; it's the sum of all permissions you've granted to every third-party application. The attack surface is no longer your public IP range; it’s the entire OAuth token chain across your digital supply chain. This incident is a call to action for CISOs and security teams everywhere: **The era of trusting third-party integrations by default is over. The era of verified, minimal, and continuously monitored access has begun.** ***This is a developing incident. Follow for ongoing technical analysis as more details from forensic investigations become available.***

loading..   24-Nov-2025
loading..   6 min read
loading..

Gafna

Authentication bypass vulnerability, CVE-2025-41115 (CVSS 10.0), allows unauthen...

Grafana has escalated a security alert to critical status, disclosing CVE-2025-41115, a maximum-severity authentication spoofing flaw. The vulnerability lies in the core identity-extraction logic of Grafana’s SAML and JWT authentication integrations. Specifically, the flaw enables a remote, unauthenticated attacker to inject arbitrary identity headers, effectively allowing them to masquerade as any user in the system by forging the `X-Grafana-User` header. This includes assuming the privileges of Grafana instance administrators, leading to a complete compromise of the Grafana environment and any integrated data sources. **Technical Mechanism: Header Manipulation and Trust Violation** The exploit chain is deceptively simple, highlighting a critical failure in the enforcement of trust boundaries. When Grafana is configured to use SAML or JWT authentication, it relies on HTTP headers passed from a reverse proxy or identity provider to identify the user. 1. **The Flaw:** The authentication logic improperly trusts user-supplied values for the header used to designate the authenticated user's identity (e.g., `X-WEBAUTH-USER`). An attacker can directly craft an HTTP request containing a spoofed header, such as `X-Grafana-User: admin`. 2. **The Bypass:** Grafana's backend, failing to validate the provenance and integrity of this header against the actual authenticated session or token, accepts the forged identity. This results in the attacker being granted a session with the targeted user's privileges. 3. **The Impact:** Successful exploitation grants an attacker the same level of access as the spoofed user. With admin rights, they can view all dashboards and data sources, exfiltrate sensitive data, modify data source configurations, and create or delete users, effectively owning the Grafana instance. **Intersection with SCIM Provisioning: An Amplification Vector** This vulnerability directly undermines the security model of System for Cross-domain Identity Management (SCIM) provisioning. SCIM, used for automated user lifecycle management, relies on the integrity of admin-level authentication to create, modify, or deactivate users. * **Compromise Scenario:** An attacker exploiting CVE-2025-41115 to spoof a SCIM administrator could manipulate the entire user base. They could deactivate legitimate administrators, create new admin accounts for persistence, or alter user roles, leading to a permanent and difficult-to-trace backdoor into the enterprise user directory as managed by Grafana. **Mitigation and Immediate Action Required** Grafana Labs has released patched versions for all affected branches: 11.3.9, 10.4.17, and 9.5.21. The remediation is non-negotiable. 1. **Patching:** Upgrade Grafana instances to the patched versions immediately. This is the primary and most effective mitigation. 2. **Configuration Hardening:** For organizations unable to patch instantly, a critical workaround involves configuring the reverse proxy (e.g., Nginx, Apache) to strip the implicated headers (`X-Grafana-User`, `X-WEBAUTH-USER`, etc.) from all **incoming** client requests before they reach the Grafana backend. These headers should only be set internally by the proxy itself based on validated authentication tokens from a trusted IdP. CVE-2025-41115 is not a mere bug; it is a fundamental design flaw in Grafana's external authentication trust model. Its CVSS 10.0 score is warranted, as it provides a direct, low-complexity path for a network-based attacker to escalate from unauthenticated to complete administrative control. The intersection with SCIM transforms a severe instance compromise into a potential identity governance disaster. Security teams must treat this as a top-priority remediation event, prioritizing patching above all other non-critical maintenance tasks.

loading..   21-Nov-2025
loading..   3 min read