All Projects → StopDDoS → packet-captures

StopDDoS / packet-captures

Licence: other
packet captures of real-world ddos attacks

Projects that are alternatives of or similar to packet-captures

A-Detector
⭐ An anomaly-based intrusion detection system.
Stars: ✭ 69 (-20.69%)
Mutual labels:  wireshark, pcap-analyzer
anti-ddos-lite
Anti-DDoS-Lite (Anti-Crawler app) is a small PHP app to protect your site against DDoS attack.
Stars: ✭ 96 (+10.34%)
Mutual labels:  ddos, ddos-protection
PoW-Shield
Project dedicated to fight Layer 7 DDoS with proof of work, featuring an additional WAF. Completed with full set of features and containerized for rapid and lightweight deployment.
Stars: ✭ 99 (+13.79%)
Mutual labels:  ddos, ddos-protection
DDOS Detection
ddos attack detector using ML Algorithms
Stars: ✭ 38 (-56.32%)
Mutual labels:  ddos, ddos-protection
epiphany
A pre-DDoS security assessment tool
Stars: ✭ 106 (+21.84%)
Mutual labels:  ddos, ddos-protection
Anti-DDOS-Script
Anti DDOS Protection that will stop DDOS from taking down your Linux Server
Stars: ✭ 51 (-41.38%)
Mutual labels:  ddos, ddos-protection
gosynflood
Demonstrates a synflood DDOS attack with raw sockets (for Ubuntu and Debian-like distros)
Stars: ✭ 88 (+1.15%)
Mutual labels:  ddos
simtrace2
Osmocom SIM card tracer, v2.0; mirror of https://gitea.osmocom.org/sim-card/simtrace2
Stars: ✭ 54 (-37.93%)
Mutual labels:  wireshark
rvi capture
rvictl for Linux and Windows: capture packets sent/received by iOS devices
Stars: ✭ 124 (+42.53%)
Mutual labels:  wireshark
overload
📡 Overload DoS Tool (Layer 7)
Stars: ✭ 167 (+91.95%)
Mutual labels:  ddos
hashseq
A simple proof of work, mainly designed to mitigate DDoS attacks.
Stars: ✭ 20 (-77.01%)
Mutual labels:  ddos
HULK-v3
Asynchronous HTTP Botnet for Distributed Denial of Service (DDoS)
Stars: ✭ 152 (+74.71%)
Mutual labels:  ddos
ddos-mitigation
Tips to mitigate and secure your large-scale server against DDoS attacks.
Stars: ✭ 58 (-33.33%)
Mutual labels:  ddos
DDoS-Script
A script written in perl for ddos ​​with automatic detection of open and vulnerable port that gives up to 1.5 gb packages / s
Stars: ✭ 30 (-65.52%)
Mutual labels:  ddos
sqredirect
Redirection and filtering Source Engine game traffic in bundle with sqproxy
Stars: ✭ 21 (-75.86%)
Mutual labels:  ddos
palantir
🔮 HTTP REST API reverse proxy
Stars: ✭ 21 (-75.86%)
Mutual labels:  ddos-protection
Python3-Botnet
Project moved to -> https://github.com/Leeon123/Aoyama
Stars: ✭ 24 (-72.41%)
Mutual labels:  ddos
url-regex-safe
Regular expression matching for URL's. Maintained, safe, and browser-friendly version of url-regex. Resolves CVE-2020-7661 for Node.js servers.
Stars: ✭ 59 (-32.18%)
Mutual labels:  ddos
ChromeBluetooth
Demo of a "Stress Display" using Chrome Bluetooth. Reads Heart-rate data, and displays "stress" colors to a smart bulb. (Uses a SBT5007 smart bulb)
Stars: ✭ 14 (-83.91%)
Mutual labels:  wireshark
8821au
Linux Driver for USB WiFi Adapters that are based on the RTL8811AU and RTL8821AU Chipsets
Stars: ✭ 67 (-22.99%)
Mutual labels:  wireshark

DDoS Packet Capture Collection

This is a collection of multiple anonymized packet captures of real-world and lab-tested DDoS attacks.

Mirror

Github has disabled LFS on this repository due to the high amount of downloads. A zipped version of this repository can be downloaded at https://wqrld.net/captures.zip.

Goal

The goal of providing these captures is to stimulate the growth of ddos research. Real-world DDoS captures are hard to come by which makes research harder. We are trying to overcome that issue.

License

These captures may be freely used to build and improve DDoS Protection systems. Attribution is not required, but greatly appreciated. Do not claim any of these resources as your own.

Citing

The following information can be used when citing this dataset:

L.F. Haaijer, DDoS Packet Capture Collection, (2022). Available from https://github.com/StopDDoS/packet-captures

Contributing

If these captures or any of our other resources were useful to you, or you just want to help, Please contribute through one of our github repositories.

Make sure that these captures only show one-way (incoming) traffic and are atleast 99% real ddos traffic (preferably 100%, but this may include things like icmp control messages. Please leave those in.)

If you prefer to anonymize your captures because they may contain real user information. Please do. Instructions are below.

Naming scheme

This project uses a very lean naming scheme. The name should start with either amp (amplification) or pkt (spoofed/direct) and then udp/tcp/another protocol. For amplification, if you know what protocol is being used, please add the protocol name (eg SNMP). Otherwise please use the port. Other than that you can add any other information as long as the title stays short and identifyable.

Anonymizing your own packet captures

First, open your capture in wireshark and write a display filter to only select traffic that's part of your attack. For example udp && ip.dst == 10.10.10.10 && udp.dstport == 8080. Then under file > export specified packets write a new filtered pcap.

(optionally, but recommended) Also anonymize the destination ip. This can for example be done with tcpreplay's tcprewrite

for file in $(ls);
  do tcprewrite --infile=$file --outfile=/root/anonymous/$file --dstipmap=0.0.0.0/0:10.10.10.10;
done
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].