Serving false signatures to attack scanners with Portspoof
Flytrap

The Internet is a tough place to live – especially for publicly accessible computers. A small tool called Portspoof makes port scanning a real challenge for attackers.
Seasoned attackers, and even some amateur cyber-vandals, find sport in trying to scan servers and hijack them at the same time (Figure 1). Firewalls and Intrusion Detection/Prevention systems can help, but if a single tool could truly stop all potential attacks, the Internet intrusion industry wouldn't even exist.

A professional intrusion attempt is typically preceded by reconnaissance and scanning. Many attackers simply perform a scan, which is easily automated with tools like Nmap. An attacker who discovers a firewall and similar defensive system can often guess which ports and services are worth attacking. However, a tool called Portspoof [1] intervenes to cause complications and confusion for the attacker. Portspoof answers port requests with a wild mix of signatures and payloads. This confusing and unwanted information slows down any attempted port scan, forcing the attacker to manually evaluate the results in a time-consuming process.
Portspoof was developed in 2012 by Piotr Duszynski, who calls his program a "Service Emulator and Frontend Exploitation Framework." The application is available under the GPLv2 and is implemented in C++.
Portspoof presents various service signatures on some or all available ports, making it very difficult to discover which services are actually running on the computer. The application can simulate more than 8,000 signatures and has the ability to throw a couple of exploits back at the scanning computer.
When launched, Portspoof only listens on one port (port 4444 by default). All other ports, where attackers fall for the trap, are redirected using an iptables rule.
Installation
Portspoof is currently available in version ++1.0. Download the tool as a ZIP archive or via Git (Listing 1).
Listing 1
Getting Portspoof with Git
After unzipping or cloning, change to the directory created in the process, portspoof[-master]
; then install the application in the three normal steps (Listing 1, line 2). By default, Portspoof ends up in /usr/local/
. To define a different target directory, pass the --prefix
parameter into ./configure
, along with your directory choice.
After the install, quickly run portspoof -h
to check whether everything has worked out so far. If everything is working, you can now run Portspoof.
Gluing and Sticking
Before launching Portspoof, you must tell iptables which ports you want to be "sticky" in the future. To let all ports join in with the fun, use the following directive:
# iptables -t nat -A PREROUTING -i eth0 -p tcp -mtcp --dport 1:65535 -j REDIRECT --to-ports 4444
However, if you are running some genuine services on the computer, omit the matching ports using the --dport
option with --match multiport --dports
. For example, the following command forwards all ports except 22 and 80:
# iptables -t nat -A PREROUTING -i eth0 -p tcp -m tcp -m multiport --dports 1:21,23:79,81:65535 -j REDIRECT --to-ports 4444
The iptables multiport feature can handle a maximum of 15 port ranges. If you have a busy server – like the ones used in small businesses that serve everything from DNS, FTP, SSH, mail, web, and file sharing – you might need a small loop to conveniently set up and manage the IP ranges.
An example is provided in set-spoofports.sh
(Listing 2). You need to make the script executable with chmod 755 set-spoofports.sh
to execute it conveniently. Then, you can use iptables -L -t nat
to check afterwards whether the firewall rules are registered.
Listing 2
set-spoofports.sh
Once iptables is forwarding all the ports to the target port, you can launch Portspoof. This small tool offers a useful feature set. For example, you can switch Portspoof to verbose mode with the -v
option and listen in live when a "visitor" drops by. Alternatively, you can start the program as a daemon that performs its work in the background using the with -D
option.
If you call Portspoof without any additional parameters, it works in what is known as open port mode. As the name suggests, open port mode means that Portspoof only shows all forwarded ports as open. That's a nice tick, but you can do much nastier things, too. For example, why not try the following command?
# portspoof -c </path/to>/portspoof.conf -s </path/to>/portspoof_signatures -D
The Service Emulator now responds to requests with heaps of signatures or even exploits, which greatly complicate the attacker's task of evaluating the results (Figure 2). Both portspoof.conf
, as well as portspoof_signatures
, reside by default in /usr/local/etc
. The portspoof_signatures
file contains prepared signatures.

