Marauder Flipper Zero, ESP32-Wifi-Hacking

Hello there!

This documentation is on how to crack a WPS/WPA2 encrypted wifi password using Flipper Zero WiFi-Development board.

Welcome to the ESP32-Wifi-Hacking project! This project aims to provide a comprehensive guide on how to crack WPS/WPA2 encrypted WiFi passwords using the Flipper Zero WiFi-Development board.

Project Overview

This project is designed for educational purposes only. It demonstrates how to use the Flipper Zero WiFi-Development board to perform WiFi penetration testing. Please use this information responsibly and only on networks you own or have permission to test. Alright, let's get started!

Use the Table of Contents to view the page

Install the prerequisites

Table of Contents for this page:

• Install the prerequisites
  • Table of Contents for this page:
    • Install the Marauder Flash
• Install WireShark
  • Install Hashcat
  • Install the crack passwords
  • What I Used: For this tutorial

Install the Marauder Flash

This is the link to install the Marauder Flash

It's recommended to flash the Marauder Flash to the flipper development using Linux or Mac OS.

Windows have an issue for quite some time, so it's recommended to run on Linux or MacOS

Make sure to choose option 2! That option will allow you to save the .pcap file to the SD card.

Install WireShark

Wireshark Download

Install Hashcat

Download the latest release of it

After that, use 7zip to extract the file.

Then open the command prompt and type in the following command:

cd C:\Users\%USERNAME%\Downloads\hashcat-6.2.4

This will change the directory to the hashcat folder.

Install the crack passwords

Huge (74 gig): This large list of passwords

Common: Password list

What I Used: For this tutorial

Execution Phase

Great! Now that you have installed all the prerequisites, let's get started!

Step 0:

Navigate to Applications -> GPIO -> [ESP32] Wifi Marauder

Step 1:

Scan your AP

Step 2:

Select the AP you want to Deauth and Sniff

Step 3:

Find your SSID and remember the number beside it.

Step 4:

Press on Select and Key in the number beside your SSID. Example: 1

Step 5:

Before you press on the Deauth button, change your Sniff to raw to make sure that you can sniff the handshake.

Step 6:

Get your pcap file from the Flipper Zero and open it with Wireshark.

SD Card -> app_data -> marauder -> pcap -> Sniffraw_1.pcap

Step 7:

Go click on the .pcap file and it will open up Wireshark.

Type on the filter bar: eapol

You should have something like this: key(Message 1 of 4), key(Message 2 of 4), key(Message 3 of 4) and key(Message 4 of 4)

Step 8:

Go to this website and upload your .pcap file

And download the .hc22000 file.

Step 9:

Drag the .hc22000 file into the hashcat folder.

AND also the cracked.txt.gz file into the hashcat folder (depends on what you want to crack).

Make sure both files are in the same folder.

Open up CMD and CD to the hashcat folder.

Afterward, run this command:

hashcat -m 22000 (your .hc22000 file) (your cracked.txt.gz file)

Your password will be cracked in a few seconds or minutes depending on your computer and the password.

```

Conclusion

You can use this method to crack any WPA/WPA2 password. But it's not 100% guaranteed that you can crack the password. It depends on the password strength and your computer.

Please do not use this method to crack other people's wifi passwords. This is for educational purposes only—do it on your own wifi! Happy hacking!

                             Apache License
                       Version 2.0, January 2004
                    http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

   "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

   "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

   "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

   "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

   "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

   "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

   "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

   "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

   "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

   "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

   (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

   (b) You must cause any modified files to carry prominent notices stating that You changed the files; and

   (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

   (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

   You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

  To apply the Apache License to your work, attach the following
  boilerplate notice, with the fields enclosed by brackets "[]"
  replaced with your own identifying information. (Don't include
  the brackets!)  The text should be enclosed in the appropriate
  comment syntax for the file format. We also recommend that a
  file or class name and description of purpose be included on the
  same "printed page" as the copyright notice for easier
  identification within third-party archives.

Copyright [2024] [StepSisStuck]

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

   http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Contributing to ESP32-Wifi-Hacking

Thank you for your interest in contributing to the ESP32-Wifi-Hacking project! We welcome contributions from the community and are grateful for your support.

Guidelines for Contributing

Coding Standards

• Follow the existing coding style and conventions used in the project.
• Write clear and concise code with appropriate comments.
• Ensure that your code is well-documented and includes necessary explanations.

Commit Message Conventions

• Use clear and descriptive commit messages.
• Follow the format: type(scope): subject
  • type: The type of change (e.g., feat, fix, docs, style, refactor, test, chore).
  • scope: The scope of the change (e.g., module, component, file).
  • subject: A brief description of the change.

Pull Request Process

1. Fork the repository and create a new branch for your contribution.
2. Make your changes and ensure that the code builds and passes all tests.
3. Submit a pull request with a clear description of your changes.
4. Address any feedback or comments provided during the review process.

Setting Up the Development Environment

To set up the development environment for ESP32-Wifi-Hacking, follow these steps:

1. Clone the repository:

   git clone https://github.com/StepSisStuck/ESP32-Wifi-Hacking.git
   

2. Navigate to the project directory:

   cd ESP32-Wifi-Hacking
   

Reporting Issues and Requesting Features

If you encounter any issues or have feature requests, please follow these guidelines:

1. Check the existing issues to see if your problem or request has already been reported.
2. If not, create a new issue with a clear and descriptive title.
3. Provide detailed information about the issue or feature request, including steps to reproduce the problem if applicable.

If there is an issue

If you have any questions or need further assistance, you can create an issue, and I will get back to you!

Thank you for contributing to ESP32-Wifi-Hacking!