You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
11.2 Secure Implementation Recommendations. Mobile Security 2026
#1600
Intent Spoofing & Hijacking Prevention: Validate the sender and verify incoming data within the receiving component before acting on it.
Use getCallingActivity() or getCallingPackage() to check if the caller matches a trusted package name and certificate.
Secure Intent Dispatches: When launching an internal component, use explicit intents (specifying the exact target class or package) instead of implicit intents. This prevents malicious third-party apps on the same device from intercepting or "hijacking" the intent.
val explicitIntent =Intent(context, TargetActivity::class.java).apply {
putExtra("param", value)
}
startActivity(explicitIntent)
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
getCallingActivity()orgetCallingPackage()to check if the caller matches a trusted package name and certificate.Source section. MOBILE-SECURITY-2026.md, 11.2 Secure Implementation Recommendations.
This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run
bash scripts/install.sh install, then run the guard on your project before you submit. Questions or a correction? Reply below.All reactions