Closed darknightmc80 closed 1 year ago
To test my claim against it, I put it on the device and set it up. While testing, I attempted to run the payload on the PC's virtual machine, but it failed to capture the five dummy credentials that I had previously saved in Chrome.
Can you tell me:
1) The Chrome version.
2) The Windows version.
3) Does %localappdata%\Google\Chrome\User Data
exists?
4) Is your PC a VM, and if it is then what type (Windows sandbox/VMware/Virtual Box/RDP/something else)?
5) Does this tool shows your passwords?
And if there were error logs in the archive file, can you show them?
To test my claim against it, I put it on the device and set it up. While testing, I attempted to run the payload on the PC's virtual machine, but it failed to capture the five dummy credentials that I had previously saved in Chrome.
Can you tell me:
- The Chrome version.
- The Windows version.
- Does
%localappdata%\Google\Chrome\User Data
exists?- Is your PC a VM, and if it is then what type (Windows sandbox/VMware/Virtual Box/RDP/something else)?
- Does this tool shows your passwords?
And if there were error logs in the archive file, can you show them?
1.Chrome: 115.0.5790.110 2.Windows: 22H2 3.yes it does 4.VMware 5.yep it does show em
Also side note what is the password for the Blank-{username}.rar file it generates in the dc server with the grabbed data
Also side note what is the password for the Blank-Abby.rar file it generates in the dc server with the grabbed data
Look inside config.json file along with the builder.
Hey there, I am unable to reproduce the problem. Can you try to run the grabber with keeping chrome closed.
I tried running it while Chrome was closed and it worked fine. However, when I ran it with Chrome open, there were some issues. To improve the user experience, it may be useful to add a feature that terminates Chrome and other browser processes before attempting to grab data.
man Grammarly helps out
It actually autocloses chrome. I am not sure why your chrome was still running.
It actually autocloses chrome. I am not sure why your chrome was still running.
And I get why, given the credentials cannot be accessed at all while chrome is opened, I've already tried this with a different library.
It actually autocloses chrome. I am not sure why your chrome was still running.
And I get why, given the credentials cannot be accessed at all while chrome is opened, I've already tried this with a different library.
You get them without closing chrome? May I see the code?
One thing I tried as a poc was to try to copy the chrome's Cookies
file while it was running and Windows didn't let me do that.
I have the same version of chrome but I am unable to reproduce the issue.
To test my claim against it, I put it on the device and set it up. While testing, I attempted to run the payload on the PC's virtual machine, but it failed to capture the five dummy credentials that I had previously saved in Chrome.