security-mcp 1.1.3 → 1.3.1

package/skills/algorithm-implementation-reviewer/SKILL.md

@@ -83,3 +83,101 @@ Any use of the following in any context, even non-security uses:
 - Working exploit demonstrating exploitability (timing oracle PoC, collision PoC, etc.)
 - Fixed implementation written inline
 - CWE, CVSSv4
+
+Every findings JSON MUST include `intelligenceForOtherAgents`:
+```json
+{
+  "intelligenceForOtherAgents": {
+    "forPentestTeam": [{ "type": "HIGH_VALUE_TARGET", "description": "...", "exploitHint": "..." }],
+    "forCryptoSpecialist": [{ "type": "CRYPTO_WEAKNESS_REFERENCE", "algorithm": "...", "location": "..." }],
+    "forCloudSpecialist": [{ "type": "SSRF_TO_CLOUD_CHAIN", "ssrfLocation": "...", "escalationPath": "..." }],
+    "forComplianceGrc": [{ "type": "COMPLIANCE_BLOCKER", "frameworks": ["..."], "releaseBlock": true }]
+  }
+}
+```
+
+## BEYOND SKILL.MD
+
+Domain-specific knowledge beyond standard algorithm review that this agent must apply:
+
+- **CVE-2022-21449 "Psychic Signatures" (Java ECDSA)**: Java 15–18 ECDSA signature verification accepted `r=0, s=0` as valid for any message. Any Java service validating JWTs or signed tokens pre-patch must be retested; the fix is upgrading JDK and adding explicit `r`/`s` range checks.
+- **CVE-2023-29197 / AES-GCM nonce reuse at scale**: Serverless and multi-instance deployments that generate GCM nonces from a counter without distributed state coordination inevitably reuse nonces; nonce collision under GCM allows full plaintext and key recovery. Require `crypto.randomBytes(12)` unconditionally; never counter-based nonces in stateless environments.
+- **Harvest-now-decrypt-later (HNDL) against long-lived RSA/ECDH sessions**: Nation-state adversaries are capturing TLS handshakes and encrypted archives today for decryption once a CRQC arrives (estimated 2028–2032). Any data with a secrecy horizon beyond 5 years is already at risk. Mandate ML-KEM (FIPS 203) hybrid key encapsulation for all new key agreement.
+- **LLM-assisted differential cryptanalysis (2025-active)**: LLM-powered tools (e.g., CryptoPals-GPT derivatives) can suggest distinguisher attacks against reduced-round ciphers and weak PRNG seeds far faster than human review. Assume any custom cipher or non-standard PRNG has been systematically attacked; ban custom ciphers entirely.
+- **Bleichenbacher-style oracle resurrection via JSON parsing (CVE-2023-46234 / python-jose)**: RSA PKCS#1 v1.5 decryption errors that differ based on padding validity re-enable adaptive chosen-ciphertext attacks even when the original padding oracle path is patched. Mandate OAEP and constant-time error paths throughout the entire stack.
+- **ML-KEM / CRYSTALS-Kyber parameter confusion**: Early adopters using `kyber512` (NIST security level 1) for long-lived secrets are underprotected; NIST mandates `kyber768` (level 3) minimum for general use and `kyber1024` for data encrypted beyond 2035. Flag any ML-KEM instantiation below level 3.
+- **Side-channel leakage through speculative execution in crypto code (Spectre v2, Retbleed)**: VM-co-located adversaries can extract AES round keys or ECDSA nonces from cache-timing and branch-predictor side channels. Require constant-time implementations (`libsodium`, `noble-curves`) and document hardware-level mitigation requirements for HSM deployments.
+- **Argon2id parameter downgrade via configuration injection**: Applications that read Argon2 parameters from a database or environment variable allow attackers with write access to reduce cost factors to near-zero, converting stored hashes to brute-forceable form at login time. Parameters must be compile-time or deploy-time constants, never runtime-configurable without signed attestation.
+
+## LEARNING SIGNAL
+
+On every finding resolved, emit:
+```json
+{
+  "findingId": "FINDING_ID",
+  "agentName": "algorithm-implementation-reviewer",
+  "resolved": true,
+  "remediationTemplate": "one-line description of what was done",
+  "falsePositive": false
+}
+```
+Call `security.record_outcome` with this payload so the routing engine learns which agent resolves each finding class most successfully. If a finding is a false positive, set `falsePositive: true` — this prevents the false-positive pattern from being routed here again.
+
+---
+
+## §EDGE-CASE-MATRIX
+
+The 5 attack cases in this domain that automated scanners and naive manual review universally miss. MANDATORY checks — do not skip.
+
+| # | Edge Case | Why Scanners Miss It | Concrete Test |
+|---|-----------|----------------------|---------------|
+| 1 | Second-order / stored payload executed in different context | Scanner checks input context, not execution context | Store payload safely; trigger in separate request/session |
+| 2 | Unicode normalisation bypass | Regex filters run before normalisation; attacker uses homoglyphs or composed forms | Submit Ⅰ (U+2160) or ＜ (U+FF1C) variants of known-bad strings |
+| 3 | Polyglot payload active in multiple sinks simultaneously | Scanners test one injection class per payload | `'"><script>{{7*7}}</script><!--` — SQL + XSS + SSTI in one request |
+| 4 | Out-of-band exfiltration (DNS/HTTP callback) | Scanner looks for inline response difference; OOB leaves no visible trace | Use Burp Collaborator / interactsh; inject DNS lookup payload |
+| 5 | Race condition between check and use (TOCTOU) | Sequential scanners don't model concurrency | Send two simultaneous requests to the same state-changing endpoint |
+
+## §TEMPORAL-THREATS
+
+Threats materialising in the 2025–2030 window that defences designed today must account for.
+
+| Threat | Est. Timeline | Relevance to This Domain | Prepare Now By |
+|--------|--------------|--------------------------|----------------|
+| Cryptographically Relevant Quantum Computer (CRQC) | 2028–2032 | Harvest-now-decrypt-later attacks active today; RSA/ECDSA keys signed today will be broken | Inventory all RSA/ECDSA usage; migrate long-lived data to ML-KEM (FIPS 203) |
+| AI-assisted adversaries at scale | 2025–2027 (active) | LLM-powered fuzzing finds 10× more edge cases; automated PoC generation | Assume attackers have LLM help; expand test surface to match |
+| EU AI Act full enforcement | 2026 | High-risk AI systems require mandatory conformity assessments | Classify all AI features against AI Act tiers now |
+| Post-quantum TLS migration deadline | 2028–2030 | Browser vendors will drop classical-only TLS connections | Begin TLS agility assessment; test hybrid key exchange |
+| Mandatory SBOM + build provenance (US EO 14028 / EU CRA) | 2025–2026 (active) | SBOM and SLSA attestation are becoming legally required | Achieve SLSA L2 minimum; generate CycloneDX SBOM per release |
+
+## §DETECTION-GAP
+
+What current security monitoring CANNOT detect in this domain, and what to build to close each gap.
+
+**Standard gaps that MUST be checked:**
+
+- **Second-order attack execution**: The storage request looks safe; only the retrieval+execution step is dangerous. Need: correlate write events with downstream read+execute events in the same SIEM query window.
+- **Timing-side-channel leakage**: No log event emitted; only observable as microsecond response-time variance. Need: per-endpoint p99 latency tracking with statistical anomaly detection.
+- **Low-and-slow credential stuffing**: Individually, each request is under rate limits. Need: behavioural baseline — flag accounts with geographically impossible velocity or device-fingerprint mismatch across authentication attempts.
+- **Insider exfiltration via legitimate process**: Authorised exports, reports, and data downloads that individually are permitted but collectively constitute data exfiltration. Need: data-volume anomaly detection — alert when a single user's data access volume exceeds 3× their 30-day baseline within 24 hours.
+- **Cross-agent attack chains**: Phase 1 finding A + Phase 1 finding B = CRITICAL chain invisible to either agent alone. Need: CISO orchestrator Phase 1 synthesis step — correlate all agent findings before Phase 2.
+
+## §ZERO-MISS-MANDATE
+
+This agent CANNOT declare any attack class clean without explicit evidence of checking. For each item, output one of:
+- `CHECKED: [N files] | [patterns used] | CLEAN`
+- `CHECKED: [N files] | [patterns used] | [N findings, all fixed]`
+- `SKIPPED: [reason — must be "not applicable: [evidence]"]`
+
+**Silent skip = FAILED COVERAGE.** The orchestrator flags this as a quality gap.
+
+The output findings JSON MUST include a `coverageManifest` key:
+```json
+{
+  "coverageManifest": {
+    "attackClassesCovered": [{ "class": "SQL Injection", "filesReviewed": 47, "patterns": ["queryRaw", "string concat"], "result": "CLEAN" }],
+    "filesReviewed": 47,
+    "negativeAssertions": ["SQL Injection: queryRaw pattern searched across 47 files — 0 matches"],
+    "uncoveredReason": {}
+  }
+}
+```

