Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

suggestion: wifi spammer #344

Open
guibais opened this issue Oct 1, 2015 · 13 comments
Open

suggestion: wifi spammer #344

guibais opened this issue Oct 1, 2015 · 13 comments

Comments

@guibais
Copy link

guibais commented Oct 1, 2015

imagine, if you can make huge fake clients connecting to the wifi, the ITs guys will be crazy!!. i think it's an awesome feature to implement.

@Rubenoo
Copy link
Contributor

Rubenoo commented Oct 1, 2015

Or like redirect everyone on the wifi to a custom page that you can make

@domenicoblanco
Copy link

@Rubenoo You can already do this with the MITM when you attack the subnet

@Rubenoo
Copy link
Contributor

Rubenoo commented Oct 1, 2015

Yeah but i meant that you can upload a custom webpage or site like in social engineering and get the results back you know

@guibais
Copy link
Author

guibais commented Oct 1, 2015

@Rubenoo you can already do that

@tux-mind
Copy link
Member

tux-mind commented Oct 4, 2015

@Haxin-hipopcorn I didn't understand what is the feature request.
please explain in detail and thanks for your time 😉

@ETeissonniere
Copy link
Member

Maybe it was "wifi jammer"...
The goal is to disconnect all the client of an AP
Le 4 oct. 2015 23:49, "tux-mind" notifications@github.com a écrit :

@Haxin-hipopcorn https://github.com/Haxin-hipopcorn I didn't understand
what is the feature request.
please explain in detail and thanks for your time [image: 😉]


Reply to this email directly or view it on GitHub
#344 (comment).

@guibais
Copy link
Author

guibais commented Oct 6, 2015

@tux-mind fake clients in the app, for example you run csploit and show a lot of fake targets, then you will make the owners of the network being confused

@tux-mind
Copy link
Member

tux-mind commented Oct 6, 2015

on a static ip LAN you'll get collisions with existing addresses ( admin get stats only if a sniffer it's installed on the router ).
on a DHCP LAN is enough to start many DHCP requests until the DHCP server finishes up it's pool.
this will also prevent other clients to connect to the network.

we can make it, but I really want to ask who else will find it useful.

@ETeissonniere
Copy link
Member

I think it is not, sorry.
Le 6 oct. 2015 09:32, "tux-mind" notifications@github.com a écrit :

on a static ip LAN you'll get collisions with existing addresses ( admin
get stats only if a sniffer it's installed on the router ).
on a DHCP LAN is enough to start many DHCP requests until the DHCP server
finishes up it's pool.
this will also prevent other clients to connect to the network.

we can make it, but I really want to ask who else will find it useful.


Reply to this email directly or view it on GitHub
#344 (comment).

@guibais
Copy link
Author

guibais commented Oct 6, 2015

@tux-mind it will be usefull to disguise, think with me, if they want to find you, spamming a lot of clients, they will cannot find you!!, or if they want to filter some macs... will be difficulty, or just if someone tries to search for clients, or do an nmap, it will be sooo sloowww, so we have a lot of utilities.

@0MazaHacka0
Copy link
Contributor

It will be useful

@Rubenoo
Copy link
Contributor

Rubenoo commented Oct 9, 2015

It would be nice if you could crash the router for a while :)

@newbie442
Copy link

ISTM the original post is very interesting - and likely a different tool than csploit.

IIUC, the suggested tool would create multiple connections with the WAP, using multiple spoofed MAC addresses, and each would effect traffic with the WAP - perhaps additionally signing in and effecting traffic with the WAN via the WAP.

This might do a couple of things:

  1. Hide the csploit user from a whitehat in a crowded room.
  2. Hide the csploit user from an attacker within the crowd.

(I actually doubt that 1. would succeed, but suspect that it could confuse would be attackers - "which target to attack?" This seems a very complex app)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants