SecureBlockLog in
All servicesMobile Testing

iOS & Android penetration testing from binary to backend.

Static decompilation, runtime hooking with Frida, local data exposure, certificate pinning bypass, and full API security review — every layer of your mobile attack surface.

OWASP MASVS alignediOS & Android coverageBackend API included
What we test

Full coverage, tested by hand.

Every assessment is led by an OSCP- or CREST-certified tester — not a scanner with a human proofreading the output.

Static binary analysis

Decompile the app binary to identify hardcoded secrets, API keys, sensitive string literals, and insecure configurations embedded at build time.

Runtime instrumentation

Hook live app behaviour with Frida to inspect memory, bypass SSL pinning, tamper with business logic, and intercept sensitive function calls at runtime.

Local storage & keychain review

Review all data persisted on-device: SharedPreferences, SQLite databases, NSUserDefaults, the iOS Keychain, and insecure file permissions.

Backend API assessment

The app's backend API is tested with full authentication context — same rigour as our standalone API assessment, included at no extra charge.

Methodology

How we run the engagement.

A structured process that ends with a report you can hand directly to your auditor.

1
Setup & extraction

Obtain the app binary (or build from source), set up test devices, and establish a proxy for traffic interception.

2
Static analysis

Decompile and analyse the binary for secrets, insecure configs, debug flags, and exported components.

3
Dynamic testing

Runtime instrumentation, traffic analysis, deeplink fuzzing, and intent injection across the full app workflow.

4
Backend validation

Replay and tamper API calls with full auth context to identify broken authorization, mass assignment, and data leakage.

Sample findings

The kind of issues we find.

Real finding types from past engagements — titles and targets anonymised.

criticalCVSS 8.8SB-M-001
Hardcoded production AWS credentials in app binary
com.acme.app — MainActivity.smaliDay 1
Remediation — Remove all credentials from client-side code. Use short-lived tokens dispensed by a backend credential vending service.
highCVSS 7.1SB-M-002
Sensitive PII stored unencrypted in SQLite database
/data/data/com.acme.app/databases/userdata.dbDay 2
Remediation — Encrypt the database with SQLCipher or store only non-sensitive identifiers locally, retrieving sensitive data on demand from the backend.
mediumCVSS 5.3SB-M-003
Certificate pinning bypass via Frida hook
iOS — TrustKit implementationDay 3
Remediation — Add runtime integrity checks and jailbreak/root detection in addition to pinning; consider using a hardened SDK wrapper.
FAQ

Questions about this service.

Still unsure? Ask an engineer in chat — not a sales rep.

No. We can test from the compiled binary (IPA/APK). Source code helps us go deeper and is welcome if available.

Know where you stand before your auditor does.