Phishing Club is designed to work with most Linux distributions and provides automated installation and update functionality for systems using systemd.
We recommend deploying on infrastructure where hardware resources can be scaled to accommodate your actual usage patterns and campaign requirements.
Component | Minimum | Recommended |
---|---|---|
Operating System | Any Linux distribution | Ubuntu 24.04 LTS or newer |
CPU | 1 core (64-bit) | 2+ cores (64-bit) |
RAM | 1 GB | 4 GB or more |
Storage | 500 MB free space | 2 GB or more |
Download the latest version of Phishing Club from the official downloads page.
A valid license key is required to use Phishing Club. Your license key can be found and copied from the user dashboard.
Running the binary with the --install
flag launches an interactive installer that
streamlines the setup process. The installer handles configuration, dependency installation,
creates a dedicated phishingclub
user and group, sets up a systemd service, and
copies the binary to /opt/phishingclub
.
This approach ensures the application runs with an unprivileged user account and automatically starts on system reboots for maximum security and reliability.
For advanced users who prefer manual installation, use the --help
command to view
all available options and configuration parameters.
Transfer the Binary
Transfer the downloaded binary to your target server:
scp ./phishingclub [email protected]:/tmp/
Prepare for Installation
Connect to your server and make the binary executable:
ssh [email protected] cd /tmp chmod +x ./phishingclub
Run the Interactive Installer
Launch the installer to begin the setup process:
/tmp/phishingclub --install
The interactive installer will prompt you to configure the following options:
Configuration | Description | Default Value |
---|---|---|
HTTP Port | The HTTP (unencrypted) port for the phishing server | 80 |
HTTPS Port | The HTTPS (TLS encrypted) port for the phishing server | 443 |
Admin Port | The HTTPS port for the administration interface | Random port |
Admin Host | The hostname for the administration server TLS certificate (e.g., your server IP or domain name) | localhost |
Auto TLS | Enable automatic TLS certificate management via Let's Encrypt When disabled, creates a self-signed certificate | false |
Complete Installation and Note Credentials
After installation completes, the installer will display important server details and login credentials.
Important: Copy these credentials immediately as they are required to set up your administrative account.
Item | Description |
---|---|
Generated Password | Randomly generated administrative password Note: This password changes if the service restarts before setup |
Phishing HTTP Server | URL for the HTTP phishing server endpoint |
Phishing HTTPS Server | URL for the HTTPS phishing server endpoint |
Administration Server | URL for the HTTPS administration interface |
After completing the installation, you must complete the initial setup process before Phishing Club is ready for use.
Note: If the application has been restarted after installation, you'll need to retrieve the temporary password from the system logs.
Initial Login
Access the administration interface and log in using:
admin
Configure Administrator Account
Set up your permanent administrative account with secure credentials:
License Activation
Enter your license key to activate Phishing Club:
Setup Completion
Review your configuration and complete the setup process:
Congratulations! Phishing Club is now successfully installed and ready for use. You can now begin creating your first phishing campaigns.
Phishing Club automatically checks for new versions and will notify you when updates are available.
When a new update is ready, an Update Available
notification appears in the bottom
right corner of the interface.
Click the Update
button and follow the prompts to confirm the update process.
For manual updates, first download the latest binary using the Update
button in the
interface.
If your service was installed using the --install
flag and runs via systemd, you
can perform the update using the --update
flag on the new binary.
For manually configured instances, replace the current binary with the latest version and restart the service manually.
If you installed Phishing Club using the --install
flag, you can perform a
complete uninstallation using the --uninstall
flag.
Warning: The uninstall process removes the user/group, systemd service, and all files including the database. This action cannot be undone.
./phishingclub --uninstall
You will be prompted to type YES
in capital letters to confirm the uninstallation.
--uninstall
flag.The config.json
configuration file, specified with the -config
flag, allows you to customize various aspects of Phishing Club's behavior and operation.
Note: A service restart is required for configuration changes to take effect.
The configuration uses JSON format with the following available properties:
Configuration Key | Default Value | Description |
---|---|---|
acme.email | Empty string | Email address for ACME certificate management Learn more about ACME emails |
administration.tls_host | localhost | Hostname for administration server TLS certificate (e.g., server IP address or domain name) |
administration.tls_cert_path | Empty string | File path to custom TLS certificate |
administration.tls_cert_key | Empty string | File path to custom TLS private key |
phishing.http | 80 | HTTP port for the phishing server |
phishing.https | 443 | HTTPS port for the phishing server |
database.engine | sqlite3 | Database engine type |
database.dsn | file:./db.sqlite3 | Database Data Source Name (connection string) |
config.path | Empty string | File path for stdout logging output |
config.errorPath | Empty string | File path for stderr logging output |
ip_security.admin_allowed | Empty array | Array of IP addresses allowed to access administration server Empty array allows all IPs |
ip_security.trust_proxies | Empty array | Array of trusted proxy IP addresses for forwarding client information Proxy configuration details |
ip_security.trusted_ip_header | Empty string | Specific HTTP header trusted for IP forwarding information |