You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've started using these pretty nifty wireless keyloggers on engagements. They're super handy! They spin up a little AP and let you connect to them to view keystrokes, so you dont have to, say, re-gain access to an office, or even a floor if you're within "wifi earshot".
Cool part: there are creds in here! rad!
Not so cool part: I can't use the creds unless I can inject keystrokes.
There is no current solution available for a, sorta, dual-wield device that both captures keystrokes, and then lets you arbitrarily re-inject them. The closest thing is the ESPKEY, which sorta does this, except its with that wiegand 1wire protocol for rfid badges and not keystrokes.
Understanding this is an ubertooth we're dealing with and not a keylogger, it stands to reason they coudl be deployed at the same time, and run sorta akimbo: 1) deploy wifi keylogger and nab keystrokes with creds, then 2) use uberducky to inject keystrokes.
Do you think something like this is possible to add to the uberducky functionality, or am I crazy? (it's okay to say I'm crazy).
The text was updated successfully, but these errors were encountered:
I've started using these pretty nifty wireless keyloggers on engagements. They're super handy! They spin up a little AP and let you connect to them to view keystrokes, so you dont have to, say, re-gain access to an office, or even a floor if you're within "wifi earshot".
Cool part: there are creds in here! rad!
Not so cool part: I can't use the creds unless I can inject keystrokes.
There is no current solution available for a, sorta, dual-wield device that both captures keystrokes, and then lets you arbitrarily re-inject them. The closest thing is the ESPKEY, which sorta does this, except its with that wiegand 1wire protocol for rfid badges and not keystrokes.
Understanding this is an ubertooth we're dealing with and not a keylogger, it stands to reason they coudl be deployed at the same time, and run sorta akimbo: 1) deploy wifi keylogger and nab keystrokes with creds, then 2) use uberducky to inject keystrokes.
Do you think something like this is possible to add to the uberducky functionality, or am I crazy? (it's okay to say I'm crazy).
The text was updated successfully, but these errors were encountered: