Mobile SDKs: Use with Caution
summary
Average Android apps contain 17 SDKs on average (one app had 60), and SafeDK’s analysis finds 70% of SDKs read the list of installed apps, 9% access email accounts while only 4% disclose PII, and ~6% try to use the microphone. Store actions include Google banning 155 apps and Apple 250 over malicious SDKs, and 18,000 apps contained SMS-stealing SDKs. SafeDK builds a wrapped meta‑SDK with Android Studio/Xcode plugins, realtime visibility and a switch off an SDK remotely feature that toggles SDK code or permissions without resubmitting.
AI-written summary · about
chapters (6)
- 0:00Introduction and SDK basics
- 3:27Risks of integrating SDKs
- 8:22User experience impacts
- 12:14Balancing SDK use and risks
- 13:19SafeDK solution overview
- 16:26Q&A session
related talks
15mAvoiding Security and Privacy Issues in SDK Integration
23mSpeed Trap Ahead - Avoiding Costly Security and Privacy Issues in SDK Integration
43mTrusting SDKs
35mTrusting iOS SDKs
26mPrivacy in SDKs
23mWhy an SDK is Needed to Protect APIs from Mobile Apps
28mEmbracing innovation by building privacy friendly apps
24mModern Android App Security: Protecting Code, Keys, and Data