mobile-pentest
Audited by Socket on Sep 23, 2026
8 alerts found:
Securityx5Anomalyx3SUSPICIOUS. The skill is internally consistent with its stated purpose, but that purpose is to give an AI agent offensive mobile exploitation capability: bypassing protections, extracting secrets, and abusing components on real apps/devices. There is no clear credential-harvesting or deceptive exfiltration behavior, so this is not confirmed malware, but it is a high-risk exploit/pentest skill for an autonomous agent.
The fragment documents intentionally offensive Android instrumentation techniques that enable TLS interception, certificate-pinning bypass, and concealment of root or Frida indicators. It presents substantial security risk if used against applications without authorization, but the visible content is not evidence of malware such as credential theft, persistence, exfiltration, or destructive behavior. The assessment is limited to the supplied fragment and does not infer hidden behavior from omitted code.
The fragment is a reverse-engineering and mobile application instrumentation guide. It contains actionable TLS-pinning bypass, transparent traffic interception, bytecode patching, and runtime code-injection techniques. These are high-impact capabilities but are presented for security testing and do not themselves demonstrate malware or data theft. It should be used only with authorization and in controlled environments.
The code is an explicit Android penetration-testing/fuzzing harness rather than malware. It intentionally sends potentially harmful test inputs and can modify provider data through content insert when --no-write is omitted. The main security concern is operational misuse and possible shell-injection exposure if surface.json is untrusted, not credential theft or covert malicious behavior. Use only against authorized test devices and treat the surface JSON as trusted or validate/escape its values.
This is a root-only Android testing utility intended to inject a custom CA into Zygote's mount namespace. It contains no evident malware, credential theft, network exfiltration, persistence outside the running watcher, or destructive behavior beyond replacing the effective trust-store view. However, it materially weakens TLS trust for all applications inheriting the modified namespace, and its unescaped positional arguments create a command-injection risk when invoked with attacker-controlled certificate names or paths. It should be restricted to authorized rooted test devices and updated to pass arguments safely without shell interpolation.
This is an intentional Android runtime security-bypass script, commonly used with Frida for application testing, traffic interception, or reverse engineering. It materially weakens TLS certificate validation, hostname validation, WebView SSL handling, and root/instrumentation detection. It does not show evidence of data theft, persistence, destructive behavior, or network exfiltration, so malware likelihood is low; however, executing it against an application creates a high security risk because it accepts untrusted certificates and conceals a potentially compromised analysis environment.
The content is a readable iOS penetration-testing reference with a Frida jailbreak-detection bypass script and commands for privileged access, decryption, and sensitive-data extraction. It does not show clear malware or supply-chain sabotage, and it contains no automatic persistence or exfiltration behavior. Security risk is moderate because misuse or poor handling could expose credentials, application data, and decrypted proprietary binaries; the default SSH credential and stealth-oriented Frida guidance require strict authorization and operational controls.
The code is a deliberate Frida-based iOS security-bypass and instrumentation script. It disables jailbreak detection, bypasses TLS certificate pinning, defeats a common biometric authentication flow, and logs keychain queries. It does not itself exfiltrate data or establish persistence, but its purpose is unauthorized runtime tampering and it can materially weaken application security and expose sensitive keychain-related information.