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

Emotet

Trickbot

Botnet

loading..
loading..
loading..

Emotet reincarnated through Trickbot's infrastructure

Emotet botnet has returned and is rebuilding its infrastructure though Trickbot after ten months when law enforcement shut down their C&C servers...

17-Nov-2021
4 min read

No content available.

Related Articles

loading..

Vulnerability

Cursor and Windsurf IDEs harbor 94 unpatched Chromium vulnerabilities, exposing ...

A critical systemic vulnerability has been identified in the Cursor and Windsurf integrated development environments (IDEs). The core issue is not a novel, "zero-day" flaw but a **proliferation of known, patchable vulnerabilities** stemming from the use of a severely outdated software foundation. This technical debt creates a large, exploitable attack surface, effectively turning these modern AI-powered tools into high-risk assets within a development ecosystem. #### **Inheritance of Risk** The narrative is not one of a single flaw, but of a **cascade of architectural decisions** leading to a compromised security posture. * **Primary Cause:** Dependency on an Outdated Electron Framework. * **Technical Context:** Both Cursor and Windsurf are forks of Visual Studio Code (VS Code). VS Code itself is built on the Electron framework, which bundles the Chromium rendering engine and the V8 JavaScript engine to provide a desktop application using web technologies. * **The Vulnerability:** The forked versions of these IDEs are locked to an Electron version that is **six major releases behind** the current stable branch. Consequently, they package a version of Chromium and V8 that is equally outdated. * **Mechanism of Compromise:** Proliferation of n-day Vulnerabilities. * **Definition:** An "n-day vulnerability" is a flaw for which a patch already exists but has not been applied. The IDEs in question contain **at least 94 documented CVEs** that have been publicly disclosed and patched in upstream Chromium and by extension, in the official VS Code. * **Illustrative Example:** **CVE-2025-7656** is a high-severity integer overflow vulnerability in the V8 JavaScript engine. In the context of these IDEs, this is not a theoretical threat. Security researchers have successfully weaponized this CVE to create a proof-of-concept exploit that crashes the IDE (Denial-of-Service) and demonstrated the feasibility of escalating it to **remote code execution (RCE)**. #### **Attack Vectors** The risk is amplified because the attack surface is integrated directly into the developer's workflow. Potential exploitation vectors include: | Attack Vector | Technical Execution | Impact | | :--- | :--- | :--- | | **Malicious Link Preview** | A developer views a project's `README.md` within the IDE, which fetches and renders a remote image or contains a malicious link that is previewed using the outdated Chromium engine. | Arbitrary Code Execution | | **Compromised Extension** | An installed IDE extension, either malicious by design or hijacked, executes a payload within the IDE's Node.js context via the vulnerable V8 engine. | System Compromise | | **Phishing Campaign** | A targeted developer receives a seemingly legitimate link (e.g., to a code review or issue tracker) and clicks it within the IDE's internal browser. | Credential Theft / RCE | #### **Technical Impact Assessment** * **Confidentiality:** Breached if an attacker can execute code to read sensitive files, such as SSH keys, API tokens, or proprietary source code, from the developer's machine. * **Integrity:** Compromised as an attacker could subtly alter source code, dependencies, or build scripts to introduce persistent backdoors. * **Availability:** Directly impacted via Denial-of-Service attacks that crash the IDE, halting development work. #### **Mitigation Strategy** Given the vendors' current stance (Cursor deeming the report "out of scope," Windsurf not responding), the responsibility for mitigation falls on the end-user and the broader development organization. 1. **Immediate Action (Risk Acceptance & Awareness):** * Formally acknowledge that using these IDEs introduces measurable and significant risk. * Ensure development and security teams are fully briefed on the specific threats. 2. **Short-term Mitigation (Operational Controls):** * **Network Segmentation:** Restrict the IDEs from running in high-privilege network environments. * **Principle of Least Privilege:** Run the IDE with user-level, not administrator-level, permissions to limit the impact of a potential code execution. * **Vigilance:** Prohibit the use of the IDE's internal browser for general web navigation and rigorously audit installed extensions. 3. **Long-term Strategy (Archructural Shift):** * **Vendor Pressure:** The only complete solution is for the IDE vendors to rebase their forks onto a modern, patched version of Electron. This should be a primary point of feedback from the user community. * **Alternative Evaluation:** Consider transitioning development projects to the **official, upstream Visual Studio Code**, which maintains a regular patching cadence and is not affected by these specific vulnerabilities. The security posture of Cursor and Windsurf IDEs is currently untenable due to a foundational reliance on deprecated components. The presence of 94+ n-day vulnerabilities represents a known and patchable risk that has been left unaddressed. While the AI features of these tools offer forward-looking capabilities, their underlying runtime architecture is dangerously antiquated. A strategic shift towards maintained and secure foundational software is not just recommended but essential for operational security.

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

Exploit

Ghost in the machine! Operation Zero Disco hijacks Cisco switches via a critical...