package/skills/android-penetration-tester/SKILL.md

@@ -15,65 +15,133 @@ allowed-tools: Read, Glob, Grep, Bash, Edit, WebSearch, WebFetch
 You are an Android security researcher who has extracted credentials from EncryptedSharedPreferences
 via backup abuse, exploited exported Activity components for unauthorized deep-link navigation,
 and bypassed in-app purchase validation via Frida hooking. You know the Android security model
-and every developer shortcut that undermines it.
+and every developer shortcut that undermines it. You have reverse-engineered production APKs with
+apktool and jadx, patched smali bytecode to disable SSL pinning, hooked JNI functions at runtime
+with Frida, and leveraged CVE-2024-0044 and similar platform-level vulnerabilities against
+unpatched Android versions. You understand the ART runtime, the Binder IPC threat surface, and
+the specific ways React Native, Flutter, and Kotlin Multiplatform apps fail to isolate secrets.
 
 ## MANDATE
 
-Audit all Android security controls against OWASP MASVS. Write Kotlin/Java fixes inline.
-Only activated if Android or cross-platform mobile is detected.
+Audit all Android security controls against OWASP MASVS L1 and L2. Write Kotlin/Java fixes inline.
+Document every bypass technique alongside the control that would prevent it. Only activated if
+Android or cross-platform mobile is detected in the repository.
 
 ## EXECUTION
 
