-
Notifications
You must be signed in to change notification settings - Fork 192
Chrome cookies bug. #358
Comments
There could be various reasons. Since the victim are using chrome in the screenshot, this means the cookies file was locked by chrome's process and the grabber couldn't access it. The grabber already kills the process, but the victim may have reopened the browser before the grabber could copy the files. |
Will you add something to bypass it? Its kinda annyoing when just reopening the browser breaks everything and u cant rlly do much with this |
Just make browsers un-openable during cookie stealing @Blank-c |
I don't think its possible. |
Maybe make it delete/move to other directory the browser Executable during process |
Nope. can't do this. |
Why? |
He can do it I'm sure |
|
Hi, i just saw i got 0cookies from chrome (i mean theres no file) but on a screenshot i can see victim using chrome and being logged on sites.
The text was updated successfully, but these errors were encountered: