I posted it already, but if you are looking to get into reverse-engineering App's (like android apps, such as Star Wars: Commander) I've put together a small list of resources. I'll also give my notes at the end since Q has told us to work together, essentially, in that one picture of people climbing a hill.
Resources
Virtual Environment
https://www.virtualbox.org/
Operating System Suggestion (Ubuntu is user-friendly)
https://ubuntu.com/
Star Wars: Commander App:
https://apkpure.com/star-wars%E2%84%A2-commander/com.lucasarts.starts_goo
-or-
https://star-wars-commander.en.uptodown.com/android
Ghidra
https://ghidra-sre.org/
Jadx (helpful for this project and other android apps)
https://github.com/skylot/jadx
Tutorial for Basic App Reverse Programming (get the .ova in this tutorial and load it into VirtualBox, it's essentially loaded with what the tutorial goes through)
https://maddiestone.github.io/AndroidAppRE/index.html
As a rule of thumb its much safer to run everything through the virtualbox, but if you want to all the above will also work/have options to work on an average Windows machine. I wouldn't suggest it, but I can't say that I'm above just running it all on my computer anyway. I'll accept the risk.
Exploratory Notes
As a disclaimer, I'm very new to software engineering and I've never reverse-engineered anything before in my life. Having said that, I encourage anyone with an interest in this to try their hand. The more people we have on this the better.
So right off the bat, looking at the AndroidManifest.xml, it looks like this application runs like a normal app does with nothing nefarious that stands out. I'm not seeing anything out of the ordinary in the Manifest but I still have a loooooooooooooot of code to go through. I did notice that a few things can be activated by other apps/programs though:
FBUnityDeepLinkingActivity (fuck you FaceBook)
SwrvePushEngageReceiver
SwrveEngageEventSender
FirebaseMessagingService
FirebaseInstanceIdService
Only thought on this is that the Firebase messaging service seems to be able to activate even when the app is closed, but I don't think that in and of itself is abnormal or malicious, as apps should be able to do this (right?). Someone with more app development experience can tell me otherwise, but I'm going to move on.
The game runs on the Unity3d.player…
Lots of source code in Java to look through…
Boy, Facebook really likes our activity…
Nothing stands out. I'm going to take a look at the Native Libraries now and see if I can pry those apart. The 'native libraries' are the '.so' files, such as…
libbugsnag-ndk.so
libbugsnag-unity.so (another bugsnag file, ho-hum)
libil2cpp.so (my God its huge [~30MB]. That's going to take forever!)
libmain.so
libunity.so (I haven't looked just yet, but I think this is the unity engine that the game runs in. Also my God its 19MB and is going to take forever)
Kind of getting hung up. I decompiled the libl2cpp.so with Ghidra and there's an awful lot to go through here, and it takes some in-depth analysis to do so. I'm thinking I need to hit the books a bit more before I start jumping into this because passively reading and hoping that something jumps out at me will be futile.
Any suggestions would be welcome.