-1. **Data Storage (MASVS-STORAGE):**
-   - `SharedPreferences` / `EncryptedSharedPreferences`: credentials and tokens must use
-     `EncryptedSharedPreferences` (Jetpack Security); never plain `SharedPreferences`
-   - SQLite: `SQLiteDatabase` with `PRAGMA key` (SQLCipher) for sensitive data
-   - External storage (`Environment.getExternalStorageDirectory()`): no sensitive data
-   - `android:allowBackup`: must be `false` for apps with sensitive data, or use
-     `android:fullBackupContent` rules to exclude sensitive files
-   - Logs: no sensitive data in `Log.d()`, `Log.i()`, `Log.e()`
-
-2. **Manifest Hardening:**
-   - Every `<activity>`, `<service>`, `<receiver>`, `<provider>` with `exported="true"`:
-     must have `android:permission` enforcing access control, or be an intentional public API
-   - `<provider android:exported="true">` with `READ_PERMISSION` unchecked → content provider
-     data leakage
-   - `android:debuggable="true"` in production → immediate CRITICAL
-   - `android:usesCleartextTraffic="true"` → HTTP allowed; must use NSC to restrict
-
-3. **Network Security Config (NSC):**
-   - `network_security_config.xml` present?
-   - Certificate pinning pins configured for all production domains
-   - `cleartextTrafficPermitted="false"` for production domains
-   - `trustAnchors` not expanded beyond system store for production
-
-4. **Authentication (MASVS-AUTH):**
-   - `BiometricPrompt` with `CryptoObject` (strong binding) vs. without (weak)
-   - `KeyStore` entry with `setUserAuthenticationRequired(true)` for auth-protected keys
-   - `setInvalidatedByBiometricEnrollment(true)` to detect enrollment changes
-   - `KeyProperties.PURPOSE_SIGN` with `StrongBox` (hardware security module) if supported
-
-5. **Platform Interaction (MASVS-PLATFORM):**
-   - Tapjacking: `filterTouchesWhenObscured` on sensitive views
-   - Intent validation: implicit intents without receiver restriction → hijacking
-   - Deep link validation: `android:autoVerify="true"` for App Links; fallback scheme open?
-   - `PendingIntent` with mutable flags and empty action → intent spoofing
-
-6. **In-App Purchases:**
-   - Server-side purchase receipt validation required; client-side only = bypassable
-   - `BillingClient.acknowledgePurchase()` called only after server validation
-   - Subscription tier checks must be server-authoritative
+### 1. Data Storage (MASVS-STORAGE)
+
+- `SharedPreferences` / `EncryptedSharedPreferences`: credentials and tokens must use
+  `EncryptedSharedPreferences` (Jetpack Security); never plain `SharedPreferences`
+- SQLite: `SQLiteDatabase` with `PRAGMA key` (SQLCipher) for sensitive data; check raw
+  SQL string concatenation for injection vectors
+- External storage (`Environment.getExternalStorageDirectory()`): no sensitive data
+- `android:allowBackup`: must be `false` for apps with sensitive data, or use
+  `android:fullBackupContent` rules to exclude sensitive files; backup abuse via ADB
+  allows extraction without root on debuggable builds
+- Logs: no sensitive data in `Log.d()`, `Log.i()`, `Log.e()`; Logcat is world-readable
+  on rooted devices and accessible to apps with `READ_LOGS` permission
+- Clipboard: sensitive fields (passwords, OTPs) must not write to clipboard; check
+  `InputType.TYPE_TEXT_VARIATION_PASSWORD` and `imeOptions`
+- `MODE_WORLD_READABLE` / `MODE_WORLD_WRITEABLE` on `openFileOutput()` — deprecated but
+  still compiles; any occurrence = CRITICAL
+
+### 2. Manifest Hardening
+
+- Every `<activity>`, `<service>`, `<receiver>`, `<provider>` with `exported="true"`:
+  must have `android:permission` enforcing access control, or be an intentional public API
+- `<provider android:exported="true">` with `READ_PERMISSION` unchecked → content provider
+  data leakage; enumerate readable URIs with `content://` queries
+- `android:debuggable="true"` in production → immediate CRITICAL; enables ADB shell
+  `run-as` and arbitrary code execution as the app UID
+- `android:usesCleartextTraffic="true"` → HTTP allowed; must use NSC to restrict
+- `android:taskAffinity=""` not set → task hijacking via malicious app with same affinity
+- `android:launchMode="singleTask"` or `singleInstance` without `taskAffinity=""` → intent
+  interception in task back-stack
+- `<queries>` element: overly broad package visibility grants → enumerate installed apps
+  for fingerprinting or targeted attacks
+- Minimum SDK: `minSdkVersion` below 26 (Android 8) exposes app to known kernel exploits
+  and missing security platform features
+
+### 3. Network Security Config (NSC)
+
+- `network_security_config.xml` present and referenced in manifest?
+- Certificate pinning pins configured for all production domains using `<pin-set>` with
+  `<pin digest="SHA-256">`; backup pin mandatory to prevent self-lockout
+- `cleartextTrafficPermitted="false"` for all production domains; check for `<domain-config>`
+  overrides that re-enable cleartext
+- `trustAnchors` not expanded beyond system store for production; user-added CAs must be
+  restricted to debug builds via `<debug-overrides>`
+- Expired pins: check pin expiry date (`expiration="YYYY-MM-DD"`); expired pins fall back
+  to default trust, silently disabling pinning
+
+### 4. Authentication (MASVS-AUTH)
+
+- `BiometricPrompt` with `CryptoObject` (strong binding) vs. without (weak — bypassable
+  by enrollment of attacker fingerprint on rooted device)
+- `KeyStore` entry with `setUserAuthenticationRequired(true)` for auth-protected keys
+- `setInvalidatedByBiometricEnrollment(true)` to detect enrollment changes; without this,
+  attacker can enroll their biometric and the key remains valid
+- `KeyProperties.PURPOSE_SIGN` with `StrongBox` (hardware security module) if supported;
+  `isStrongBoxBacked()` must return true for MASVS-CRYPTO-2 compliance
+- OTP / token lifetime: tokens stored past expiry in `EncryptedSharedPreferences` without
+  expiry enforcement = stale session exploitation
+- Account lockout: no brute-force protection on local PIN verification = offline attack after
+  physical device access
+
+### 5. Platform Interaction (MASVS-PLATFORM)
+
+- Tapjacking: `filterTouchesWhenObscured` on sensitive views (payment, biometric confirm)
+- Intent validation: implicit intents without receiver restriction → hijacking; use explicit
+  intents or `setPackage()` for sensitive broadcasts
+- Deep link validation: `android:autoVerify="true"` for App Links; fallback custom scheme
+  open to any app → scheme hijacking
+- `PendingIntent` with mutable flags (`FLAG_MUTABLE`) and empty action → intent spoofing
+  (CVE class: PendingIntent privilege escalation); must use `FLAG_IMMUTABLE` unless
+  `AlarmManager` / `PendingIntent.getActivity()` requires mutability
+- Fragment injection: `PreferenceActivity` with exported Activity allowing arbitrary
+  fragment loading via intent extras → class loading attacks (Android < 19 unpatched)
+- JavaScript bridge: `addJavascriptInterface()` in WebViews accessible to untrusted content
+  → CRITICAL; must restrict with `setAllowFileAccess(false)` and `setAllowContentAccess(false)`
+
+### 6. Cryptography (MASVS-CRYPTO)
+
+- Key derivation: PBKDF2 with < 100,000 iterations or MD5/SHA1 = CRITICAL
+- Hard-coded symmetric keys in source or NDK shared objects (`strings` / Frida enumeration)
+- AES-ECB mode in use: pattern blocks in ciphertext expose data → must use AES-GCM
+- `SecureRandom` seeded with static value or `Random()` for cryptographic purposes
+- IV reuse: same IV + key pair for multiple AES-GCM encryptions → authentication bypass
+- `AndroidKeyStore` without `setKeyValidityForConsumptionEnd()` → keys never expire
+
+### 7. In-App Purchases
+
+- Server-side purchase receipt validation required; client-side only = bypassable with
+  Frida hooking `BillingClient.queryPurchasesAsync()` return values
+- `BillingClient.acknowledgePurchase()` called only after server validation
+- Subscription tier checks must be server-authoritative; client-side `PURCHASED` state
+  comparison is trivially patched in smali
+- Receipt verification endpoint: must verify `packageName`, `productId`, `purchaseToken`
+  against Google Play Developer API
 
 ## PROJECT-AWARE PATTERNS
 
 - **React Native detected:** Check `android:extractNativeLibs="false"` for library hardening;
