https://github.com/1ultimat3/BadIntent

Intercept, modify, repeat and attack Android's Binder transactions using Burp Suite
https://github.com/1ultimat3/BadIntent

android burp-extensions mobile-security pentesting

Last synced: 21 days ago
JSON representation

Intercept, modify, repeat and attack Android's Binder transactions using Burp Suite

• Host: GitHub
• URL: https://github.com/1ultimat3/BadIntent
• Owner: 1ultimat3
• License: bsd-3-clause
• Archived: true
• Created: 2017-07-17T18:01:58.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2017-08-20T20:32:29.000Z (over 7 years ago)
• Last Synced: 2024-07-30T14:17:34.484Z (4 months ago)
• Topics: android, burp-extensions, mobile-security, pentesting
• Language: Java
• Homepage:
• Size: 3.62 MB
• Stars: 322
• Watchers: 34
• Forks: 62
• Open Issues: 6
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-hacking-lists - 1ultimat3/BadIntent - Intercept, modify, repeat and attack Android's Binder transactions using Burp Suite (Java)

README

        
# BadIntent

## Introduction

BadIntent is the missing link between the Burp Suite and the core Android's IPC/Messaging-system.  BadIntent consists of two parts, an Xposed-based module running on Android and a Burp-plugin. Based on this interplay, it is possible to use the Burp's common workflow and all involved tools and extensions, since the intercept and repeater functionality is provided. BadIntent hooks deeply into the Android system, performs various method redirections in Parcels and adds additional services to provide the described features. Most notably, BadIntent works system-wide (**experimental**) and is not restricted to individual user apps.

BadIntent can used to perform various pentesting activities such as the following [examples](https://github.com/mateuszk87/BadIntent/wiki/Showcases):

  * identifying [insecure logging](https://github.com/mateuszk87/BadIntent/wiki/Showcases#insecure-logging), [access control issues](https://github.com/mateuszk87/BadIntent/wiki/Showcases#access-control-issues), [pasteboard vulnerabilities](https://github.com/mateuszk87/BadIntent/wiki/Showcases#pasteboard-vulnerability), 

  * conduct and configure [intent sniffing](https://github.com/mateuszk87/BadIntent/wiki/Showcases#intent-sniffing), [brute force attacks](https://github.com/mateuszk87/BadIntent/wiki/Showcases#brute-force),  

  * [AIDL testing](https://github.com/mateuszk87/BadIntent/wiki/Showcases#aidl-testing), [GCM attacks](https://github.com/mateuszk87/BadIntent/wiki/Showcases#cloud-messaging), and searching for [WebView vulnerabilities](https://github.com/mateuszk87/BadIntent/wiki/Showcases#mobile-xss-web-view) 

  * and finally how BadIntent can be (mis-)used as a [keylogger](https://github.com/mateuszk87/BadIntent/wiki/Showcases#keylogger)



## Installation

The most handy approach is to install BadIntent Android from the Xposed Module Repository and BadIntent Burp from the Burp’s BApp Store. Both are made available/submitted before the Arsenal presentation of BadIntent in Black Hat Las Vegas 2017.

 * [Xposed Repo Module](http://repo.xposed.info/module/de.mat3.badintent)

 * [BApp Store Ref](https://portswigger.net/bappstore/bapps/)

## Environment

BadIntent has been tested on Genymotion with Xposed v87 on Android Marshmallow (6.0) and Burp Suite 1.7.23 (Free and Pro).

There are known limitations in hooking all system apps and all interfaces. During the boot proccess the Android system will remain in a boot loop and you will not be able to uninstall BadIntent from your Android device. Therefore, it is strongly recommended to use the mentioned setup in case all system apps are hooked. 

## Configuration & Usage

Please refer to the [wiki](https://github.com/mateuszk87/BadIntent/wiki) for more details.

## License

BadIntent is released under a 3-clause BSD License. See LICENSE for full details.