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.
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:
The attack chain unfolds in several stages:
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.svc.py) to the disk and executes it.T1547.001, T1543.003): DEEP#DOOR is highly resilient, establishing persistence through multiple redundant methods simultaneously:Registry Run keys.Scheduled Task.Windows Management Instrumentation (WMI) event subscriptions.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.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.A successful DEEP#DOOR infection can have severe consequences:
bore.pub), script-based execution (Python, Batch), and multiple persistence mechanisms makes the malware difficult to detect and fully eradicate.install_obf.batsvc.pybore.pubbore.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.bore.pub at your web proxy or firewall.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.
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.

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.
Help others stay informed about cybersecurity threats
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.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
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 detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.