Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
zhaoxuya520/competition-ios-runtimeMobile, firmware e hardware

competition-ios-runtime

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for IPA runtime analysis, Frida hooks, Objective-C or Swift method tracing, Keychain inspection, SSL pinning bypass, URL scheme handling, and iOS request-signing recovery. Use when the user asks to hook an IPA, trace Object⁩

v2026.9.22-cab634b3 installazioni+3 in 7 giorni44,8K StelleMITsincronizzato 2 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-ios-runtime

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
ItGcNX+8ni…1kqCcrCg==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettoeafe0a86…916e5363
eafe0a86568a…0e41916e53633 file · ⁦2.1 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-ios-runtime@cab634b

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive path runs through live iOS trust boundaries rather than static strings or plist values alone.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Preserve the original IPA, extracted bundle, and any decrypted or re-signed copy as separate artifacts.
  2. Start with Info.plist, entitlements, URL schemes, frameworks, Keychain usage, and local app storage before broad runtime hooks.
  3. Choose the narrowest runtime boundary that proves behavior: signer, trust evaluator, Keychain accessor, Objective-C or Swift method, or network request builder.
  4. Correlate static bundle evidence and live hook output before claiming the trust path is understood.
  5. Reproduce the accepted request, token, or gated branch from the smallest hook set.

Workflow

1. Static iOS Triage

  • Map bundle structure, Info.plist, entitlements, URL schemes, universal links, embedded frameworks, and app group paths.
  • Record likely trust boundaries: request signers, device binding, certificate checks, jailbreak checks, Keychain access, or local cache loading.
  • Note whether sensitive logic sits in Objective-C, Swift, embedded frameworks, or a bundled web surface.

2. Hook The Runtime Boundary

  • Prefer hooking request builders, crypto helpers, trust evaluators, Keychain reads, or Objective-C selectors instead of broad UI handlers.
  • Record plaintext inputs, headers, nonces, signed strings, and outputs at the boundary that changes server acceptance.
  • Patch or bypass pinning or environment checks only enough to expose the real request path.

3. Replay The Accepted Path

  • Rebuild the smallest stateful sequence: local token, device identifier, request body, signature, headers, and trust checks.
  • Keep hook logs, bundle paths, plist keys, and local storage artifacts tied to the same session or account state.
  • If the task becomes mostly about transform recovery instead of iOS runtime, switch back to the broader crypto or mobile skill.

Read This Reference

  • Load references/ios-runtime.md for hook targets, storage checklist, and evidence packaging.

What To Preserve

  • Bundle paths, entitlements, plist keys, selectors, class names, hook points, and header names
  • Keychain items, local DB or plist paths, URL schemes, and app-group storage locations
  • The smallest replayable request or branch that proves the iOS trust boundary

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.9.22-cab634b13 nov 2026cab634beafe0a86Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login