exploiting-deeplink-vulnerabilities

Featured

Tests and exploits deep link (URL scheme and App Link) vulnerabilities in Android and iOS mobile applications to identify unauthorized access, data injection, intent hijacking, and redirect manipulation. Use when assessing mobile app attack surface through custom URI schemes, Android App Links, iOS Universal Links, or intent-based navigation. Activates for requests involving deep link security testing, URL scheme exploitation, mobile intent abuse, or link hijacking.

AI & Automation 36,355 stars 4443 forks Updated 2 months ago Apache-2.0

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
75
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Exploiting Deep Link Vulnerabilities ## When to Use Use this skill when: - Assessing mobile app deep link handling for injection and redirect vulnerabilities - Testing Android intent filters and iOS URL scheme handlers for unauthorized access - Evaluating App Links (Android) and Universal Links (iOS) verification - Testing for link hijacking via competing app registrations **Do not use** without authorization -- deep link exploitation can trigger unintended actions in target applications. ## Prerequisites - Android device with ADB or iOS device with Objection/Frida - APK decompiled with apktool or JADX for AndroidManifest.xml analysis - Knowledge of target app's registered URL schemes and intent filters - Drozer for Android intent testing - Burp Suite for intercepting deep link-triggered API calls ## Workflow ### Step 1: Enumerate Deep Link Entry Points **Android - Extract from AndroidManifest.xml:** ```bash # Decompile APK apktool d target.apk -o decompiled/ # Search for intent filters with deep link schemes grep -A 10 "android.intent.action.VIEW" decompiled/AndroidManifest.xml # Look for: # <data android:scheme="myapp" android:host="action" /> # <data android:scheme="https" android:host="target.com" /> ``` **iOS - Extract from Info.plist:** ```bash # Extract URL schemes plutil -p Payload/TargetApp.app/Info.plist | grep -A 5 "CFBundleURLSchemes" # Extract Universal Links (Associated Domains) plutil -p Payload/TargetApp.app/Info.plist | grep -A 5 "com.apple.deve...

Details

Author
mukul975
Repository
mukul975/Anthropic-Cybersecurity-Skills
Created
8 months ago
Last Updated
2 months ago
Language
Python
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

android-deeplink-applink-abuse

Exploit Android deep links and App Links — unvalidated params in BROWSABLE activities, custom-scheme OAuth-callback hijacking, open redirect into WebViews, and App Links verification gaps (missing/invalid assetlinks.json). Tier 1. Use when the manifest declares deep-link intent-filters. Aligns to OWASP MASTG MASVS-PLATFORM (MASTG-TEST-0028).

26 Updated 2 days ago
AnandJogawade
AI & Automation Listed

mobile-deeplink-abuse

Abuse deep links / custom URL schemes / intents for redirect, token theft, and reaching internal screens. Load on custom schemes (myapp://), App Links/Universal Links, exported activities, or "open in app". Signals: intent-filters in the manifest, WebView loading deep-link params, OAuth redirect via a custom scheme.

27 Updated 1 months ago
NoorQureshi
AI & Automation Listed

auditing-mobile-deeplink-trust

Audit how a mobile app handles a deep link, app link, or custom-scheme URL, so an attacker-supplied URL cannot drive a sensitive action or reach a trusted WebView context. Covers a custom scheme any app can register and hijack, an app link whose domain association is unverified so the link is not exclusively the app's, a deep-link parameter that flows unvalidated into a sensitive action, an attacker-controlled URL loaded into a WebView, and a JavaScript bridge exposed to a WebView that can load untrusted content. Use when reviewing deep-link routing, URL handling, and WebView configuration, not the manifest export state of the component that receives the link (that is the component-exposure skill). The attacker-supplied URL is the source, a sensitive action or a trusted WebView bridge acting on it is the sink, and a link parameter trusted without validation is the bug.

27 Updated 2 months ago
UnboundCompute