Exodus-Privacy / Exodus-Privacy/etip

package defpackage

Open
#88 0 comments 0 reactions 0 assignees View on GitHub
tracker
Dominant language
Python
Stars
76
Forks
23
Avg merge
17d 6h
Merged PRs (30d)
2

Description

i have been seeing some of these signatures "package defpackage" and they do things like this:
import com.facebook.FacebookSdk
and
import android.media.AudioRecord;

they tend to have obfuscated class names, such as:
public static final aeyd a = aeyd.a("aasl");

and generally seem to be doing a lot of things that would ordinarily be of interest to Exodus in terms of tracking etc, which makes me think that the generic defpackage name is being used as a way of bypassing signature detection and allowing multiple sdks to be incorporated into an app via this single signature.

currently looking into this app:
https://reports.exodus-privacy.eu.org/en/reports/149926/

and i also note that com.facebook.FacebookSdk doesn't register in Exodus.
this class makes many calls to "defpackage.*"

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the referenced Exodus report and the issue's examples of com.facebook.FacebookSdk, android.media.AudioRecord, and defpackage.* calls. Determine whether the app's obfuscated package and SDK usage represent a missing tracker signature; done means documenting a reproducible finding and the required detection scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile-dev, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.