siege-engine
A general basic Python-powered SYN flooder bot.
Installation and operation
Just type:
pip install siege-engine
python -m siege_engine 300 tass.com
Note that a helpful error message will be displayed if you just type:
python -m siege_engine
Please set the 300 value regarding your network conditions. This is the amount of threads that will be spawned. Obviously, more is better (I bet your network could hold about 2000 of them).
Note that increasing thread count about 100% CPU usage is pointless, because of the GIL. You can, altogether, fire up multiple instances :D
Just note that GIL is not a practical limit, I've tested it on my PC with 15k threads and it ate only 23% of the CPU, so it's more academic concern.
Note that if zero connections were made, that means the target server is no longer responding, which is a good thing.
Change log
- v2.0: Better messages
- v1.9: added a total counter for wasted bytes
- v1.8: fixed problems with termination
- v1.7: Removed scapy
- v1.6: Added scapy
- v1.5: SSL socket will be picked upon now
- v1.4: fixed a critical bug
- v1.3: significantly refactored the code
- v1.2: since v1.1 we're been hosted on PyPI, removed these nasty entry points
- v1.1: added graceful support for time-out sessions
How to adjust thread count.
Start from 13000. The startup time for 25000 threads is pretty rough, but overall the app manages to start. If the process manages to hit a single core 100%, start a new program, or just reduce the amount of threads. The process is network-bound.
Valid targets
- tass.com
- kremlin.ru
- eng.putin.kremlin.ru
- eng.constitution.kremlin.ru
- eng.flag.kremlin.ru
- lenta.ru
- government.ru
- rt.com
- ach.gov.ru
- customs.ru
- economy.gov.ru
- fas.gov.ru
- fedsfm.ru
- gks.ru
- minfin.ru
- nalog.ru
- rosreestr.ru
- rosreserv.ru
- gosbar.gosuslugi.ru
- cikrf.ru
- council.gov.ru
- duma.gov.ru
- government.ru
- kremlin.ru
- open.gov.ru
- gusp.gov.ru
- udprf.ru
- fapmc.ru
- rkn.gov.ru
- fso.gov.ru
- gfs.ru
- rossvyaz.ru
- digital.gov.ru
- fstec.ru
- rs.gov.ru
- fsvts.gov.ru
- mid.ru
- russiatourism.ru
- ombudsmanrf.org
- rosmintrud.ru
- rostrud.ru
- archives.ru
- fsa.gov.ru
- gost.ru
- fadm.gov.ru
- obrnadzor.gov.ru
- federalspace.ru
- mkrf.ru
- rupto.ru
- edu.gov.ru
- minobrnauki.gov.ru
- minvostokrazvitia.ru
- mil.ru
- nac.gov.ru
- svr.gov.ru
- fsb.ru
- mchs.gov.ru
- scrf.gov.ru
- rosavtodor.ru
- favt.ru
- mintrans.ru
- morflot.ru
- rostransnadzor.ru
- roszeldor.ru
- fsin.su
- genproc.gov.ru
- ksrf.ru
- mvd.ru
- rosgvard.ru
- fssprus.ru
- minjust.ru
- xn--b1ab2a0a.xn--b1aew.xn--p1ai
- rpn.gov.ru
- voda.mnr.gov.ru
- fishcom.ru
- fsvps.ru
- gosnadzor.ru
- mcx.ru
- meteorf.ru
- mnr.gov.ru
- rosleshoz.gov.ru
- rosnedra.gov.ru
- fmbaros.ru
- rosminzdrav.ru
- rospotrebnadzor.ru
- minsport.gov.ru
- roszdravnadzor.ru
- minenergo.gov.ru
- minpromtorg.gov.ru
- minstroyrf.ru
- data.gov.ru
- partners.gosuslugi.ru
- gosuslugi.ru
If you have any better ideas, PRs are welcome!
Usage via Docker
You can use the excellent Docker image at https://github.com/maksym-iv/battle-tools#siege-engine.
Metadata
Release files for siege-engine 3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| siege-engine-3.0.tar.gz | 5.1 kB | Without provenance | Details for siege-engine-3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| siege_engine-3.0-py3-none-any.whl | Python 3 | none | any | Details for siege_engine-3.0-py3-none-any.whl |
Total release size: 10.3 kB
Release files / siege-engine-3.0.tar.gz
| Download URL | siege-engine-3.0.tar.gz |
|---|---|
| Size | 5.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a9de6e5a1569517a77046bad800cc6526c0ae7d31794bcd04a6c9a5dceaf5694
|
|
BLAKE2b-256 checksum How to use checksums |
76b56e08f47c6843d764db6b7d8af19a190cfd874dc3c558778f66fcd4c615cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.0 requests-toolbelt/0.9.1 urllib3/1.26.7 tqdm/4.62.3 importlib-metadata/4.11.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.0
|
Release files / siege_engine-3.0-py3-none-any.whl
| Download URL | siege_engine-3.0-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2475ca00de61e343fd45cf2a77d6b0254769d3795e2c30cf8b5af3b52b18fe0b
|
|
BLAKE2b-256 checksum How to use checksums |
59d7c93ec3f93914ae3f3c6df2fee77596c3f770b7ee2342817fa02c118ed994
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.0 requests-toolbelt/0.9.1 urllib3/1.26.7 tqdm/4.62.3 importlib-metadata/4.11.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.0
|
Security for siege-engine 3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.