How hackerhouse-opensource/backdoors works
Project’s Type and Purpose
• The project is a suite of “Backdoors” – a collection of PoC tools that simulate persistence techniques (e.g., kernel mode hooking, command & control implementations) and various methods to maintain access on target systems.
• The tools cover different platforms including Windows, Linux, and OS-X, and they are written in different languages (e.g., GoLang, Python, and even kernel modules packaged as .tgz or .tar.gz).
• The purpose is demonstrative rather than a “live” system – each tool shows off a particular technique (bind shells, hidden files, rootkits, etc.) that might be deployed in real-world situations.
File Structure
• The directory listing shows a flat file structure with multiple archives and source files.
• Files are grouped by type such as compressed archives (.tgz, .tar.gz, .zip) containing more complex modules (e.g., Linux kernel modules like filehider.tgz and magicroot.tgz, OS-X rootkit rubilyn-0.0.1.tar.gz, and Windows-specific tools like SYSTEMservice.tgz and Peony.zip).
• Standalone scripts and source files (e.g., bindshell.go, bindshell.py, cmdbot.py, halloween.py, icmp.py) indicate separate implementations of remote access or command execution.
a. Out Different Functional Areas:
– Remote Shells: Include both the Go and Python bind shell examples. These demonstrate how a remote shell connection is implemented.
– Command & Control (C2) Implementations: Represented by tools like cmdbot.py (IRC C2), TrojanSource.zip (web-based C2 implant), and luna.tgz (AX.25 APRS via satellite). Also, icmp.py shows raw socket command execution.
– Kernel and System-Level Backdoors: Package tools like filehider.tgz (kernel module for hiding files), magicroot.tgz (kernel module for “magic” root backdoor), rubilyn-0.0.1.tar.gz (OS-X rootkit), and SYSTEMservice.tgz (Windows service-based persistent backdoor).
– Auxiliary and Supporting Tools: Include utilities such as StringCrypt.tgz (string encryptor for OS-X tools) and yolo-openssl.tgz (an OpenSSL backdoor extension).
b. Relationships and Interactions:
– Highlight any supporting or dependency relationships (e.g., StringCrypt might be used with rubilyn) even though these relationships are conceptual in a PoC tool repository.
Architectural Patterns and Design Principles
• Even though this is not a monolithic system, the design intent shows modularity – each tool is focused on a specific aspect of persistence or remote access.
• Separation of concerns by grouping tools based on their functional domain (e.g., network communications, kernel manipulation, service persistence).
• That the system design in this repository follows a “collection of independent modules” pattern where each module demonstrates a different technique.
Specific Elements
• A clear label for each module/component (e.g., “Remote Shells: bindshell.go / bindshell.py”).
• Notes or callouts that briefly describe the purpose of each tool if space permits (e.g., “Peony.zip – Windows Defender AV bypass using a Meterpreter harness”).