Google AdMob detection fails on new update.

[MuntashirAkon]

Previously, these signatures were used for Google Admob detection (there could be others as well but I don't know since I haven't found public VCS):

com.google.ads.|com.google.android.gms.ads.

But recently these have been changed to the following:

com.google.ads.|com.google.android.gms.ads.AdView|com.google.android.gms.ads.AdRequest|com.google.android.gms.ads.mediation|com.google.android.gms.ads.doubleclick

Which means classes such as com.google.android.gms.ads.AdActivity are skipped from scanning.

Previous static scan listed 290 classes for an app called Battery Bar Free and how it lists only 61.

[MuntashirAkon]

Also, com.google.unity.ads. seems to be missing.

[pnu-s]

Hi @MuntashirAkon

We indeed restricted the list of signatures matching for this tracker because we had some false positives. I'll investigate the 2 new signatures you mentioned, thanks!

[MuntashirAkon]

We indeed restricted the list of signatures matching for this tracker because we had some false positives.

What were the false-positives, could you, perhaps, share a link to the discussion? I've included com.google.android.gms.ads.AdActivity as an example, there are other classes that are missing there. Since Exodus only does static scans which isn't really perfect, wouldn't it be the best to leave com.google.android.gms.ads. as is instead of adding all the true positive classes?

[pnu-s]

What were the false-positives, could you, perhaps, share a link to the discussion? I've included com.google.android.gms.ads.AdActivity as an example, there are other classes that are missing there.

I think they were several discussions, but the only one I could find is this one: Exodus-Privacy/exodus#390

[MuntashirAkon]

I think they were several discussions, but the only one I could find is this one: Exodus-Privacy/exodus#390

Thanks. I'll further investigate on that matter to separate all the useful classes between Firebase Analytics and AdMob.