zmap tuned for stealth to evade fingerprinting/tracking.
Go to file
2024-03-01 14:03:44 -06:00
conf initial 2024-02-21 18:23:18 -06:00
examples initial 2024-02-21 18:23:18 -06:00
lib initial 2024-02-21 18:23:18 -06:00
scripts initial 2024-02-21 18:23:18 -06:00
src initial 2024-02-21 18:23:18 -06:00
test initial 2024-02-21 18:23:18 -06:00
.clang-format initial 2024-02-21 18:23:18 -06:00
.editorconfig initial 2024-02-21 18:23:18 -06:00
.gitignore initial 2024-02-21 18:23:18 -06:00
10gigE.md initial 2024-02-21 18:23:18 -06:00
checkFormat.sh initial 2024-02-21 18:23:18 -06:00
CMakeLists.txt initial 2024-02-21 18:23:18 -06:00
format.sh initial 2024-02-21 18:23:18 -06:00
README.md initial 2024-03-01 14:03:44 -06:00
release-build.sh initial 2024-02-21 18:23:18 -06:00

zmap - mark II

zmap stripped of its trackers. evades fingerprinting by threat intelligence firms, service providers, and everyone in between.

Why?

the original zmap contains values in its headers that are used to identify the traffic as belonging to zmap.

this makes it easy for threat intelligence agencies, isp's, and anyone else to fingerprint zmap traffic and generate alerts/tags/abuse reports accordingly.

Installation

dependencies: cmake, gmp, gengetopt, libpcap, flex, byacc, json-c, libunistring, pkg-config, libjudy

to install the dependencies on debian based systems:

sudo apt install -y build-essential cmake libgmp3-dev gengetopt libpcap-dev flex byacc libjson-c-dev pkg-config libunistring-dev libjudy-dev

compile it with

git clone https://git.supernets.org/delorean/zmap-mark-ii
cd zmap-mark-ii
cmake .
make -j4

then install it via

sudo make install

Usage

zmap -h

refer to zmap's usage