Switch branches/tags
Nothing to show
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
214 lines (133 sloc) 7.64 KB

Honey Ports



A Python based cross-platform HoneyPort solution, created by Paul Asadoorian.

Install Location



Change to the Honeyports directory and execute the latest version of the script:

~$ cd /opt/honeyports/cross-platform/honeyports

/opt/honeyports/cross-platform/honeyports$ python2 ./

    Usage: -p port 
    Please specify a valid port range (1-65535) using the -p option

Video Walkthrough

Part 1

Your browser does not support html5 video.

Part 2

Your browser does not support html5 video.

Example 1: Monitoring A Port With HoneyPorts

From the honeyports directory, run:

/opt/honeyports/cross-platform/honeyports$ sudo python2 ./ -p 3389

    Listening on IP:  :  3389

We can confirm that the listening is taking place with lsof:

/opt/honeyports/cross-platform/honeyports$ sudo lsof -i -P | grep python

    python   26560     root    3r  IPv4 493595      0t0  TCP *:3389 (LISTEN)

Looks like we're good.

Any connection attempts to that port will result in an instant ban for the IP address in question. Let's simulate this next.

Example 2: Blacklisting In Action

If Honeyports is not listening on 3389 please follow the instructions in [Example 1: Monitoring A Port With HoneyPorts].

Once you have Honeyports online and a backup Windows machine to connect to Honeyports from, let's proceed.

First we need to get the IP address of the ADHD instance.

~$ ifconfig

    eth0      Link encap:Ethernet  HWaddr 08:00:27:65:3c:64  
              inet addr:  Bcast:  Mask:
              inet6 addr: fe80::a00:27ff:fe65:3c64/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:46622 errors:0 dropped:0 overruns:0 frame:0
              TX packets:8298 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:14057203 (14.0 MB)  TX bytes:2659309 (2.6 MB)

    lo        Link encap:Local Loopback  
              inet addr:  Mask:
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:94405 errors:0 dropped:0 overruns:0 frame:0
               TX packets:94405 errors:0 dropped:0 overruns:0 carrier:0
                 collisions:0 txqueuelen:0 
              RX bytes:37127292 (37.1 MB)  TX bytes:37127292 (37.1 MB)

We can see from the ifconfig output that my ADHD instance has an IP of

I will connect to that IP on port 3389 from a box on the same network segment in order to test the functionality of Honeyports.

I will be using RDP to make the connection.

To open Remote Desktop hit Windows Key + R and input mstsc.exe before hitting OK.

Next simply tell RDP to connect to your machine's IP address.

We get an almost immediate error, this is a great sign that Honeyports is doing its job.

Any subsequent connection attempts are met with failure.

And we can confirm back inside our ADHD instance that the IP was blocked.

~$ sudo iptables -L

    Chain INPUT (policy ACCEPT)
    target     prot opt source               destination         
    REJECT     all  --        anywhere             reject-with icmp-port-unreachable

    Chain FORWARD (policy ACCEPT)
    target     prot opt source               destination         

    Chain OUTPUT (policy ACCEPT)
    target     prot opt source               destination         

    Chain ARTILLERY (0 references)
    target     prot opt source               destination    

You can clearly see the REJECT policy for (The address I was connecting from).

To remove this rule we can either:

~$ sudo iptables -D INPUT -s -j REJECT

Or Flush all the rules:

~$ sudo iptables -F

Example 3: Spoofing TCP Connect for Denial Of Service

Honeyports are designed to only properly respond to and block full TCP connects. This is done to make it difficult for an attacker to spoof being someone else and trick the Honeyport into blocking the spoofed address. TCP connections are difficult to spoof if the communicating hosts properly implement secure (hard to guess) sequence numbers. Of course, if the attacker can "become" the host they wish to spoof, there isn't much you can do to stop them.

This example will demonstrate how to spoof a TCP connect as someone else, for the purposes of helping you learn to recognize the limitations of Honeyports.

If you can convince the host running Honeyports that you are the target machine, you can send packets as the target. We will accomplish this through a MITM attack using ARP Spoofing.

Let's assume we have two different machines, they may be either physical or virtual. One must be your ADHD machine running Honeyports, the other for this example will be a Kali box. They must both be on the same subnet.

Note: Newer Linux operating systems like ADHD often have builtin protection against this attack. This protection mechanism is found in /proc/sys/net/ipv4/conf/all/arp_accept. A 1 in this file means that ADHD is configured to accept unsolicited ARP responses. You can set this value by running the following command as root echo 1 > /proc/sys/net/ipv4/conf/all/arp_accept

If our ADHD machine (running the Honeyports) is at and we want to spoof

Let's start by performing our MITM attack.

~# arpspoof -i eth0 -t 2>/dev/null &

~# arpspoof -i eth0 -t 2>/dev/null &

If you want to confirm that the MITM attack is working first find the MAC address of the Kali box.

~# ifconfig -a | head -n 1 | awk '{print $5}'


Then on the ADHD machine run this command to determine the current mapping of IPs to MACs.

~# arp -a

Look to see if the IP you are attempting to spoof is mapped to the MAC address from the previous step.

Once we have properly performed our arpspoof we will move on to assigning a temporary IP to the Kali machine.

This will convince the Kali machine to send packets as the spoofed host.

~# ifconfig eth0:0 netmask up

The last step is to connect from the Kali box to the ADHD machine on a Honeyport, as

For this example, lets say that port 3389 is a Honeyport as we used before in [Example 1: Monitoring A Port With HoneyPorts].

~# nc 3389 -s

It's that easy, if you list the firewall rules of the ADHD machine you should find a rule rejecting connections from

Mitigation of this vulnerability can be accomplished with either MITM protections, or careful monitoring of the created firewall rules.