Contains many different ways to identify hostile environments.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
app Wrap with gradle Sep 2, 2014
gradle/wrapper Wrap with gradle Sep 2, 2014
.gitignore Wrap with gradle Sep 2, 2014
LICENSE Add license Feb 5, 2016
Readme.md Update Readme.md Feb 5, 2016
build.gradle Wrap with gradle Sep 2, 2014
gradle.properties Wrap with gradle Sep 2, 2014
gradlew Wrap with gradle Sep 2, 2014
gradlew.bat Wrap with gradle Sep 2, 2014
settings.gradle Wrap with gradle Sep 2, 2014

Readme.md

Android Hostile Environment Detection

Contains many different ways to identify hostile environments. This project is an android application that uses various techniques to identify the environment that it is currently running in. It borrows code and extends the idea offered up by BlueBox here

There was a great presentation by Oberheide and Miller with their experience poking around the emulator. This project borrows and implements ideas from it as well. Bouncer

Future work: A Fistful of RedPills a paper about auto generating ways to identify CPUs would be particularly useful in this case. The premise is that certain instructions on CPUs have undefined behavior for various registers. I.E. What state should the overflow bit have when a move regA, regB instruction is issued. It turns out that some of these states are unique enough to identify CPU families. These so-called 'pills' can also be auto generated.

Running

./gradew installDebug