Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
zhaoxuya520/competition-android-hookingMobile, firmware e hardware

competition-android-hooking

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Android APK hooking, Frida tracing, request-signing recovery, SSL pinning bypass, JNI boundary inspection, and app trust-boundary analysis. Use when the user asks to hook an APK, inspect signer logic, trace Java or nati⁩

v2026.9.22-cab634b3 instalações+3 em 7 dias44,8 mil EstrelasMITsincronizado há 2 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
9aegcYb3a4…dFeeGfDQ==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote76f51ed1…87c91124
76f51ed1fca4…230587c911243 arquivos · ⁦2.1 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-android-hooking@cab634b

Este item ainda não foi escrito no seu idioma, então aparece em 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 an Android app's live trust boundary rather than static strings alone.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Preserve the original APK, extracted resources, and decompiled output before patching or resigning.
  2. Start with manifest, exported components, deeplinks, native libs, prefs, local DBs, and bundled configs.
  3. Decide the narrowest runtime boundary to hook: signer, crypto helper, JNI bridge, WebView bridge, or request builder.
  4. Correlate static evidence and dynamic traces before claiming a trust edge is understood.
  5. Reproduce the signed request, accepted token, or gated branch from the smallest hook set.

Workflow

1. Static Triage Before Hooks

  • Map package structure, exported activities, services, receivers, providers, and deeplink handlers.
  • Note SSL pinning logic, root checks, feature flags, token storage, shared prefs, SQLite tables, and protobuf or RPC boundaries.
  • Identify whether the sensitive logic sits in Java, Kotlin, JNI, or a bundled WebView.

2. Hook The Narrowest Boundary

  • Prefer hooking request signers, crypto helpers, keystore access, protobuf encode or decode, or JNI marshaling instead of broad UI hooks.
  • Record plaintext inputs, signed strings, headers, nonces, and outputs at the boundary that actually changes trust.
  • If pinning or environment checks block progress, patch or hook only enough to expose the real request path.

3. Replay The Accepted Path

  • Rebuild the smallest sequence that reaches the accepted server-side branch: local state, nonce, request body, signature, and headers.
  • Keep hook logs, captured request shapes, and local storage paths tied to the same account or session state.
  • If the challenge becomes more about transform recovery than Android runtime, switch back to the broader crypto or mobile skill.

Read This Reference

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

What To Preserve

  • Hook points, class names, JNI symbols, signer inputs and outputs, and header names
  • Shared prefs, local DB rows, deeplinks, exported components, and token storage paths
  • The smallest replayable request or branch that proves the trust boundary

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.9.22-cab634b13 de nov. de 2026cab634b76f51ed1Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login