Understanding the Chrysalis Backdoor Campaign
Rapid7’s Threat Research uncovers the infrastructure, tooling, and techniques behind the Chrysalis campaign.
A backdoor attack explained
A backdoor attack occurs when a threat actor gains unauthorized access to a system by bypassing standard authentication and security controls. Instead of breaking in repeatedly, the attacker creates or exploits a hidden entry point—known as a backdoor—to maintain persistent access.
Backdoors can be introduced intentionally by attackers, accidentally through insecure development practices, or embedded within compromised software updates. Once established, a backdoor allows attackers to operate quietly inside an environment for extended periods.
Backdoor attacks are often associated with:
- Command-and-control (C2) communication
- Persistent remote access
- Credential abuse
- Lateral movement across networks
How backdoor attacks work
A backdoor attack typically follows a lifecycle: initial access, installation, persistence, and exploitation.
Initial access
Attackers first need a foothold. Common entry methods include:
- Phishing emails that deliver malware
- Exploiting unpatched vulnerabilities
- Compromised software supply chains
- Stolen credentials
- Exposed remote access services
In some cases, attackers insert malicious code into legitimate software before it reaches users, as seen in high-profile supply chain compromises.
Installation
Once inside, attackers install or activate a backdoor mechanism. This may involve:
- Dropping a malware payload.
- Creating a hidden administrator account.
- Installing a web shell on a server.
- Embedding hardcoded credentials.
- Modifying authentication logic in an application.
The goal is to ensure continued access even if the original vulnerability is fixed.
Persistence and control
After installation, attackers establish persistence to survive system reboots and security updates. Techniques include:
- Scheduled tasks or cron jobs (a scheduled task in Unix-like operating systems (Linux, macOS) that automates repetitive background processes at specific times, dates, or intervals).
- Registry modifications.
- Startup folder changes.
- Encrypted C2 communications.
At this stage, the attacker can issue commands remotely, exfiltrate data, deploy ransomware, or pivot to other systems.
Types of backdoor attacks
Backdoor attacks vary depending on how and where the hidden access is created.
Malware-based backdoors
Malware-based backdoors are malicious programs designed specifically to open remote access channels. These often connect to external command-and-control servers.
Web shell backdoors
Web shell backdoors are malicious scripts uploaded to web servers that allow attackers to execute commands through a browser. They are common after web application compromises.
Supply chainbackdoors
Supply chain backdoors are inserted into legitimate software updates or third-party libraries. Organizations that install the compromised software unknowingly deploy the backdoor internally.
Hardcoded or developer backdoors
Hardcoded backdoors are built into applications for testing or maintenance but left exposed in production environments. If discovered, attackers can exploit them.
Hardware and firmware backdoors
Hardware or firmware backdoors are hidden access mechanisms embedded in physical components or low-level system code, making them harder to detect and remove.
AI and model backdoors
AI backdoors involve manipulating training data or model behavior so that specific triggers cause malicious outputs. These are an emerging concern in machine learning security.
Backdoor vs. trojan vs. remote access tool
Backdoors are often confused with other types of malicious software.
- Backdoor: A hidden method of bypassing authentication to maintain persistent access.
- Trojan: Malware disguised as legitimate software that may install a backdoor once executed.
- Remote access tool (RAT): Software that allows remote control of a system; legitimate tools can be abused, while malicious RATs often function as backdoors.
A trojan may deliver a backdoor, and a malicious RAT often operates as a backdoor—but the terms are not interchangeable.
Real-world examples of backdoor attacks
Backdoor attacks appear in a range of incidents, including:
- Compromised software packages that distribute hidden malicious code
- Web server breaches where attackers install web shells
- Insider threats involving unauthorized administrative accounts
- Targeted attacks that insert backdoors into development pipelines
In supply chain cases, attackers may compromise a trusted software provider, embedding a backdoor that propagates to thousands of downstream users.
Risks of backdoor attacks
Backdoor attacks pose significant risks because they enable long-term, stealthy access.
Potential impacts include:
- Data exfiltration of sensitive information.
- Ransomware deployment.
- Intellectual property theft.
- Credential harvesting.
- Regulatory penalties for data breaches.
- Reputational damage.
Because backdoors are designed to evade detection, organizations may remain unaware of an intrusion for months.
How to detect a backdoor attack
Detecting a backdoor attack requires continuous monitoring and behavioral analysis.
Key detection strategies include:
- Centralized log collection and correlation through a SIEM.
- Endpoint detection and response (EDR) monitoring.
- Network traffic analysis for unusual outbound connections.
- Behavioral analytics to identify authentication anomalies.
- Threat hunting for persistence mechanisms.
Unusual administrative account creation, unexpected outbound traffic, or modified authentication logic can indicate backdoor activity.
How to prevent backdoor attacks
Preventing backdoor attacks requires a layered security approach.
Maintain strong patch management
Unpatched vulnerabilities are a common entry point. Timely updates reduce exploit opportunities.
Implement least privilege and zero trust
Limiting access and continuously verifying identity reduces the impact of credential-based backdoors.
Secure the software supply chain
Code reviews, dependency monitoring, and validation of third-party software updates help prevent supply chain backdoors.
Monitor continuously
Continuous monitoring and threat detection help identify suspicious behavior early, reducing dwell time.
Enforce secure development practices
Removing test credentials, eliminating hardcoded passwords, and validating authentication logic prevent accidental backdoors in production systems.