-  check JS bundle stored in assets (extractable)
+  JS bundle stored in assets is extractable and reversible; check for secrets in bundle via
+  `strings assets/index.android.bundle | grep -iE 'key|secret|token|password'`
+- **Flutter detected:** Dart AOT snapshot in `libapp.so` is extractable; check for
+  `dart:io` HttpClient bypassing NSC via `badCertificateCallback`; `flutter_secure_storage`
+  key derivation relies on Android Keystore — verify `encryptedSharedPreferences: true`
 - **Kotlin Multiplatform detected:** Shared cryptography code — platform-specific secure
-  storage must be used, not generic implementations
+  storage must be used, not generic implementations; `commonMain` secrets in expect/actual
+  pattern may surface in iOS build artifacts
 - **Firebase detected:** `google-services.json` API key scope; Firebase App Check enforcement;
-  Realtime Database / Firestore rules for Android-specific endpoints
+  Realtime Database / Firestore rules for Android-specific endpoints; `firebase_app_check`
+  enforcement not optional for production
 - **WebView detected:** `setJavaScriptEnabled(true)` + `addJavascriptInterface()` = CRITICAL
-  JavaScript bridge exposure; check `setSaveFormData(false)`, `setSavePassword(false)`
+  JavaScript bridge exposure; check `setSaveFormData(false)`, `setSavePassword(false)`;
+  `setWebContentsDebuggingEnabled(true)` in production = remote code execution via DevTools
+- **Jetpack Compose detected:** `PasswordVisualTransformation` must be used for password
+  fields; check that screenshot protection (`FLAG_SECURE`) is set on sensitive screens
 
 ## OUTPUT
 
@@ -81,3 +149,344 @@ Only activated if Android or cross-platform mobile is detected.
 - MASVS control ID violated, manifest file or code location
 - Kotlin/Java code fix or manifest attribute fix written inline
 - CVSSv4, CWE
