Researchers Uncover 'DEEP#DOOR', a Stealthy Python Backdoor Stealing Credentials

New Stealthy Python Backdoor 'DEEP#DOOR' Steals Credentials Using Legitimate Tunneling Service

HIGH
April 30, 2026
5m read
MalwareThreat IntelligenceCyberattack

Related Entities

Organizations

Products & Tech

PythonWindows

Other

DEEP#DOOR

Full Report

Executive Summary

Researchers at Securonix have detailed a new and stealthy Python-based backdoor framework they have named DEEP#DOOR. This malware is a full-featured Remote Access Trojan (RAT) designed to gain persistent access to Windows systems and exfiltrate sensitive data. The attack chain begins with an obfuscated batch script that contains the core Python implant, a technique that minimizes its network footprint. Upon execution, DEEP#DOOR disables Windows security features and establishes persistence using at least four different methods to ensure its survival. A key feature of the malware is its use of bore.pub, a legitimate tunneling service, for its command and control (C2) communications. This allows it to bypass network security controls and stealthily exfiltrate stolen browser and cloud credentials.


Threat Overview

DEEP#DOOR is a sophisticated RAT that demonstrates a trend towards fileless and script-based malware that abuses legitimate system tools and services to evade detection. The initial access vector is believed to be phishing or a similar social engineering tactic to trick a user into running the initial dropper.

The malware's primary objectives are to:

  1. Establish a persistent foothold on the victim's machine.
  2. Disable security software.
  3. Steal credentials, particularly from web browsers and cloud service applications.
  4. Provide the attacker with remote access for further post-exploitation activities.

Technical Analysis

The attack chain unfolds in several stages:

  1. Initial Dropper (install_obf.bat): The attack starts with an obfuscated batch script. This script contains the embedded and encoded Python payload, avoiding the need to download a second stage from the internet.
  2. Defense Evasion: The batch script first attempts to disable Windows security controls, likely including Windows Defender and other monitoring services.
  3. Payload Extraction: The script then decodes and writes the embedded Python implant (svc.py) to the disk and executes it.
  4. Persistence (T1547.001, T1543.003): DEEP#DOOR is highly resilient, establishing persistence through multiple redundant methods simultaneously:
    • Creating scripts in the user's Startup folder.
    • Adding entries to the Registry Run keys.
    • Creating a Scheduled Task.
    • Using Windows Management Instrumentation (WMI) event subscriptions.
  5. Command and Control (T1572): The Python implant communicates with bore.pub, a legitimate, Rust-based tunneling service. It uses this service to create a reverse tunnel from the victim's machine to the attacker's C2 server. This makes the C2 traffic appear as legitimate outbound web traffic to a known service, helping it bypass firewalls and network monitoring tools.
  6. Credential Theft (T1555): Once active, the RAT can receive commands to execute various modules, including those designed to steal credentials from browsers, email clients, and cloud applications.

Impact Assessment

A successful DEEP#DOOR infection can have severe consequences:

  • Complete System Compromise: As a RAT, it gives the attacker full control over the infected machine, allowing them to install other malware (like ransomware), spy on the user, and use the machine as a pivot point for lateral movement.
  • Widespread Credential Theft: The theft of saved browser and cloud credentials can lead to the compromise of numerous other online accounts, both personal and corporate.
  • Data Exfiltration: The attacker can use their remote access to search for and exfiltrate any sensitive files or data on the compromised system or accessible network shares.
  • Difficult Detection: The use of legitimate services (bore.pub), script-based execution (Python, Batch), and multiple persistence mechanisms makes the malware difficult to detect and fully eradicate.

IOCs — Directly from Articles

Type
File Name
Value
install_obf.bat
Description
The initial obfuscated batch script dropper.
Type
File Name
Value
svc.py
Description
The name of the core Python implant payload.
Type
Domain
Value
bore.pub
Description
The legitimate tunneling service abused for C2 communications.

Detection & Response

  1. Monitor for Tunneling Services: Monitor network traffic for connections to known tunneling services like bore.pub, ngrok.io, or localtunnel.me. While these have legitimate uses, an unexpected connection from a user workstation or server is highly suspicious and should be investigated.
  2. Script-Block Logging: Enable PowerShell and other script-block logging and forward the logs to a SIEM. This can capture the content of malicious scripts like the initial batch file, even if they are obfuscated.
  3. Persistence Mechanism Auditing (D3-SFA): Regularly audit the common persistence locations used by DEEP#DOOR (Startup folders, Run keys, Scheduled Tasks, WMI subscriptions) for any unauthorized or suspicious entries.

Mitigation

  1. Application Control (D3-EAL): Use application control solutions like AppLocker to restrict the execution of batch scripts and unsigned Python scripts in user-writable directories. This can prevent the initial dropper from running.
  2. Endpoint Protection: Deploy a modern EDR solution capable of detecting and blocking suspicious script execution and fileless malware techniques.
  3. Egress Traffic Filtering (D3-OTF): If your organization does not have a business need for tunneling services, explicitly block the domains of services like bore.pub at your web proxy or firewall.
  4. User Training: Educate users about the dangers of running unsolicited scripts or attachments from emails.

Timeline of Events

1
April 30, 2026
This article was published

MITRE ATT&CK Mitigations

Using application control policies to restrict the execution of scripting languages like Python and Batch from untrusted locations can prevent the malware from running.

Explicitly blocking outbound connections to known tunneling services like bore.pub at the network perimeter can disrupt the malware's C2 channel.

Audit

M1047enterprise

Regularly auditing common persistence locations (Registry, Startup folders, WMI) can help detect the presence of DEEP#DOOR and similar threats.

D3FEND Defensive Countermeasures

A key feature of DEEP#DOOR is its abuse of the legitimate service 'bore.pub' for C2 tunneling. Organizations should implement an egress filtering policy that blocks access to known tunneling services unless there is an explicit business justification. Create a category of 'Proxy and Tunneling Services' in your web proxy or firewall and set it to block. This list should include bore.pub, ngrok.io, and other similar services. This simple network control directly severs the malware's communication channel, rendering it unable to receive commands or exfiltrate data.

To prevent the initial execution of the DEEP#DOOR dropper, organizations should implement application allowlisting using tools like Windows AppLocker. Configure a policy that prevents the execution of batch files (.bat) and Python scripts (.py) from user-writable directories such as C:\Users\ and %APPDATA%. By only allowing scripts to run from protected, administrator-controlled directories (e.g., C:\Program Files\), you can effectively block this and many other script-based threats that rely on a user downloading and running a file in their local profile.

Sources & References

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

DEEP#DOORPythonBackdoorRATSecuronixWMI PersistenceTunneling

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.