ios-pentest
Audited by Socket on Sep 15, 2026
11 alerts found:
Securityx6Anomalyx5SUSPICIOUS. The skill is internally coherent for iOS pentesting, but it grants an AI agent high-risk offensive security capabilities, sensitive data extraction paths, and remote device file transfer. It is not confirmed malware, yet it should be treated as high-risk due to exploit-tooling scope and unpinned third-party execution guidance.
The code is a readable Frida crypto-hooking/debugging script. It is designed to inspect cryptographic operations and intentionally exposes keys, plaintext, decrypted data, and other sensitive buffers through console logging. This creates a substantial information-disclosure risk in production or untrusted instrumentation environments, but the fragment itself shows no malware indicators such as network exfiltration, persistence, command execution, sabotage, or obfuscation. Use should be restricted to authorized testing with sensitive logs protected.
The code is a purpose-built Frida jailbreak-detection bypass script. It intentionally falsifies filesystem, URL, process, command-execution, and dynamic-library observations to conceal jailbreak and instrumentation artifacts. It does not exhibit package malware indicators such as data theft, network exfiltration, persistence, cryptomining, or system damage, but it is intrusive instrumentation code and can undermine application security checks when injected into a target process.
This is a Frida-based iOS Keychain monitoring script. It is consistent with authorized reverse engineering, debugging, or security testing, and contains no clear malware indicators such as network exfiltration, persistence, credential transmission, or system damage. Its principal security concern is intentional disclosure of Keychain contents and queries through console logging; it should only be used on authorized devices and applications.
This is a Frida instrumentation script intended to bypass iOS TLS certificate pinning and certificate-trust validation. It is clearly dual-use for authorized testing, debugging, or reverse engineering, but it materially weakens transport security in the attached process and could enable interception of otherwise protected HTTPS traffic. The fragment shows no evidence of malware such as exfiltration, persistence, system damage, or credential harvesting; the primary risk is deliberate security-control circumvention.
This is a dual-use Frida instrumentation reference for authorized iOS security testing. It does not contain evident malware, exfiltration, persistence, or destructive behavior. Its main risks are intentional observation of sensitive data and an explicit biometric-authentication bypass example. Use only against applications and devices for which testing authorization exists, and protect or discard captured console output.
This is an explicit Frida instrumentation script for bypassing iOS biometric authentication and biometric-protected keychain access. It is highly security-impacting because it defeats application authentication controls, but it does not itself exhibit typical package malware behavior such as theft, exfiltration, persistence, or system damage. Its acceptability depends on authorized testing; use against an application without authorization would be an access-control bypass.
The fragment is a security-testing workflow for bypassing iOS SSL pinning and inspecting HTTPS traffic. It contains no evident malware or supply-chain payload, but it intentionally weakens TLS authentication and can expose sensitive traffic when used against a target application. Use should be limited to authorized testing environments and applications.
This is security-testing documentation for instrumenting iOS applications and bypassing anti-debugging, jailbreak detection, and TLS certificate pinning. It contains no evident malware, credential theft, persistence, or exfiltration behavior. Its operational guidance presents a moderate security risk if used against applications or devices without authorization.
The supplied text is a jailbreak-detection and anti-debugging bypass guide. It is not itself executable malware and contains no evident data theft or destructive behavior, but it directly enables security-control evasion and application tampering. Use should be limited to authorized testing of applications and devices.
This is a security assessment blueprint for extracting and evaluating iOS Keychain protections. It contains no clear malware or supply-chain backdoor behavior, but it performs highly sensitive credential access and writes raw dump output to a file. It should only be used on authorized targets, with strict handling, redaction, retention, and deletion controls for the dump and findings.