Little Tricks
The portspoof.conf
can be populated with signatures and even exploits that Portspoof then delivers when a remote entity queries a specific port or port range. The specification of the signature file typically suffices; you only need portspoof.conf
to output precisely defined feedback for selected ports.
In portspoof.conf
, you enter (line by line) the port for which the content ("payload") is intended. The payload can be simple ASCII words, but also hexadecimal characters or regular expressions. Even exploits can be returned (caution: see the "Computer Sabotage" box). The default portspoof.conf
is well commented by the Portspoof developer, which makes it easy to add your own messages and niceties.
Computer Sabotage
Think carefully before you set up Portspoof to launch its own exploits. Many governments consider such measures no different from other forms of attack. Section 303b of the German Penal Code sanctions the transmission of data "with the intent of causing another disadvantage" under the heading of "Computer Sabotage," with prison sentences of up to 10 years (in extreme cases).
Individual port requests are entirely legitimate and necessary to establish a connection in many cases, so it isn't always wise to regard every port request as an attack and respond with a counterattack.
This is by no means the end of the fun for the target of the scan. Piotr Duszynski seems to have developed Portspoof under the motto that nothing is unfriendly enough for attackers, and therefore built in several additional fuzzing functions. For example, you can return several payloads specified in a file to an individual port or even generate completely arbitrary payloads in queries. A call to portspoof -f </path/to/redridinghood>.txt -D
treats the scanner to a rendition of the fairy tale "Little Red Riding Hood" – known as "Little Red Cap" in the German version (Figure 3) – and portspoof -1 -D
would generate random signatures (Figure 4).


Enable another fuzzer by adding -1
or -f </path/text>.txt
with -n /path/signature_name.txt
to a signature file. Now Portspoof not only provides entertaining, instructive, or motley payloads, but additionally adds services for signatures that you actually might encounter in the wild (Figure 5).

By returning arbitrary or predefined signatures and payloads, Portspoof significantly slows down a network scanner. With the service emulation alone, the time for a scan of the entire port range in the test was just under 10 hours (Figure 6); without Portspoof, it would have been done in just over 90 seconds. If you bring fuzzing into play, an attacker needs even more patience; a scan of all ports can take 30 hours or more.

Buy this article as PDF
(incl. VAT)
Buy Linux Magazine
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Subscribe to our ADMIN Newsletters
Support Our Work
Linux Magazine content is made possible with support from readers like you. Please consider contributing when you've found an article to be beneficial.
News
-
Arch Linux 2023.12.01 Released with a Much-Improved Installer
If you've ever wanted to install Arch Linux, now is your time. With the latest release, the archinstall script vastly simplifies the process.
-
Zorin OS 17 Beta Available for Testing
The upcoming version of Zorin OS includes plenty of improvements to take your PC to a whole new level of user-friendliness.
-
Red Hat Migrates RHEL from Xorg to Wayland
If you've been wondering when Xorg will finally be a thing of the past, wonder no more, as Red Hat has made it clear.
-
PipeWire 1.0 Officially Released
PipeWire was created to take the place of the oft-troubled PulseAudio and has finally reached the 1.0 status as a major update with plenty of improvements and the usual bug fixes.
-
Rocky Linux 9.3 Available for Download
The latest version of the RHEL alternative is now available and brings back cloud and container images for ppc64le along with plenty of new features and fixes.
-
Ubuntu Budgie Shifts How to Tackle Wayland
Ubuntu Budgie has yet to make the switch to Wayland but with a change in approaches, they're finally on track to making it happen.
-
TUXEDO's New Ultraportable Linux Workstation Released
The TUXEDO Pulse 14 blends portability with power, thanks to the AMD Ryzen 7 7840HS CPU.
-
AlmaLinux Will No Longer Be "Just Another RHEL Clone"
With the release of AlmaLinux 9.3, the distribution will be built entirely from upstream sources.
-
elementary OS 8 Has a Big Surprise in Store
When elementary OS 8 finally arrives, it will not only be based on Ubuntu 24.04 but it will also default to Wayland for better performance and security.
-
OpenELA Releases Enterprise Linux Source Code
With Red Hat restricting the source for RHEL, it was only a matter of time before those who depended on that source struck out on their own.