-
-
Notifications
You must be signed in to change notification settings - Fork 154
How to Use
jm33-ng edited this page Dec 30, 2019
·
9 revisions
mec > help
Command Description
------- -----------
clear (c) Clear screen
reset (x) Terminal reset
init (i) Return to mec root directory
help (?) Display this help info
quit (^C) Quit
attack (e) Start a mass-exploit job
masscan Run masscan to collect target hosts, requires root
info Current mec settings, and proxy status
target Change target list
init Return to mec root directory
baidu Search via m.baidu.com
proxy Start ss-proxy using ./data/ss.json config
google Fetch URLs from Google using custom dork
zoomeye Crawler for ZoomEye
censys Crawler for Censys.io
exploits List all usable exploits
help Display this help info
(others) Treated as shell commands
mec > attack
[?] Do you wish to use proxychains? [y/n] n
[?] Do you wish to use
[a] built-in exploits
[m] or launch your own manually?
[=] Your choice: a
[?] Choose a module from:
ssh_bruteforcer
weblogic
s2_045
witbe
[?] Choose your exploit module: weblogic
[*] Welcome to Weblogic getshell exploit
[?] What's the port of Welogic server?
...
mec has a built-in ss-proxy
that's compiled as a static-linking binary, see https://github.com/shadowsocks/go-shadowsocks2 for details
To use ss-proxy
, you need to find some shadowsocks server from the internet, or deploy your own.
Edit ss.json
:
{
"server": "<server's ip address>",
"server_port": "<int: server port>",
"local_address": "127.0.0.1",
"local_port": "<int: port of local socks5 proxy>",
"password": "password",
"timeout": 300,
"method": "<cipher>",
"fast_open": false,
"workers": 1
}
Now just type proxy
command to start it:
mec > proxy
mec > info
session
-------
[*] Current directory: /home/u/.mec
[*] Root directory: /home/u/.mec
[*] Log file: /home/u/.mec/output/2019_12_26_02_27_48.log
[*] Target: /home/u/.mec/data/ip_list.txt
PROXY
-----
[*] Shadowsocks config: ss://aes-256-cfb:[email protected]:8080
[*] Shadowsocks local port: 1099
[*] Shadowsocks connectivity: DISCONNECTED
info
command tests your shadowsocks connectivity, if okay, you will see [*] Shadowsocks connectivity: OK
mec console uses readline
for basic completion and command history features.
Press TAB
to complete your input, arrow keys to move around
- If you have any issues, please report them to https://github.com/jm33-m0/mec/issues
- Open a pull request when you have fixed any bugs or added any features
- I would appreciate you adding your own adapted exploits to this repo