In one of the most significant cybersecurity disclosures of the year, Trend Micro has detailed **"Operation Zero Disco,"** a highly sophisticated attack campaign leveraging a critical vulnerability in Cisco switches. The threat actors use a flaw in the Simple Network Management Protocol (SNMP) to install a stealthy Linux rootkit, granting them permanent, hidden control over the network infrastructure. This represents a fundamental shift in attacker methodology, moving from servers and workstations to the very backbone of the network itself. ## **CVE-2025-20352 Explained** The entire attack chain begins with a single point of failure: **CVE-2025-20352**. This is a critical-rated vulnerability (CVSS score likely 9.8+) within the SNMP subsystem of specific Cisco IOS XE and IOS Software. SNMP, or Simple Network Management Protocol, is a ubiquitous service used for monitoring and managing network devices. The flaw allows an unauthenticated, remote attacker to execute arbitrary code with the highest level of privileges (root) by sending a specially crafted SNMP packet to a vulnerable device. The most alarming aspect is that the exploitation requires no user interaction and leaves no immediate forensic trace, making the initial breach virtually silent. ### **Primary Targets in the Crosshairs** The campaign has shown a deliberate focus on essential Cisco switching hardware, including: * Cisco Catalyst 9400 and 9300 Series Switches * Legacy Cisco Catalyst 3750 Series Switches These devices are not obscure; they are the foundational plumbing of enterprise networks worldwide, handling data for corporations, governments, and critical infrastructure. The attackers are strategically targeting older, unpatched, or internet-facing instances of this equipment. ## **The Anatomy of an Advanced Attack** Operation Zero Disco is not a simple smash-and-grab; it is a methodical, multi-stage operation designed for maximum stealth and persistence. ### **Phase 1: Initial Compromise and Exploitation** The attack initiates with broad scanning to identify vulnerable devices. Once a target is located, the attacker deploys the exploit for CVE-2025-20352. This malicious SNMP packet triggers the vulnerability, allowing the attacker to break out of the protocol's intended constraints and execute their own commands on the underlying operating system with root-level authority. ### **Phase 2: Deployment of the "Zero Disco" Rootkit** With a foothold established, the attacker installs their namesake payload: a custom Linux rootkit. This is where the operation's true sophistication is revealed. Unlike traditional malware that writes files to a disk, this rootkit is largely fileless. It operates by injecting malicious code directly into the memory of the key IOSd process—the core software that runs the switch's operating system. **Key capabilities of the rootkit include:** * **A Universal Backdoor Password:** It sets a secret, hardcoded password that provides backdoor access to the switch's console, completely bypassing all legitimately configured user credentials. * **Memory Residency:** By living primarily in memory, it avoids leaving traces on the filesystem, rendering conventional file-based antivirus and integrity checks useless. * **Persistence Mechanism:** The rootkit is engineered to survive device reboots, ensuring the compromise is long-lasting. ### **Phase 3: Command and Control via the UDP Backdoor** To maintain remote control, the rootkit establishes a covert communication channel. A separate UDP-based backdoor component listens for encrypted commands from the attacker's command-and-control (C2) server. **This backdoor controller grants the attacker god-like control over the device, enabling them to:** * **Disable all system logging,** effectively making the switch "forget" all malicious activity. * **Bypass authentication checks** to grant access to anyone using the secret handshake. * **Hide malicious configurations** from the `show running-config` command. Specific user accounts, EEM (Embedded Event Manager) applets, and Access Control Lists (ACLs) can be active on the device while remaining completely invisible to network administrators. * **Execute "timestomping,"** manipulating file timestamps to avoid detection during forensic audits. ### **Phase 4: Lateral Movement and Espionage** With full, invisible control over a network switch, the attacker gains a strategic vantage point. They can now: * **Bridge separate VLANs,** dismantling critical network segmentation designed to contain breaches. * **Conduct ARP spoofing** to impersonate trusted IP addresses, allowing them to bypass internal firewalls and intercept sensitive data in transit. * **Move laterally** throughout the network to target high-value servers and workstations, all from a trusted network position. ## **Mitigation and Defense: A Strategic Response** Given the severity and stealth of this threat, a layered and immediate defensive strategy is non-negotiable. ### **Immediate Action: Patching and Workarounds** The single most effective action is to apply the official patch. Organizations must immediately upgrade their Cisco switches to a fixed software release. The **Cisco Software Checker** should be used to identify the correct version for specific hardware models. If patching cannot be performed instantly, a temporary mitigation is available. Administrators can disable the specific vulnerable Object ID (OID) using the SNMP view configuration: `snmp-server view NO-DISCO iso excluded` `snmp-server community public view NO-DISCO RO` **Important Note:** This is a temporary workaround, not a permanent solution. Patching remains critical. ### **Strategic Security Hardening** Beyond immediate mitigation, organizations must reinforce their security posture: * **Eliminate Default SNMP Communities:** Immediately change or disable well-known community strings like "public" and "private." * **Restrict SNMP Access:** Use Access Control Lists (ACLs) to ensure the SNMP service is only accessible from a dedicated, trusted management station and is blocked from general network access. * **Conduct Proactive Threat Hunting:** There is no automated tool to reliably detect a compromise. Security teams must hunt for anomalies, such as unexplained device reboots, unexpected EEM scripts, or unusual SNMP traffic patterns. * **Engage Cisco TAC for Forensic Analysis:** If a compromise is suspected, the only reliable course of action is to contact Cisco's Technical Assistance Center for a low-level forensic investigation. It demonstrates that advanced threat actors are now systematically targeting the network infrastructure itself with tools designed to be invisible to conventional security controls. The combination of a potent, remotely exploitable flaw and an advanced, persistent rootkit creates a perfect storm for enterprise security. This campaign serves as a stark reminder that network devices are not just plumbing—they are critical security endpoints that require the same level of scrutiny, patching, and monitoring as any server or desktop.

