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

Howard University

Education

Ransomware

loading..
loading..
loading..

Howard University Abruptly Dropped Classes & Shut Down Wi-Fi Services Following Ransomware Attack

Howard University was reportedly prompted to cancel its online classes and forcefully shut down its wi-fi services following an alarming ransomware attack...

08-Sep-2021
2 min read

No content available.

Related Articles

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

WhatsApp

Trustwave SpiderLabs exposes a sophisticated Android banking Trojan, "SpyNote," ...

Cyber threats exploit human trust. Trustwave SpiderLabs has uncovered a new, highly effective distribution campaign for the **SpyNote Android banking Trojan**. Masquerading as a critical "WhatsApp Update," this malware leverages the platform's immense credibility to bypass user skepticism and deploy a full-featured spying and financial-theft tool directly on victim devices. The campaign, detailed in a recent threat intelligence report, demonstrates a shift from less-personalized distribution methods to highly targeted social engineering, marking a significant evolution in the mobile threat landscape. #### **A Multi-Stage Social Engineering Assault** The attack begins not with a technical exploit, but with a persuasive lie. Victims receive a message, typically via SMS or another platform, urging them to update WhatsApp by clicking a provided link. This sense of urgency and the use of a trusted brand name is the critical first step in bypassing initial defenses. 1. **The Lure:** The victim is directed to a phishing page that convincingly mimics the official WhatsApp website, complete with branding and a prominent "Update" button. 2. **The Payload:** Clicking the button downloads a malicious APK file (`api[.]whatsapp[.]com/update_whatsapp.apk`). This file is the SpyNote banking Trojan, digitally signed with a seemingly legitimate certificate to evade basic checks. The user must enable "Install from Unknown Sources," a step the social engineering context makes them more likely to accept. 3. **The Permissions Grab:** Once installed, the app, disguised with a generic "Settings" icon and name, requests extensive Android permissions. Crucially, it abuses the Accessibility Service—a powerful feature intended to aid users with disabilities—to grant itself additional permissions without user interaction, effectively neutering Android's standard security prompts. #### **Beyond Simple Banking Theft** SpyNote (detected by SpiderLabs as `Android.SpyNote`) is not a simple information stealer; it's a modular RAT (Remote Access Trojan) with a comprehensive suite of spying capabilities designed for persistent control and data exfiltration. Key malicious functionalities include: * **Overlay Attacks:** The Trojan dynamically injects fake login screens over legitimate banking and social media applications, capturing credentials in real-time as the user enters them. * **SMS Interception & Theft:** It can read, send, and block SMS messages. This is critical for intercepting one-time passwords (OTPs) and two-factor authentication (2FA) codes used by banks. * **Call Redirection & Recording:** The malware can redirect incoming calls and record both sides of a conversation, providing attackers with a direct audio intelligence feed. * **Keylogging:** By abusing the Accessibility Service, it can log every keystroke made on the infected device, capturing usernames, passwords, and private messages. * **Remote Control (RAT):** Attackers can remotely trigger these functions, access the device's file system, and even use the camera and microphone, turning the smartphone into a full-fledged surveillance device. * **Payload Update Capability:** The malware can communicate with its Command and Control (C2) server to download and execute additional malicious payloads, ensuring its functionality can evolve post-infection. #### **Why This Campaign is So Effective** This campaign's success lies in its psychological precision. By hijacking the WhatsApp brand—a service used by billions for personal and professional communication—attackers create a powerful cognitive bias. The fear of missing out on critical updates or functionality overrides the natural caution associated with installing unknown apps. Furthermore, the use of a digitally signed APK and the abuse of legitimate Android features like the Accessibility Service represent a "living-off-the-land" technique for mobile malware, making it harder for traditional security solutions to distinguish malicious from legitimate behavior. #### **Mitigation & Defense Recommendations** For enterprises and individuals, a proactive, defense-in-depth strategy is essential. **For End-Users:** * **Never install apps from unofficial sources.** Only use the Google Play Store or official enterprise app stores. * **Be inherently skeptical of unsolicited update links,** especially those received via SMS or email. Navigate to the official app store directly to check for updates. * **Scrutinize app permissions critically.** If an app, especially one claiming to be a simple utility, requests Accessibility Service permissions or SMS access, it is a major red flag. * **Keep "Install Unknown Apps" disabled for all browsers and messaging apps.** **For Enterprises (via EMM/MDM):** * Enforce policies that block the installation of applications from unknown sources on all corporate-managed devices. * Implement application allow-listing to restrict which apps can run on enterprise devices. * Deploy a modern Mobile Threat Defense (MTD) solution capable of detecting malicious behavior, such as the abuse of Accessibility Services and the presence of overlay attacks. * Conduct ongoing user awareness training focused on mobile social engineering tactics. The SpyNote campaign is a potent indicator that mobile banking Trojans are becoming more sophisticated, not just in their code, but in their delivery. In an era where the smartphone is a digital vault, vigilance is the first and most important line of defense.

loading..   19-Nov-2025
loading..   4 min read