Stealth Savage Coding

Target / preset LHOST LPORT Format Encoder Iterations Output name (optional) Extra msfvenom args (optional)

Implant language Persistence mode C2 host (LHOST) C2 port (LPORT) Beacon path User-Agent Beacon sleep (seconds) Jitter (%) Handler payload written into the .rc Transport Use HTTPS / WSS where supported Certificate checks Validate the C2 certificate Save kit as (optional)

Save implant + handler.rc + manifest.json

Implant source

msfconsole handler (.rc)

Wrap a legitimate binary with a payload (msfvenom -x <template> -k) so the host program keeps working. Templates are resolved from ~/.hackcode/payloads/templates; the service runs with PrivateTmp, so files under /tmp are not visible to it.

Payload preset Template binary (absolute path, or a filename from the templates dir) LHOST LPORT Output format Encoder Encoder iterations Output name (optional) Keep original behaviour Add -k so the host program still runs after the payload

One-click mode. Choose what you are attacking, switch on Undetectable, and press Build — you get the implant, a matching listener and plain-English instructions. No payload expertise needed.

What are you attacking? Your IP (LHOST) Port (LPORT) Evasion level Save as (optional) Disguise Wrap inside a harmless-looking program when a template is available Undetectable mode — maximum evasion: encoder ×20 + AES-256 stub + NOP sled (slowest build)

Live session mirror. Start a managed multi/handler here and watch everything — connections, sessions and console output — stream live into this pane. Type commands to steer it.

Handler payload Bind address (LHOST) Port (LPORT) AutoRunScript (optional) Session name (optional)

Forge the flagship Apex RAT — or drop in your own template — and choose your own options: capability modules, a kill-date, a working-hours beacon window and custom @@TOKEN@@ variables. Apex is a standard-library-only, cross-platform implant with authenticated encryption, jittered beaconing, cross-platform persistence and self-destruct, and it ships with a matching handler.

Template C2 host C2 port Handler payload Beacon sleep (s) Jitter (s) Beacon path Persistence User-Agent Kill date (unix s, 0=never) Working hours from (0-23) Working hours to (0-23) Use HTTPS (TLS) Use my own template below (replaces the selected implant) Own template (supports @@TOKEN@@ placeholders) Save as (optional)

Capability modules

Custom @@TOKEN@@ variables

Never built a payload before? Just follow the four steps. Pick a target, type your address, choose a style, tick what it should be able to do, then press Forge my implant. You get a ready-to-run kit and a plain-English to-do list.

1Target
2Address
3Style
4Abilities

Step 1 of 4

Build Apex Android - a complete Android RAT project, based on the most trusted open-source Android RAT (AhMyth) and rebuilt stronger: authenticated encryption, Android 6-15 support, build-time capability modules, a kill-date + working-hours window, anti-uninstall + hidden icon, and a one-command build/sign script. You get the full Gradle/Kotlin project, a builder and a matching console.

C2 host C2 port Transport App label (shown on the phone) Package name Beacon sleep (s) Jitter (s) Beacon path User-Agent Kill date (unix s, 0=never) Working hours start (0-23) Working hours end (0-23) Output name

Hide the launcher icon Device-admin (anti-uninstall) Restart after reboot

Capability modules

Email delivery. Build your implant in any tab — try Simple for one click — then send the finished file straight to an inbox. Just type the email address and press Send; the subject and message are already filled in. Set your sending mailbox once in step 3 and it is remembered.

1

Pick the file to send

Payload file (newest first)

2

Who receives it

Send to (email address) Subject Message

3

Your sending mailbox (saved once)

Provider SMTP host SMTP port Username (your email) Password / app password From address (optional) Use STARTTLS (recommended, usually port 587) Public link base URL (for Download link mode)

Delivery method

File is attached to the email (may be blocked by Gmail/O365).

R31 C2 console - forge a self-contained implant, run the authenticated listener and task live sessions from one place. Implants speak the stdlib seal protocol (SHA-256 CTR + HMAC-SHA256) over HTTP(S)/TCP and beacon back here. Everything stays on this machine.

Listener

Bind host Port Beacon path Console token (optional)

Forge implant

Language Transport C2 host (LHOST) C2 port Beacon path Persistence Sleep (s) Jitter (s) Name base User-Agent Kill date (unix s, 0=never) Work window start (0-23) Work window end (0-23)

Capability modules

Include tiny in-memory stager

Live sessions

Verb Argument (cmd / path / seconds)

Hey — I'm Stealth Savage Coding.