A workflow for examining JavaScript in a real browser to find where login data, API requests, form fields, or responses are encrypted or signed. It then produces code and connection documentation for using that logic elsewhere.
A six-stage workflow for authorized security analysis of Android apps using decompiled code, captured network traffic, and native libraries such as JNI or SO files.
A mobile-app security agent for the first round of static inspection of an unpacked or decompiled Android app. Static inspection examines files and code without running the app.
A mobile-app reverse-engineering analysis role that links captured requests, request fields, signatures, authentication data, and code locations. Reverse engineering here means examining local app code and traffic to understand how they correspond.
A mobile reverse-engineering agent for analyzing native cryptography code, JNI bridges, and shared-library logic. JNI is the interface that lets Java or Kotlin code call native code, while a shared library is compiled code such as an Android .so file.
A security-analysis agent that checks code for weak encryption and other high-risk vulnerabilities, then records how much evidence supports each finding.
A reporting assistant for mobile-security testing that gathers results from several earlier testing phases into a structured report. It preserves findings, evidence, severity levels, and reproduction details.