loading..   16-Oct-2025
loading..   6 min read
loading..

Exploit

TigerJack's malicious VS Code extensions, like C++ Playground & HTTP Format, ste...

A threat actor known as **TigerJack** has been systematically infiltrating developer marketplaces with malicious Visual Studio Code (VS Code) extensions, creating a sophisticated attack infrastructure that steals source code, hijacks system resources for cryptocurrency mining, and establishes remote backdoors for complete system control. This ongoing campaign highlights a critical and escalating threat to the software supply chain, leveraging the trust developers place in popular IDE marketplaces. ### Malicious Extension Arsenal TigerJack operates a coordinated multi-account campaign across at least three publisher identities (`ab-498`, `498`, and `498-00`), deploying at least 11 malicious extensions. The most successful ones, "C++ Playground" and "HTTP Format," infected over **17,000 developers** before being removed from the Microsoft Marketplace, though they remain available on the open-source **OpenVSX registry** (used by Cursor, Windsurf, and other VS Code-compatible IDEs). The attack employs a "Trojan Horse" strategy: the extensions function as advertised to avoid suspicion while malicious code runs invisibly in the background. | Extension Name | Primary Malicious Function | Key Technique | | :--- | :--- | :--- | | **C++ Playground** | Source code theft | Exfiltrates C++ code via document change listener | | **HTTP Format** | Cryptocurrency mining | Runs CoinIMP miner with hardcoded credentials | | **cppplayground, httpformat, pythonformat** | Remote Code Execution (Backdoor) | Fetches & executes remote JavaScript payloads every 20 minutes | ### A Multi-Faceted Attack on Developers 1. **Real-Time Source Code Theft**: The "C++ Playground" extension uses an `onDidChangeTextDocument` listener that activates 500 milliseconds after a keystroke, capturing and exfiltrating complete C++ source files in near-real-time to multiple remote servers. The stolen code, often containing proprietary algorithms and intellectual property, is packaged into JSON payloads and sent to endpoints like `https://ab498.pythonanywhere.com/test4`. 2. **Cryptojacking and System Hijacking**: "HTTP Format" secretly runs a **CoinIMP miner**, using hardcoded API credentials to monopolize CPU resources. This causes noticeable performance issues like constant fan noise and system lag, which developers often mistake for hardware or software problems. The threat actor can monitor mining progress and withdraw mined cryptocurrency directly. 3. **Persistent Remote Backdoor**: The most dangerous extensions establish a **persistent backdoor** that polls a remote server (`https://ab498.pythonanywhere.com/static/in4.js`) every 20 minutes for new commands. Using JavaScript's `eval()` function on the fetched code, TigerJack can dynamically push any malicious payload without updating the extension. This allows for: * Stealing credentials and API keys * Deploying ransomware * Using developer machines as entry points into corporate networks * Injecting backdoors into software projects ### A Persistent & Evolving Threat TigerJack demonstrates high persistence. As recently as September 2025, the actor launched a coordinated republication campaign, repackaging the same malicious code under the new "498-00" publisher account. This occurred even as the investigation was ongoing, proving the operation's sophistication. This campaign is part of a broader trend of attacks targeting developers through their tools. Recent incidents include a malicious dependency in the **"Material Theme"** that impacted nearly 4 million users, a cryptojacking campaign impersonating popular tools like **"Prettier"** and **"Discord Rich Presence"**, and a supply chain attack on the **"Ethcode"** extension via a malicious pull request. ### How to Protect Your Development Environment For individual developers and organizations, vigilance and proactive security measures are critical: * **Vet Extensions and Publishers**: Only install extensions from verified, well-known publishers. Scrutinize the publisher's name, history, and other extensions. * **Practice Least Privilege**: Grant extensions only the minimum permissions they require. Regularly audit installed extensions and revoke access for those no longer in use. * **Monitor System Performance**: Unexplained high CPU usage or system slowdown could indicate a hidden cryptominer. * **Use Security Tools**: Consider community-built security scanners like **ExtensionTotal** that can detect malicious or risky extensions before they cause harm. * **Maintain Visibility**: Organizations should have visibility into third-party vendors and tools integrated into their development environment, as limited visibility is a major risk factor. The TigerJack campaign serves as a stark reminder that the very tools intended to boost productivity can become potent weapons in the hands of threat actors. As the attack vector evolves, a shift from blind trust to verified security becomes not just prudent, but essential for safeguarding intellectual property and infrastructure.

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