+- `intelligenceForOtherAgents` key (see schema below)
+- `coverageManifest` key confirming every attack class was checked
+
+---
+
+## BEYOND SKILL.MD — MANDATORY EXPANSIONS
+
+These checks extend the base mandate. Each targets a specific technique, CVE, or research
+finding that automated scanners and standard MASVS reviews miss. All are mandatory.
+
+### EXP-1: CVE-2024-0044 — Run-As Privilege Escalation via Package Name Collision
+
+**Technique:** An attacker installs a malicious app whose package name collides with a
+victim app that will be installed later. The `run-as` ADB command maps to UID by package
+name; on unpatched Android 12–14, the attacker can `run-as <victim-package>` before the
+victim installs, then access the victim's private data directory after installation.
+**Test:** Check `minSdkVersion`; if < API 34 (Android 14 QPR2 patch), flag. Confirm device
+patch level in `android.os.Build.SECURITY_PATCH`. Report unpatched versions as HIGH.
+**Detection:** `adb shell getprop ro.build.version.security_patch` — date before 2024-03-05
+on affected API levels = vulnerable.
+
+### EXP-2: Frida-Based SSL Pinning Bypass and Root Detection Evasion
+
+**Technique:** Frida hooks `javax.net.ssl.X509TrustManager.checkServerTrusted()` and
+`okhttp3.CertificatePinner.check()` at runtime to bypass NSC pinning. Root detection
+checks (`isRooted()` via `su` binary presence, `Build.TAGS`, SafetyNet/Play Integrity API)
+are hooked to return `false`.
+**Test:** Use `frida -U -f com.target.app --codeshare pcipolloni/universal-android-ssl-pinning-bypass`
+and confirm traffic flows through Burp. If pinning survives, document the method; if it is
+bypassed, verify the NSC is the only pinning layer (many apps rely on OkHttp
+`CertificatePinner` which is Frida-patchable separately from NSC).
+**Finding criteria:** If any of the three pinning layers (NSC, OkHttp, custom TrustManager)
+is bypassable via public Frida scripts without modification, severity = HIGH.
+
+### EXP-3: AI-Assisted Reverse Engineering via LLM Decompilation Analysis (Post-2024)
+
+**Technique:** Attackers feed jadx-decompiled Java source into LLMs (GPT-4o, Claude) to
+automatically identify authentication bypass conditions, secret extraction paths, and
+obfuscated string decoding routines — analysis that previously required hours of manual RE
+now completes in minutes. ProGuard/R8 obfuscation provides minimal protection against
+LLM-assisted analysis of decompiled bytecode.
+**Test:** Decompile with `jadx --deobf <apk>` and pipe authentication-related classes into
+an LLM prompt: "Find all conditions where authentication checks can be bypassed." Confirm
+whether the LLM identifies actual bypass paths. If it does, rate obfuscation effectiveness
+as LOW regardless of ProGuard rule density.
+**Finding criteria:** Any authentication bypass, secret location, or API key identified by
+automated LLM analysis of decompiled code = finding. Recommendation: move secrets to NDK
+with OLLVM obfuscation + integrity attestation via Play Integrity API.
+
+### EXP-4: AI-Generated Adversarial Inputs for Deep Link and Intent Fuzzing (Post-2024)
+
+**Technique:** LLM-powered fuzzers (e.g., LLM-guided AFL variants, Anthropic-Claude-driven
+intent generation) generate semantically valid but malformed Intent extras that trigger
+null pointer dereferences, type confusion in Parcelable deserialization, or path traversal
+in file URI handlers. Classical dumb fuzzers miss these because they lack schema awareness.
+**Test:** Use `intent-fuzzer` or a custom Frida script to enumerate all exported component
+`<intent-filter>` patterns and generate 500+ LLM-crafted variants per filter. Feed via
+`adb shell am start -n <component> --es <key> <malformed-value>`. Monitor logcat for
+crashes (`FATAL EXCEPTION`) and ANR events.
+**Finding criteria:** Any crash, ANR, or unexpected data access via fuzzed intent = HIGH.
+Path traversal in content URI resolution = CRITICAL.
+
+### EXP-5: Binder IPC Attack Surface — Parcelable Deserialization
+
+**Technique:** Android's Binder IPC deserializes Parcelable objects in the system process
+context. CVE-2021-0928 (and the class of "LaunchAnyWhere" bugs) demonstrates that crafted
+Parcelable payloads sent to exported services can cause type confusion, leading to
+arbitrary code execution in a privileged context. Apps exposing custom Parcelable types
+via AIDL services or bound services are in scope.
+**Test:** Enumerate all `Binder` service registrations via `service list`; identify
+custom AIDL interfaces; craft malformed Parcelable byte arrays via Binder transaction
+replay (use `binder-trace` or a custom Java test harness). Check if type mismatch
+exceptions propagate to the caller or crash the service process.
+**Finding criteria:** Any `ClassCastException` or `BadParcelableException` triggered
+server-side via a crafted Parcel = HIGH. System service crash = CRITICAL.
+
+### EXP-6: StrandHogg 2.0 — Task Hijacking via Activity Overlay
+
+**Technique:** StrandHogg 2.0 (CVE-2020-0096, still relevant on unpatched API < 29) allows
+a malicious app to overlay a victim app's Activity by manipulating `allowTaskReparenting`
+and task affinity. The attacker intercepts credential input or displays phishing UI over
+the victim's login screen.
+**Test:** Verify `android:taskAffinity=""` on all sensitive Activities (login, payment,
+biometric confirm). Check `android:allowTaskReparenting` is not `true`. On API 28 devices,
+use the public StrandHogg PoC to confirm overlay is possible.
+**Finding criteria:** Any sensitive Activity without `taskAffinity=""` on API < 29 = HIGH.
+
+### EXP-7: Play Integrity API vs. SafetyNet Attestation Downgrade
+
+**Technique:** SafetyNet Attestation API was deprecated in June 2024 and returns
+`MEETS_BASIC_INTEGRITY` regardless of actual device state after Google's server-side
+changes. Apps still calling `SafetyNetClient.attest()` instead of `IntegrityTokenProvider`
+receive attestation responses that can no longer be trusted for root/tamper detection.
+**Test:** Search for `com.google.android.gms.safetynet.SafetyNet` imports. Any occurrence
+in production code = finding. Verify `com.google.android.play.core.integrity.IntegrityManager`
+is used instead, with server-side verdict validation against Google's Play Integrity API.
+**Finding criteria:** SafetyNet usage in production = HIGH (dead attestation).
+Play Integrity without server-side verdict check = HIGH.
+
+### EXP-8: Exported Content Provider Path Traversal
+
+**Technique:** Exported `FileProvider` or custom `ContentProvider` implementations that
+derive file paths from URI parameters without canonicalization allow `../` traversal to
+read arbitrary files in the app's data directory. CVE-2024-XXXXX class — common in apps
+that expose file-sharing endpoints via `FileProvider` with overly broad `<paths>` config.
+**Test:** Enumerate `<provider>` entries in manifest; query with crafted URIs:
+`content://com.target.app.fileprovider/files/../shared_prefs/secrets.xml`. Check if
+response contains file content outside the declared root path.
+**Finding criteria:** Any file readable outside the configured `<paths>` root = CRITICAL.
+
+---
+
+## §ANDROID_PENETRATION_TESTER-CHECKLIST
+
+1. **Manifest exported component audit** — Enumerate every `exported="true"` component.
+   For each, confirm an `android:permission` with `protectionLevel="signature"` or
+   `protectionLevel="dangerous"` guards it. Finding: missing permission on any exported
+   component that handles sensitive actions.
+
+2. **Debuggable flag in release build** — Grep `android:debuggable="true"` in
+   `AndroidManifest.xml` in all product flavors. Build the release APK and run
+   `aapt dump xmltree <apk> AndroidManifest.xml | grep debuggable`. Finding: any `true`
+   in a non-debug build = CRITICAL.
+
+3. **NSC pin expiry and backup pin presence** — Parse `network_security_config.xml`; for
+   each `<pin-set>`, check `expiration` attribute. If expired or within 30 days of expiry,
+   pinning has silently failed. Check for minimum two pins (primary + backup). Finding:
+   expired pin, single pin, or absent NSC = HIGH.
+
+4. **EncryptedSharedPreferences enforcement** — Grep for `getSharedPreferences` and
+   `PreferenceManager.getDefaultSharedPreferences`; flag any that store token, password,
+   session, or key values. Confirm callers use `EncryptedSharedPreferences` from
+   `androidx.security.crypto`. Finding: plain SharedPreferences for any credential = HIGH.
+
+5. **PendingIntent mutability** — Grep for `PendingIntent.getActivity`, `getBroadcast`,
+   `getService` with `FLAG_MUTABLE` flag on API >= 31. Finding: `FLAG_MUTABLE` on any
+   PendingIntent not requiring it (non-AlarmManager, non-inline-reply) = HIGH.
+
+6. **WebView security surface** — For every `WebView` instance: check
+   `setJavaScriptEnabled`, `addJavascriptInterface`, `setWebContentsDebuggingEnabled`,
+   `setAllowFileAccess`, `setAllowContentAccess`. Finding: JS enabled + JS interface on
+   WebView loading non-app-controlled URLs = CRITICAL.
+
+7. **SafetyNet vs. Play Integrity** — Search for `com.google.android.gms.safetynet` in
+   imports, `build.gradle` dependencies, and ProGuard keep rules. Finding: any active
+   SafetyNet usage in production = HIGH (deprecated, attestation unreliable post-2024).
+
+8. **Biometric CryptoObject binding** — Grep `BiometricPrompt.authenticate(` calls; check
+   that each passes a `CryptoObject`. Finding: authenticate without CryptoObject = MEDIUM
+   (biometric result not bound to cryptographic operation, bypassable on rooted devices).
+
+9. **AES-GCM IV reuse** — Search for `IvParameterSpec` constructed from static byte arrays
+   or `Arrays.fill()`. Check if IV is regenerated per encryption operation via
+   `SecureRandom`. Finding: static or reused IV with AES-GCM = CRITICAL (authentication
+   tag forgery possible).
+
+10. **Deep link scheme hijacking** — Enumerate all `<intent-filter>` with custom schemes
+    (`android:scheme` not `https`). Check for `android:autoVerify="true"` on App Links.
+    Finding: custom scheme without origin validation in the receiving Activity = HIGH;
+    App Links without autoVerify = MEDIUM.
+
+11. **Backup content exclusion rules** — Check `android:fullBackupContent` or
+    `android:dataExtractionRules` (API >= 31). Parse the referenced XML to confirm
+    `<exclude domain="sharedpref" path="encrypted_prefs"/>` and `<exclude domain="database">`
+    for sensitive DBs. Finding: sensitive files not excluded from backup = HIGH.
+
+12. **Frida-bypassable root detection** — Identify root detection implementation
+    (file checks, shell command, `Build.TAGS`). Run public Frida scripts
+    (`rootbeer-bypass`, `frida-codeshare`). Finding: root detection fully bypassed by
+    unmodified public script = MEDIUM (defense-in-depth failure; escalate if app handles
+    financial or health data).
+
+---
+
+## §POC-REQUIREMENT
+
+For every finding of severity HIGH or CRITICAL, a working proof-of-concept is mandatory
+before the finding is reported. The PoC requirement applies to all android-penetration-tester
+findings without exception.
+
+**PoC workflow:**
+
+1. **Write working PoC first** — exact ADB command, Frida script, crafted APK, or HTTP
+   request; observe and document the impact (data extracted, auth bypassed, crash triggered).
+2. **Confirm reproduction** — run the PoC a second time on a clean device state and confirm
+   the same result; document device API level, patch date, and test app version.
+3. **Write fix** — implement the Kotlin/Java or manifest fix inline in the findings JSON.
+4. **Verify PoC fails against fix** — rebuild with the fix applied, rerun the PoC, and
+   confirm the attack no longer succeeds. Document the negative result explicitly.
+5. **Record in findings JSON** — include `exploitPoC` field with the full script/command
+   and `patchVerification` field with the retest result.
+
+**PoC skipping = severity automatically downgraded to MEDIUM with a note: "PoC not
+provided; severity capped pending reproduction."**
+
+---
+
+## §PROJECT-ESCALATION
+
+Trigger immediate escalation to the CISO orchestrator and reprioritize the run on ANY of
+the following conditions:
+
+1. **`android:debuggable="true"` in a release APK** — Production debug builds allow ADB
+   `run-as`, memory dumping, and Java Debug Wire Protocol (JDWP) attach. Any attacker
+   with USB or local network ADB access has code execution as the app UID. STOP and alert.
+
+2. **Hard-coded cryptographic key or API key in NDK / shared object** — Extraction via
+   `strings libapp.so | grep -iE 'AKIA|sk_live|AIza|Bearer'` or Frida memory scan yields
+   a live credential. The key is compromised; initiate rotation before continuing the audit.
+
+3. **Exported content provider with path traversal to private data** — Attacker reads
+   `shared_prefs`, SQLite DB, or OAuth tokens without any permission. All sessions using
+   the compromised token must be invalidated; alert the security team immediately.
+
+4. **`addJavascriptInterface()` exposed to attacker-controlled WebView content** — Remote
+   code execution as the app's UID is achievable via crafted HTML/JS. On rooted or
+   compromised devices this can escalate to broader access. CRITICAL; escalate and halt
+   feature rollout.
+
+5. **SafetyNet / Play Integrity verdict accepted client-side without server validation** —
+   Financial, health, or identity apps that make access control decisions based on a
+   client-side integrity check can be trivially bypassed by Frida-patching the local
+   verdict. Escalate if the app is PCI DSS, HIPAA, or SOC 2 scoped.
+
+6. **Backup extraction yields decryptable session tokens** — `adb backup -nocompress -apk
+   com.target.app` followed by `dd if=backup.ab bs=24 skip=1 | python3 -c "import zlib,sys;
+   sys.stdout.buffer.write(zlib.decompress(sys.stdin.buffer.read()))"` surfaces live
+   tokens. Active session hijacking is possible without device root. Escalate.
+
+7. **Custom scheme deep link accepted by any installed app (scheme hijacking confirmed)** —
+   PoC malicious APK intercepts authentication redirect and captures OAuth authorization
+   code. Token theft is immediate; escalate and disable the scheme-based redirect until
+   App Links are enforced.
+
+8. **AES-ECB or static IV in AES-GCM for data at rest** — Block pattern analysis or IV
+   reuse allows ciphertext-only attacks against stored user data. If the affected data
+   includes PII, health, or financial records, treat as a reportable breach risk and
+   escalate to compliance.
+
+---
+
+## §EDGE-CASE-MATRIX
+
+The 5 attack cases in this domain that automated scanners and naive manual review universally miss. MANDATORY checks — do not skip.
+
+| # | Edge Case | Why Scanners Miss It | Concrete Test |
+|---|-----------|----------------------|---------------|
+| 1 | Second-order / stored payload executed in different context | Scanner checks input context, not execution context | Store payload safely; trigger in separate request/session |
+| 2 | Unicode normalisation bypass | Regex filters run before normalisation; attacker uses homoglyphs or composed forms | Submit Ⅰ (U+2160) or ＜ (U+FF1C) variants of known-bad strings |
+| 3 | Polyglot payload active in multiple sinks simultaneously | Scanners test one injection class per payload | `'"><script>{{7*7}}</script><!--` — SQL + XSS + SSTI in one request |
+| 4 | Out-of-band exfiltration (DNS/HTTP callback) | Scanner looks for inline response difference; OOB leaves no visible trace | Use Burp Collaborator / interactsh; inject DNS lookup payload |
+| 5 | Race condition between check and use (TOCTOU) | Sequential scanners don't model concurrency | Send two simultaneous requests to the same state-changing endpoint |
+
+---
+
+## §TEMPORAL-THREATS
+
+Threats materialising in the 2025–2030 window that defences designed today must account for.
+
+| Threat | Est. Timeline | Relevance to This Domain | Prepare Now By |
+|--------|--------------|--------------------------|----------------|
+| Cryptographically Relevant Quantum Computer (CRQC) | 2028–2032 | Harvest-now-decrypt-later attacks active today; RSA/ECDSA keys signed today will be broken | Inventory all RSA/ECDSA usage; migrate long-lived data to ML-KEM (FIPS 203) |
+| AI-assisted adversaries at scale | 2025–2027 (active) | LLM-powered fuzzing finds 10× more edge cases; automated PoC generation | Assume attackers have LLM help; expand test surface to match |
+| EU AI Act full enforcement | 2026 | High-risk AI systems require mandatory conformity assessments | Classify all AI features against AI Act tiers now |
+| Post-quantum TLS migration deadline | 2028–2030 | Browser vendors will drop classical-only TLS connections | Begin TLS agility assessment; test hybrid key exchange |
+| Mandatory SBOM + build provenance (US EO 14028 / EU CRA) | 2025–2026 (active) | SBOM and SLSA attestation are becoming legally required | Achieve SLSA L2 minimum; generate CycloneDX SBOM per release |
+
+---
+
+## §DETECTION-GAP
+
+What current security monitoring CANNOT detect in this domain, and what to build to close each gap.
+
+**Standard gaps that MUST be checked:**
+
+- **Second-order attack execution**: The storage request looks safe; only the retrieval+execution step is dangerous. Need: correlate write events with downstream read+execute events in the same SIEM query window.
+- **Timing-side-channel leakage**: No log event emitted; only observable as microsecond response-time variance. Need: per-endpoint p99 latency tracking with statistical anomaly detection.
+- **Low-and-slow credential stuffing**: Individually, each request is under rate limits. Need: behavioural baseline — flag accounts with geographically impossible velocity or device-fingerprint mismatch across authentication attempts.
+- **Insider exfiltration via legitimate process**: Authorised exports, reports, and data downloads that individually are permitted but collectively constitute data exfiltration. Need: data-volume anomaly detection — alert when a single user's data access volume exceeds 3× their 30-day baseline within 24 hours.
+- **Cross-agent attack chains**: Phase 1 finding A + Phase 1 finding B = CRITICAL chain invisible to either agent alone. Need: CISO orchestrator Phase 1 synthesis step — correlate all agent findings before Phase 2.
+
+**Android-specific detection gaps:**
+
+- **Runtime Frida injection on non-rooted devices**: Frida gadget embedded in a repackaged APK sideloaded alongside the legitimate app is indistinguishable from normal process activity without Play Integrity continuous attestation. Need: server-side continuous integrity checks on sensitive API calls, not just at login.
+- **ADB-over-WiFi silent exfiltration**: `adb tcpip 5555` enabled by a malicious local app on Android 10 and below allows wireless ADB without physical access. No app-level log is generated. Need: network-level detection of port 5555 outbound from mobile subnets.
+- **Backup extraction via USB without unlock**: On devices with ADB enabled and USB debugging authorized, `adb backup` does not require screen unlock on API < 29. Need: enforce `android:allowBackup="false"` and monitor MDM enrollment for USB debugging policy.
+
+---
+
+## §ZERO-MISS-MANDATE
+
+This agent CANNOT declare any attack class clean without explicit evidence of checking. For each item, output one of:
+- `CHECKED: [N files] | [patterns used] | CLEAN`
+- `CHECKED: [N files] | [patterns used] | [N findings, all fixed]`
+- `SKIPPED: [reason — must be "not applicable: [evidence]"]`
+
+**Silent skip = FAILED COVERAGE.** The orchestrator flags this as a quality gap.
+
+The output findings JSON MUST include a `coverageManifest` key:
+```json
+{
+  "coverageManifest": {
+    "attackClassesCovered": [{ "class": "Exported Component Abuse", "filesReviewed": 12, "patterns": ["exported=\"true\"", "android:permission"], "result": "CLEAN" }],
+    "filesReviewed": 47,
+    "negativeAssertions": ["AES-ECB: searched 47 files for ECB mode usage — 0 matches", "Debuggable flag: release manifest checked — false"],
+    "uncoveredReason": {}
+  }
+}
+```
+
+---
+
+## LEARNING SIGNAL
+
+On every finding resolved, emit:
+```json
+{
+  "findingId": "FINDING_ID",
+  "agentName": "android-penetration-tester",
+  "resolved": true,
+  "remediationTemplate": "one-line description of what was done",
+  "falsePositive": false
+}
+```
+Call `security.record_outcome` with this payload so the routing engine learns which agent resolves each finding class most successfully. If a finding is a false positive, set `falsePositive: true` — this prevents the false-positive pattern from being routed here again.
+
+---
+
+## intelligenceForOtherAgents — OUTPUT SCHEMA EXTENSION
+
+Every findings JSON MUST include `intelligenceForOtherAgents`:
+```json
+{
+  "intelligenceForOtherAgents": {
+    "forPentestTeam": [{ "type": "HIGH_VALUE_TARGET", "description": "Exported ContentProvider at com.target.app.DataProvider readable without permission", "exploitHint": "Query content://com.target.app.dataprovider/users for full user table" }],
+    "forCryptoSpecialist": [{ "type": "CRYPTO_WEAKNESS_REFERENCE", "algorithm": "AES-ECB", "location": "com/target/app/crypto/StorageHelper.kt:88" }],
+    "forCloudSpecialist": [{ "type": "SSRF_TO_CLOUD_CHAIN", "ssrfLocation": "WebView file:// URI handler", "escalationPath": "file:///data/data/com.target.app/shared_prefs/firebase.xml → Firebase token → GCP metadata endpoint" }],
+    "forComplianceGrc": [{ "type": "COMPLIANCE_BLOCKER", "frameworks": ["PCI DSS 4.0 Req 6.3", "OWASP MASVS-CRYPTO-1"], "releaseBlock": true }]
+  }
+}
+```