Analysis the APK
Requirements:
Windows Device
MobSF
Step 1: open power shell and write command ./run.bat 127.0.0.1:8000.
Step 2: Now in your browser got to "http://localhost:8000 "and upload the APK into it:
Step 3: Now that you have '"uploaded the APK", MobSF will start analyzing it.
Step 4: When the "analysis completes" we will be presented with a nice "dashboard summarizing the result"
Step 5: The source Android Manifest xml file.
Now we have lots of information to look through, but since we are only interested in the API key we may want to start searching for it in the ''Android Manifest xml file''. We can view it by ''clicking in the dark blue button'' in thesection “View Code” at the bottom right of the above screenshot, and we will land on this page:
Step 6: String Section.
As we can see from the Android manifest file the values for "MANIFEST_API_KEY and GRADLE_API_KEY_PLACEHOLDER" are readily available, but not the ones for the "GRADLE_API_KEY and GRADLE_ENV_API_KEY", though we can see in the Android manifest that they are retrieved as strings, thus we can also easily find them in the strings section of the MobSF report:Step 7: Source code of Android manifest xml file.
One of the places where developers like to drop their "API keys", but you might be interested to take a look into the "source code" itself by "clicking on Security Analysis > Code Analysis" on the "left menu":Step 8: Now we land in a section of the page with links to files with the "source code decompiled", and there we should look for this section:
Here is no data but if there any data in the fields, we click in the link for the file, we will see the source code for it:
Comments
Post a Comment