mirror of
https://codeberg.org/reverse-skill-lab/apk-reverse
synced 2026-11-16 18:04:23 +08:00
Adds docs/tool-verification/fixtures/verify_absorbed_claims.py: seven device-free checks covering the mask identity, the PKCS#7 length law, zero-fill versus skipped offsets, the hidden-salt search, compression drift, Python percent-encoding, and AES CTR/CBC/ECB separation. The AES run falsified an absorbed claim: zero prefix-XOR does not imply a stream cipher (CBC and ECB show it too). The discriminator is a one-byte flip -- 1 changed byte for CTR, all following blocks for CBC, one block for ECB -- and protocol-reverse section 7 now states that, with the capability row recording the correction. Labels are now per claim rather than per section: observed where a host command produced output, inferred for rules derived from the mechanisms, unverified for anything needing a device, a JDK, a lz4 binding or a VM sample. native-vm-recovery's claim-strength paragraph is aligned with the repository definition, and the cipher row moves to inferred. Gates and pytest green.
1050 lines
61 KiB
JSON
1050 lines
61 KiB
JSON
{
|
|
"schema": "apk-reverse/capability-matrix",
|
|
"version": 1,
|
|
"purpose": "One machine-readable row per capability this skill claims: how strong the claim is, whether the route itself was ever measured, where the evidence lives inside an installed copy, and what the claim does not cover. An installed copy of this skill must be able to answer 'is this proven, how strongly, and where' without the repository it was extracted from.",
|
|
"read_with": "references/evidence-summary.md (the prose condensation of this file, and the only place that lists the non-shipped record)",
|
|
"status_labels": {
|
|
"ok": "The documented route was carried out on a real target and the result is recorded.",
|
|
"partial": "Part of the route was measured; at least one decisive step (usually install, launch, or a second independent producer) was not.",
|
|
"blocked": "Either the route depends on something this skill does not ship, or nothing in this record is evidence about it either way. Do not treat 'blocked' as 'impossible' -- treat it as 'no footing here'."
|
|
},
|
|
"strength_labels": {
|
|
"observed": "A command was run and its output exists behind the claim.",
|
|
"inferred": "Follows from a documented mechanism or a neighbouring measurement; the step itself was not executed.",
|
|
"unverified": "Assumed, or reported by someone else, and not reproduced in this record.",
|
|
"unknown": "Nothing here covers it: not probed, or probed without the coverage to answer. Missing evidence, never a negative result -- do not read an `unknown` row as 'absent' or 'safe'."
|
|
},
|
|
"evidence_rules": [
|
|
"Every path in `evidence` is relative to the installed skill root and resolves in an installed copy.",
|
|
"Paths in `evidence_not_shipped` sit at the repository root, which `npx skills add` does not install. Every one of them is marked 'repository root, not shipped'.",
|
|
"Rows are traceable to an existing evidence file or to a row of the repository's benchmark matrix (B1-B13). Nothing here was written from expectation.",
|
|
"Where a source document and a script disagree, the script's behaviour was taken as the measurement and the row says so."
|
|
],
|
|
"capabilities": [
|
|
{
|
|
"capability": "dex-equal-length-surgical-patch",
|
|
"group": "dex",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B1"
|
|
],
|
|
"evidence": [
|
|
"references/byte-level-patching.md",
|
|
"references/dex-patching.md",
|
|
"references/patch-audit.md",
|
|
"scripts/dex_patch_bytes.py",
|
|
"scripts/dex_find_insn.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-benchmark-l1-l3.md section 2 (repository root, not shipped)",
|
|
"tests/benchmark.md row B1 (repository root, not shipped)"
|
|
],
|
|
"limits": "Equal-length edits only. The end-to-end measurement is one 2-byte branch rewrite inside a 5,528-byte dex, whose whole-file diff is those 4 bytes plus dex header bytes 8..32; the patched file self-verifies. Constraints that cannot be expressed as an equal-length edit need the dexlib2 route, which has no public-target measurement."
|
|
},
|
|
{
|
|
"capability": "dex-method-level-rewrite-dexlib2",
|
|
"group": "dex",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/dex-patching.md",
|
|
"references/patch-audit.md",
|
|
"scripts/dexpatch/"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/README.md (repository root, not shipped)"
|
|
],
|
|
"limits": "The rewriter and the smali round-trip tools (scripts/smtool.py, scripts/patch_smali.py) carry no measurement against a public target in this record. The round-trip blind spot is documented: a whole-tree smali round trip can pass every table check and still crash with IncompatibleClassChangeError. Treat the route as documented, not proven."
|
|
},
|
|
{
|
|
"capability": "dex-header-integrity-and-verifier-legality",
|
|
"group": "dex",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B1"
|
|
],
|
|
"evidence": [
|
|
"references/patch-audit.md",
|
|
"references/byte-level-patching.md",
|
|
"scripts/dexutil.py",
|
|
"scripts/dex_check_verifier.py",
|
|
"scripts/dex_classdiff.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"tests/benchmark.md row B1 (repository root, not shipped)"
|
|
],
|
|
"limits": "Header recompute order (adler32 over d[12:], sha1 over d[32:]) is proven on one written file, which reproduces both fields. Passing scripts/dex_classdiff.py is necessary, not sufficient: it cannot detect code-item damage, and the checks that look further (instruction-length audit, the equal-length blind spot, move-result adjacency) live in references/patch-audit.md."
|
|
},
|
|
{
|
|
"capability": "dex-string-constant-patch",
|
|
"group": "dex",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/byte-level-patching.md",
|
|
"references/dex-patching.md",
|
|
"scripts/dex_strpatch.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/TOOL-VERDICTS.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Equal-length only: the shipped scripts/dex_strpatch.py enforces equal length and refuses a substring of a longer identifier. A different-length string edit is therefore not covered by that script; it needs the dexlib2 route, whose build is documented and unmeasured. No public-target measurement for the string path."
|
|
},
|
|
{
|
|
"capability": "repack-sign-install-single-apk",
|
|
"group": "packaging",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B1",
|
|
"B9"
|
|
],
|
|
"evidence": [
|
|
"references/repack-and-sign.md",
|
|
"references/verification.md",
|
|
"scripts/repack.py",
|
|
"scripts/install_test.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-benchmark-l1-l3.md section 2 (repository root, not shipped)",
|
|
"tests/benchmark.md rows B1 and B9 (repository root, not shipped)"
|
|
],
|
|
"limits": "Measured chain on this class of host: zip, then zipalign -p -f 4, then apksigner.jar --v1 --v2 --v3; the order cannot be reversed (the installer refuses with [-124]). B1 confirms installability by matching the on-device base.apk sha256 against the local build, and its control build through the identical pipeline still fails the old way. Signing has no uber-apk-signer here. The isolated-constant rewrite script writes an APK through a different code path whose zip-metadata and alignment handling was recorded as a defect; that path is not covered by this row."
|
|
},
|
|
{
|
|
"capability": "split-apk-and-app-bundle-sets",
|
|
"group": "packaging",
|
|
"status": "partial",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B9"
|
|
],
|
|
"evidence": [
|
|
"references/split-apk.md",
|
|
"scripts/repack.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-split-apk.md (repository root, not shipped)",
|
|
"tests/benchmark.md row B9 (repository root, not shipped)"
|
|
],
|
|
"limits": "Analyze, unified re-sign and merge were run on two real sets: after resign every member shares one certificate with v1+v2+v3 true, and merge correctly refuses (exit 1, before writing) a set whose members carry their own resources.arsc while succeeding on the code/native-only set. adb install-multiple and launch confirmation were NOT executed, so installability of a re-signed set is unverified, and the split mode's install path is exactly where a wrong alignment hides."
|
|
},
|
|
{
|
|
"capability": "third-party-build-audit",
|
|
"group": "packaging",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/third-party-builds.md",
|
|
"scripts/apk_diff.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/README.md (repository root, not shipped)"
|
|
],
|
|
"limits": "scripts/apk_diff.py is listed among the scripts the first verification pass never ran, and no benchmark row exercises it. Absence from that record is not a verdict on it, but nothing here supports trusting its output either."
|
|
},
|
|
{
|
|
"capability": "extraction-shell-detection-trivial-body",
|
|
"group": "unpacking",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B3"
|
|
],
|
|
"evidence": [
|
|
"references/advanced-unpacking.md",
|
|
"scripts/dex_dump_validate.py",
|
|
"scripts/dex_mem_scan.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-extraction-shell-bench.md (repository root, not shipped)",
|
|
"tests/benchmark.md row B3 (repository root, not shipped)"
|
|
],
|
|
"limits": "The ratio is bimodal, not thresholded: a real skeleton reads about 100 percent, a zero-change control 1.9 percent, nop-cleared bodies 0.0 percent and throw stubs 1.9 percent, so the shapes real shells use are invisible to it. The earlier 'tens of percent means a skeleton' rule was wrong and was deleted. Measured on an 11-variant synthetic set derived from one real dex, not on a live extraction shell, and three script defects were found by that set."
|
|
},
|
|
{
|
|
"capability": "dex-vmp-declaration-boundary",
|
|
"group": "unpacking",
|
|
"status": "partial",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B4"
|
|
],
|
|
"evidence": [
|
|
"references/advanced-unpacking.md",
|
|
"references/code-virtualization-and-custom-linkers.md",
|
|
"references/vmp-differential-analysis.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-extraction-shell-bench.md section 3.4 and section 4 (repository root, not shipped)",
|
|
"tests/benchmark.md row B4 (repository root, not shipped)"
|
|
],
|
|
"limits": "Static criteria can rule a dex-VMP out; they cannot rule runtime-applied hardening out. Never declare a VMP without an official disassembler's failure count: a hand-written opcode table reported 1,393 of 22,424 bodies as undecodable and produced a VMP verdict on a sample that the platform decoder showed to be ordinary dalvik with zero structural errors. Install, launch and refusal for that sample remain untested."
|
|
},
|
|
{
|
|
"capability": "vmp-differential-opcode-map",
|
|
"group": "unpacking",
|
|
"status": "partial",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/vmp-differential-analysis.md",
|
|
"scripts/vmp_diff_harness.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-vmp-diff.md (repository root, not shipped)"
|
|
],
|
|
"limits": "The fixture covers 218 of 224 opcodes and the closed loop re-derived that table exactly: 218 of 218 emitted opcodes, zero wrong entries, zero fabricated entries. What was not exercised is the other half of the premise -- no third-party hardening platform was contacted, and the assumption that a real engine substitutes per opcode at stable instruction length is inferred from public write-ups. No benchmark row covers this route."
|
|
},
|
|
{
|
|
"capability": "java2c-vs-jni-sinking-discrimination",
|
|
"group": "native",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B5",
|
|
"B11"
|
|
],
|
|
"evidence": [
|
|
"references/java2c-and-jni-sinking.md",
|
|
"scripts/java2c_probe.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-java2c.md (repository root, not shipped)",
|
|
"tests/benchmark.md rows B5 and B11 (repository root, not shipped)"
|
|
],
|
|
"limits": "The discriminating measurement is observed: native-declaration density separates the shapes by roughly 2000x (0.03-0.04 percent on three real JNI samples against 82.76 percent on a Java2C-shaped fixture), and Java_* symbols matched dex native-method counts 1:1 per ABI. No Dex-to-C compiler output was ever built here (no NDK, no host or device clang), so every Java2C-specific criterion is inferred. A symbol search fails silently on real Java2C: dcc emits -fvisibility=hidden and C++ jni.h inlines RegisterNatives."
|
|
},
|
|
{
|
|
"capability": "native-terminate-path-neutralisation",
|
|
"group": "native",
|
|
"status": "partial",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B2"
|
|
],
|
|
"evidence": [
|
|
"references/native-tamper-and-suicide.md",
|
|
"references/native-and-so.md",
|
|
"scripts/spawn_patch_detach.py",
|
|
"scripts/hook_patch_only.js"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-benchmark-l1-l3.md section 3 (repository root, not shipped)",
|
|
"tests/benchmark.md row B2 (repository root, not shipped)"
|
|
],
|
|
"limits": "The tooling works; the patch does not. Writes landed 0.04-0.05 s after resume and survived detach, and the patched run and a read-and-write-back control both still died with SIGABRT at the same site: neutralising the terminate routine plus both of its branch inputs was insufficient, and the region is a dense cluster of mov w0,#imm ; ret stubs. Holding the process paused until the patch lands structurally cannot work, because a frozen process has no libraries mapped. On that target the pristine original already reports tamper, so no clean baseline exists there. No surviving-target result is claimed. Site selection is a separate claim: the predicate-first rule and the tiered grading (added 2026-10-25) are absorbed from a write-up and unverified here -- no graded patch set was run, and the ordering judgement is inferred."
|
|
},
|
|
{
|
|
"capability": "native-instruction-tracing-stalker",
|
|
"group": "native",
|
|
"status": "partial",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B6"
|
|
],
|
|
"evidence": [
|
|
"references/native-dbi-and-deobfuscation.md",
|
|
"scripts/stalker_trace.js",
|
|
"scripts/stalker_report.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-stalker-exclude.md (repository root, not shipped)",
|
|
"tests/benchmark.md row B6 (repository root, not shipped)"
|
|
],
|
|
"limits": "Split result: following a hot libc export with no exclusions kills the process, and excluding 20 system modules keeps it alive -- but delivery is still zero events (blocks=0 blk=0 calls=0). Exclusion is therefore not the fix for a trace that reports nothing, which contradicts the framing that lists 'no events' among the symptoms exclusion addresses. Two harness traps that manufacture a false zero-event result were fixed in the same pass. No real OLLVM trace was produced, and no trace pipeline is verified on the test device."
|
|
},
|
|
{
|
|
"capability": "native-library-mapping-and-plt-resolution",
|
|
"group": "native",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/native-and-so.md",
|
|
"references/toolchain.md",
|
|
"scripts/lib_map.py",
|
|
"scripts/elf_plt.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/TOOL-VERDICTS.md (repository root, not shipped)"
|
|
],
|
|
"limits": "scripts/lib_map.py is verified on a real target. scripts/elf_plt.py was broken and fixed: one defect was proven to cause a false negative on a symbol that exists and is called, and a second compared a file offset against a virtual address under --diff --name-regions. Run it before patching any stub, and treat its 'no callers' answer as a claim about its own input parsing until you have seen it scan something you know references the symbol."
|
|
},
|
|
{
|
|
"capability": "native-crash-triage-and-swallowed-stacks",
|
|
"group": "native",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/native-tamper-and-suicide.md",
|
|
"references/environment.md",
|
|
"scripts/native_crash.py",
|
|
"scripts/grab_crash.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/TOOL-VERDICTS.md (repository root, not shipped)"
|
|
],
|
|
"limits": "scripts/native_crash.py was recorded as 'not applicable to this sample' in the first pass, and scripts/grab_crash.py was never run -- including on the one target whose crash-reporter SDK hid exactly the stack it claims to recover, so that claim is unverified rather than wrong. The general rule that survives without a measurement is narrower: a process that dies with only 'uncaughtException time: ...' and no stack has crashed."
|
|
},
|
|
{
|
|
"capability": "runtime-analysis-with-frida",
|
|
"group": "runtime",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B2",
|
|
"B6",
|
|
"B13"
|
|
],
|
|
"evidence": [
|
|
"references/dynamic-frida.md",
|
|
"references/environment.md",
|
|
"references/native-tamper-and-suicide.md",
|
|
"scripts/run_probe.py",
|
|
"scripts/frida_probe.js",
|
|
"scripts/preflight.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-device-run.md (repository root, not shipped)",
|
|
"tests/benchmark.md rows B2, B6 and B13 (repository root, not shipped)"
|
|
],
|
|
"limits": "Instrumentation is itself a measured variable. Attaching is what kills some targets (the probe arm of B13 dies about 300 ms after resume while the no-script control stays alive); exclusion is what keeps others alive (B6); and a spawn ordering that holds the process paused cannot work, because no libraries are mapped yet (B2). Reading a device's refusal as a fact about the target is the failure mode this row exists to prevent -- the preflight check comes before blaming a patch."
|
|
},
|
|
{
|
|
"capability": "runtime-data-local-state",
|
|
"group": "runtime",
|
|
"status": "partial",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B8"
|
|
],
|
|
"evidence": [
|
|
"references/runtime-data.md",
|
|
"scripts/datastore_inject.py",
|
|
"scripts/blob_decode.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"tests/benchmark.md row B8 (repository root, not shipped)"
|
|
],
|
|
"limits": "The DataStore encode/decode path is proven on one real 81-byte container: an edited value re-encoded (81 to 80 bytes, length prefix recomputed) was read back by the injector. SharedPreferences and SQLite edits have no equivalent measurement here, and an edit that keeps reverting is a routing signal -- something else owns the value -- not a data-editing problem."
|
|
},
|
|
{
|
|
"capability": "anti-instrumentation-triage-naming-the-check",
|
|
"group": "runtime",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B13"
|
|
],
|
|
"evidence": [
|
|
"references/detection-and-anti-analysis.md",
|
|
"scripts/anti_detect_probe.js"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-detection-pipeline.md sections 1, 4 and 5 (repository root, not shipped)",
|
|
"tests/benchmark.md row B13 (repository root, not shipped)"
|
|
],
|
|
"limits": "The check was named and the asymmetry recorded: strstr(\"frida\") fired at 303 ms of process life, then the process was gone with no tombstone, no crash and no ANR record, while the probe's own self-report showed TracerPid=0 with four frida-named mappings visible in /proc/self/maps. Reproducibility is honestly bounded: 3 same-shape arms, 1 delivered the full sequence, because a target that dies in about 300 ms leaves a sub-second window. The probe is observer-only by contract and patches nothing."
|
|
},
|
|
{
|
|
"capability": "emulation-and-frida-rpc",
|
|
"group": "runtime",
|
|
"status": "partial",
|
|
"route_measured": true,
|
|
"strength": "inferred",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/emulation-and-rpc.md",
|
|
"scripts/frida_rpc_serve.py",
|
|
"scripts/rpc_template.js"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-emulation-rpc.md (repository root, not shipped)"
|
|
],
|
|
"limits": "The rpc.exports bridge was exercised end to end on a live device and the indexer pair (droidasc / ddc) was measured on a hardened APK, but the reference classifies the route itself as inferred: emulated execution costs environment-filling work, the unidbg build needed repair before it ran, and no target .so had been emulated at the time of writing. The tool was measured; the route was not."
|
|
},
|
|
{
|
|
"capability": "schemaless-protobuf-decode",
|
|
"group": "protocol",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B8"
|
|
],
|
|
"evidence": [
|
|
"references/protocol-reverse.md",
|
|
"scripts/protobuf_decode_raw.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-protobuf-raw.md (repository root, not shipped)",
|
|
"tests/benchmark.md row B8 (repository root, not shipped)"
|
|
],
|
|
"limits": "26 of 26 built-in fixtures, 21 of 21 against the official runtime (re-encode byte-identical to SerializeToString()), 8 of 8 framing checks. Two ambiguities are inherent to the wire format rather than defects: 0801120178 is a valid nested message and a valid packed array, and a non-presence 0 is byte-identical to 'never assigned'. Four script defects were found by these checks and fixed."
|
|
},
|
|
{
|
|
"capability": "server-api-probing-and-tls-feature-scope",
|
|
"group": "protocol",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "inferred",
|
|
"benchmark_rows": [
|
|
"B7"
|
|
],
|
|
"evidence": [
|
|
"references/server-api.md",
|
|
"references/tls-and-cert.md",
|
|
"references/protocol-reverse.md",
|
|
"scripts/probe_api.py",
|
|
"scripts/tls_check.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"tests/benchmark.md row B7 (repository root, not shipped)"
|
|
],
|
|
"limits": "Client-scoped by design: this determines who owns a gate, not how to break an authorization the server performs. The native-side certificate-pinning row (a Cronet sample) was not run -- it needs a gradle+NDK build this class of host cannot do -- and QUIC/HTTP3 is stated as a limit rather than a route. Certificates and pinning are asserted from documented behaviour, so label a feature-scoped TLS failure as inferred until you have reproduced the failure yourself."
|
|
},
|
|
{
|
|
"capability": "dart-aot-analysis-given-a-snapshot-dump",
|
|
"group": "dart",
|
|
"status": "partial",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/dart-aot.md",
|
|
"scripts/dart_disasm.py",
|
|
"scripts/dart_pprefs.py",
|
|
"scripts/dart_pool_strings.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/TOOL-VERDICTS.md (repository root, not shipped)",
|
|
"docs/tool-verification/EXTENSION-dart-aot-formats.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Measured on a real Dart 3.6.0 build: the disassembler decoded identically to capstone (32 of 32 and 96 of 96), the caller index was re-derived independently with a symmetric difference of 0, and a specific business-logic site was located end to end. This row assumes a snapshot dump already exists -- producing one is a separate, blocked capability (see dart-aot-snapshot-dump-production)."
|
|
},
|
|
{
|
|
"capability": "dart-aot-string-table-format",
|
|
"group": "dart",
|
|
"status": "partial",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B12"
|
|
],
|
|
"evidence": [
|
|
"references/dart-aot.md",
|
|
"scripts/dart_pool_strings.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-dart-aot-formats.md (repository root, not shipped)",
|
|
"tests/benchmark.md row B12 (repository root, not shipped)"
|
|
],
|
|
"limits": "Two claims were tested and both were wrong before this row. The arm64 packed form is confirmed at the byte level (tag byte equals 0x80|(len<<1) at every literal checked, 4,980 chained entries). The previously documented armv7 form (len*2 plus UTF-16) is refuted: the 32-bit record is [header u32][byte-count u32le][UTF-8 payload], and the extractor's zero for that ABI is a format mismatch rather than an empty table. An end-to-end patched build was never repacked and installed, so no device patch is claimed. A third claim, that the engine banner gives x.y.z (stable), is also refuted on that target."
|
|
},
|
|
{
|
|
"capability": "dart-aot-snapshot-dump-production",
|
|
"group": "dart",
|
|
"status": "blocked",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/dart-aot.md",
|
|
"references/coverage-and-limits.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/README.md (repository root, not shipped)"
|
|
],
|
|
"limits": "This skill ships no snapshot container resolver and cannot synthesize one, so the Dart AOT workflow cannot start from an APK alone. The two offset spaces are not a constant offset apart: dart_pool_strings.py reports file offsets while the pool index speaks pool offsets, and a measured run found 4,237 distinct deltas over 4,241 shared strings. Ship a pinned front end (aotopsy, pure Go, no toolchain) or build blutter (about 80 s, needs a C++ toolchain) -- and say which one, because the two report different Dart version labels for the same binary."
|
|
},
|
|
{
|
|
"capability": "packer-custom-loader-identification",
|
|
"group": "hardening",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/packers.md",
|
|
"references/code-virtualization-and-custom-linkers.md",
|
|
"references/coverage-and-limits.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/TOOL-VERDICTS.md (repository root, not shipped)",
|
|
"docs/tool-verification/README.md (repository root, not shipped)"
|
|
],
|
|
"limits": "The first verification pass did not exercise the packer, code-virtualization, custom-linker, integrity-check-redirection or tamper-suicide scenarios: its target has none of them, and its unmodified build already fails to start, which removes the repack-and-regress loop those scenarios need. The packer tooling was recorded as 'not applicable to this sample'. Nothing in the record is evidence either way about a protected target -- the benchmark pass measured shape discrimination only."
|
|
},
|
|
{
|
|
"capability": "module-delivery-instead-of-repack-lsposed",
|
|
"group": "hardening",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "inferred",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/lsposed-and-modules.md",
|
|
"scripts/lsposed_scaffold.py",
|
|
"references/precedents/logd-broken-module-never-ran-case-3.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-lsposed.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Documented route, not a measured one: the generated project was built end to end with the gradle-free chain and its timings recorded, but the delivery route itself -- a module standing in for a refused repack -- has no public-target measurement. It needs a device with an active LSPosed, and confirming that a module actually ran takes more than one log surface; a logcat-only check has already produced one confidently wrong conclusion here."
|
|
},
|
|
{
|
|
"capability": "kernel-side-syscall-answer-forging",
|
|
"group": "kernel",
|
|
"status": "blocked",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [
|
|
"B10"
|
|
],
|
|
"evidence": [
|
|
"references/kernel-and-environment-hardening.md",
|
|
"scripts/kernelsu_syscall_mask.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-kernel-weapons.md (repository root, not shipped)",
|
|
"tests/benchmark.md row B10 (repository root, not shipped)"
|
|
],
|
|
"limits": "The generator is measured -- an 11-file userspace module skeleton plus KPM/LKM/eBPF templates, with verify reporting 0 problems -- but no kernel-side artefact was compiled or loaded: the test kernel is 4.14.186 (eBPF needs 5.10+), the host has no aarch64 cross-compiler, make or ndk-build, and there is no kernel source. Structural correction with teeth: an ordinary KernelSU module is a userspace module and cannot change a syscall return value, so a template that claims to do so is wrong regardless of the toolchain."
|
|
},
|
|
{
|
|
"capability": "svc-site-scanning",
|
|
"group": "kernel",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B13"
|
|
],
|
|
"evidence": [
|
|
"references/kernel-and-environment-hardening.md",
|
|
"scripts/svc_scan.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-detection-pipeline.md section 5 (repository root, not shipped)",
|
|
"tests/benchmark.md row B13 (repository root, not shipped)"
|
|
],
|
|
"limits": "Two independent decoders (a hand-written word scan and a capstone-based scan) returned an identical 214-site set on a device linker64, with an empty set difference, which is what makes the output usable as evidence about a library rather than about the scanner. A byte scan also matches data, so neighbour context decides whether a site is code: the hardened shell library's 21 svc sites are all data, and an ordinary module cannot act on them."
|
|
},
|
|
{
|
|
"capability": "on-device-tooling-mt-manager",
|
|
"group": "device",
|
|
"status": "partial",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/on-device-tooling.md",
|
|
"scripts/mt_mcp_probe.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-kernel-ondevice.md (repository root, not shipped)"
|
|
],
|
|
"limits": "The 'service is down' path is measured: the probe prints start-it-by-hand instructions and exits 2. The connected path needs MT Manager's APK MCP started by hand, so it is documented rather than measured, and the MCP surface itself was inventoried from the tool's own listing rather than exercised against a target."
|
|
},
|
|
{
|
|
"capability": "client-side-ads-and-server-issued-ui-config",
|
|
"group": "deliverable",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [
|
|
"B1"
|
|
],
|
|
"evidence": [
|
|
"references/ad-removal.md",
|
|
"references/server-config-and-updates.md",
|
|
"references/membership-and-limits.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/TOOL-VERDICTS.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Verified on a real mid-size Flutter-AOT-shaped target and its ad chain, where the dex reader was the primary workhorse of the analysis and a repacked build's on-screen behaviour change was confirmed. A splash, popup or tab set that arrives as server-issued UI config is a routing decision, not an SDK hunt, and the deliverable is the check that stops it, not the string that names it."
|
|
},
|
|
{
|
|
"capability": "membership-paywall-gate-client-enforceability-decision",
|
|
"group": "deliverable",
|
|
"status": "ok",
|
|
"route_measured": false,
|
|
"strength": "inferred",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/membership-and-limits.md",
|
|
"references/account-gates.md",
|
|
"references/handoff-boundaries.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/README.md (repository root, not shipped)"
|
|
],
|
|
"limits": "The decision framework is documented and its purpose is to say plainly when a gate is not client-enforceable; no gate-shaped public target was put through it in this record, so the framework is itself inferred rather than measured. A gate the server enforces is out of scope by design (see blocked-server-side-authority), and promising an unlock before classifying the owning layer is the specific failure this row prevents."
|
|
},
|
|
{
|
|
"capability": "update-and-forced-upgrade-neutralisation",
|
|
"group": "deliverable",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "inferred",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/updates-and-forced-upgrade.md",
|
|
"references/signature-derived-keys.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/README.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Documented route with no public-target measurement in this record. The shape to expect is not a crash: a rebuilt build installs, runs, and fails every signed request, so a version check and a signature-derived key must be classified before the artifact is called finished. This is an every-deliverable concern, not an optional one."
|
|
},
|
|
{
|
|
"capability": "publishing-sanitisation-leak-scan",
|
|
"group": "governance",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/desensitization-and-leak-scans.md",
|
|
"scripts/scan_leaks.py",
|
|
"references/precedents/manual-grep-finds-what-nobody-grepped-case-5.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-desensitization.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Measured against a planted corpus (30 findings across 6 categories, every rule firing, zero false positives on the do-not-anonymize list) and against this repository (26 strong hits, all inside its own evidence file, reduced to 0 strong and 4 weak across 129 files after correction). One thing it cannot do: the scanner was never run against the pre-correction historical tree, so 'the scan would have caught it' is inferred. A strong hit is a prompt to look, not a verdict, and over-redaction is the failure on the other side."
|
|
},
|
|
{
|
|
"capability": "signature-derived-keys",
|
|
"group": "deliverable",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/signature-derived-keys.md",
|
|
"scripts/sig_probe.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/README.md (repository root, not shipped)"
|
|
],
|
|
"limits": "The offline candidate path from an APK and the authoritative live read are both documented in the reference; neither has a public-target measurement here. The failure shape is a rebuilt APK that installs, launches, and then fails every signed request, which is easy to report as a server problem and is not one. A second variant -- a certificate-derived salt concatenated inside the digest, invisible to any black-box search -- is documented from the same 2026-10-25 write-up and likewise unmeasured."
|
|
},
|
|
{
|
|
"capability": "blocked-react-native-ios",
|
|
"group": "boundary",
|
|
"status": "blocked",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/framework-runtimes.md",
|
|
"references/coverage-and-limits.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/README.md (repository root, not shipped)"
|
|
],
|
|
"limits": "React Native / Hermes bytecode and Cordova internals, and every iOS or .ipa workflow, are outside this skill. references/framework-runtimes.md identifies the runtime and establishes that the dex is not the battlefield; it carries no Hermes-bytecode recipe and no iOS tooling. Say so instead of improvising. Unity is no longer in this row: its documented route is the unity-il2cpp-logic-recovery row, which is a route and not a measurement."
|
|
},
|
|
{
|
|
"capability": "unity-il2cpp-logic-recovery",
|
|
"group": "runtime",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/unity-runtime.md",
|
|
"references/framework-runtimes.md",
|
|
"references/il2cpp-protected-metadata.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"ref/unity1.md .. ref/unity12.md -- public Unity/IL2CPP reverse-engineering write-ups (2024-2026), methodology absorbed, no text copied"
|
|
],
|
|
"limits": "Absorbed, never run here: no Unity package was dumped and no patched Mono runtime was built in this record. What is documented: Mono versus IL2CPP identification by shipped files, Il2CppDumper over libil2cpp.so + global-metadata.dat with the metadata magic (0xFAB11BAF) as the encryption check, the four-step IDA import order (ida_py3.py, script.json, stringliteral.json, ida_with_struct_py3.py), a frida-il2cpp-bridge lookup for a run-time or encrypted case, and the dnSpy-Unity-mono patch set that makes a retail Mono player accept a debugger. Unverified details: the exact dnSpy patch hunks, the Android libmono.so equivalent (inferred from a desktop-only source), whether the loader prefers an on-disk .so on a hardened build, and every tool's behaviour on a stripped or protected package. No opcode or offset claim is made here. The protected-metadata and memory-dump half moved to the il2cpp-protected-metadata-recovery row; this row covers the readable case."
|
|
},
|
|
{
|
|
"capability": "il2cpp-protected-metadata-recovery",
|
|
"group": "runtime",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/il2cpp-protected-metadata.md",
|
|
"references/unity-runtime.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"ref/unity1.md, ref/unity2.md, ref/unity3.md, ref/unity4.md, ref/unity5.md, ref/unity6.md, ref/unity8.md, ref/unity10.md, ref/unity12.md -- public Unity/IL2CPP write-ups (2024-2026), methodology absorbed, no text copied",
|
|
"docs/tool-verification/EXTENSION-ref-absorption-2026-10.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Absorbed, never run here: no metadata was decrypted and no libil2cpp.so was dumped in this record. Covered as a route: deciding between absent, 0-byte, encrypted and embedded metadata; anchoring on the consumer's return pointer (MetadataLoader::LoadMetadataFile or GlobalMetadata::Initialize) instead of the path; the 0x10C descending-by-8 header sizing rule; repeating-key XOR (i & 0x7F), a custom-magic bytecode-VM container, XXTEA with a trailing length word, and length-derived string ciphers; dumping the second mapping and repairing p_offset/p_filesz/e_shoff/e_shstrndx/sh_offset; and treating the metadata version as a claim when the struct layout disagrees. Every offset and magic beyond 0xFAB11BAF belongs to one cited sample and is not a constant."
|
|
},
|
|
{
|
|
"capability": "linker-level-so-unpacking",
|
|
"group": "native",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/linker-and-soinfo-repair.md",
|
|
"references/code-virtualization-and-custom-linkers.md",
|
|
"references/advanced-unpacking.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"ref/so1.md, ref/so2.md, ref/so4.md -- public Android linker and SO-packing write-ups (Android 5.0/8.x source review plus a Frida cookbook), methodology absorbed, no text copied",
|
|
"docs/tool-verification/EXTENSION-ref-absorption-2026-10.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Source-reading synthesis plus a Frida cookbook, not a measurement: no loader was reimplemented and no protected .so was dumped here. The route covers the dlopen pipeline as a loader specification, load_size/load_bias, seg_page_offset when loading from memory, DT_HASH and DT_GNU_HASH layouts, RELATIVE/GLOB_DAT/JUMP_SLOT/IRELATIVE targets and the defining-library-versus-caller bias, APS2 packed relocations, the minimal soinfo repair set, anti-dump header XOR detected by ELF invariants, and the dump window at LoadSegments. soinfo offsets cited in the sources are Android-version-specific; resolving solist by symbol and taking layout from the matching AOSP tag is the durable form. Timing (constructors, one-shot RegisterNatives) is a documented boundary, not an end-to-end run."
|
|
},
|
|
{
|
|
"capability": "vm-protector-analysis",
|
|
"group": "native-dynamic",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/vm-protector-analysis.md",
|
|
"references/native-vm-recovery.md",
|
|
"references/native-dbi-and-deobfuscation.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"ref/vmp1.md, ref/vmp2.md, ref/vmp3.md -- public VMProtect teaching and crack write-ups (x86), methodology absorbed, no text copied",
|
|
"docs/tool-verification/EXTENSION-ref-absorption-2026-10.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Absorbed from x86 VMProtect-style samples and not executed against an Android target here. Covered: envelope triage (vmp/VMP0 section, entry jmp, push-imm/call, non-compiler prologue), VM_DATA/VM_CONTEXT/vEIP/vStack anatomy and central versus direct-threaded dispatch, data-anchored breakpoints with stack unwind, forged-return recognition, trace-then-search-by-constant with instruction-shape and operand-role filters, virtual eflags as a writable stack slot (eflags1 & 0x815 + eflags2 & ~0x815; ZF = & 0x40), NAND lowering and arithmetic identities, branchless select, and static rebase/xref caveats. Trace counts and addresses are one sample's and must not be carried across. It tells you which value a protected branch consumes; it does not reconstruct the original instruction stream."
|
|
},
|
|
{
|
|
"capability": "python-bytecode-recovery",
|
|
"group": "unpacking",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/python-bytecode-recovery.md",
|
|
"references/emulation-and-rpc.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"ref/py1.md -- public Pyarmor/pycdc static-unpacking write-up (2026), methodology absorbed, no text copied",
|
|
"docs/tool-verification/EXTENSION-ref-absorption-2026-10.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Absorbed from one Pyarmor build and never executed here. Covered: build-tag/RSA-blob/AST_nonce key derivation through MD5, AES-128-CTR with the 12-byte nonce and nonce[15]=2, the 12-byte nonce-XOR VM (8 registers, valid indices 0-5 and 7, opcodes 1-0xB, idiv clobbering register 0), version-gated pyc field widths and the pre-3.8 flag remap, the extra-section TLV (fn_count/descriptor_count, (byte>>6)+2 item length, big-endian consts index), per-code-object decryption including copy_prologue and 0x09 fill, and per-string tag rules. Every offset is version-specific; the file's own claim strength says so. Static route only: no runtime, device or root, and no recovered module was executed here."
|
|
},
|
|
{
|
|
"capability": "native-so-remote-debugger-attach",
|
|
"group": "native",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/ida-so-debugging.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"ref/idaso1.md, ref/idaso2.md -- public IDA-on-Android walkthroughs (2024-07), commands absorbed, no text copied"
|
|
],
|
|
"limits": "This is a documented route, not a measured one: no debugger was attached in this record and neither source targeted a hardened app. The mechanics covered are the two manifest preconditions, matching dbgsrv to the loaded ABI, running the server as uid 0 (else the attach list hides the target), am start -D plus the JDWP forward and jdb connect that actually releases the suspended process, and the extractNativeLibs=false failure in which the library is mapped from base.apk so no breakpoint can bind. Unverified: dbgsrv filenames per IDA release, chmod mode, menu labels across versions, and whether pushing an on-disk .so overrides the in-APK copy on a protected build. The route cannot hide TracerPid, the server binary on disk, or software breakpoints in mapped pages."
|
|
},
|
|
{
|
|
"capability": "blocked-server-side-authority",
|
|
"group": "boundary",
|
|
"status": "blocked",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/server-api.md",
|
|
"references/handoff-boundaries.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/README.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Determining who owns a gate is covered; breaking an authorization the server performs is not. There is no client-side patch that reaches it, and the honest deliverable is the residual: which authority decides, and why the artifact cannot change it."
|
|
},
|
|
{
|
|
"capability": "hardware-watchpoints-ptrace",
|
|
"group": "native-dynamic",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/hardware-watchpoints.md",
|
|
"scripts/hw_watch.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-hw-watchpoints.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Encoders, refusals and the emitted helper's static aarch64 build are measured on the host; arming a watchpoint on a device, the slot-capacity probe and the control run were never exercised here. The ptrace route leaves TracerPid visible by design -- the ledger in the reference is the contract."
|
|
},
|
|
{
|
|
"capability": "trace-differential-reduction",
|
|
"group": "native-dynamic",
|
|
"status": "partial",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/ete-diff-tracing.md",
|
|
"scripts/trace_diff.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-ete-diff.md (repository root, not shipped)"
|
|
],
|
|
"limits": "The reducer/differ is host-tested on synthetic flattened-dispatcher fixtures in both raw and run_probe-wrapped Stalker grammars. No producer (Stalker pair or cs_etm decode) was ever run through it end to end on a real target."
|
|
},
|
|
{
|
|
"capability": "ete-hardware-tracing",
|
|
"group": "native-dynamic",
|
|
"status": "blocked",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/ete-diff-tracing.md",
|
|
"scripts/ete_capture.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-ete-diff.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Gates, recipe and capture wrapper are host-measured to the no-device boundary. No coresight capture or decode ever ran here; the reference device's kernel (4.14.186) closes the gate permanently. The --control record is the one-command check that upgrades or refutes the route on a real device."
|
|
},
|
|
{
|
|
"capability": "kernel-instrument-injection",
|
|
"group": "kernel",
|
|
"status": "blocked",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/kernel-event-injection.md",
|
|
"scripts/kernel_instrument_scaffold.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-kernel-instrument.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Generate/verify and the shared spec-refusal rules are measured on the host. No kernel-side file was ever compiled or loaded; the register-rewrite action is labelled experimental in the template itself. Same gate family as the syscall-mask scaffold: a userspace carrier arms nothing."
|
|
},
|
|
{
|
|
"capability": "spe-brbe-crash-forensics",
|
|
"group": "native-dynamic",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/hardware-sampling-and-crash.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-sampling-crash.md (repository root, not shipped)"
|
|
],
|
|
"limits": "SPE data-flow sampling and BRBE branch records are documented-and-gated: no sample or record was ever captured on any device this repository used. The crash loop's ordering (tombstone -> branch records -> symbolize) is the deliverable."
|
|
},
|
|
{
|
|
"capability": "address-symbolization",
|
|
"group": "native-static",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/hardware-sampling-and-crash.md",
|
|
"scripts/trace_addr2sym.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-sampling-crash.md (repository root, not shipped)"
|
|
],
|
|
"limits": "The zero-dependency ELF64 walker is host-verified against a real cross-compiled aarch64 .so (symbols cross-checked with readelf) and a hand-built minimal ELF. Runtime-address inputs (hits, traces) were exercised on fixtures only, never on a live device trace."
|
|
},
|
|
{
|
|
"capability": "interpreter-trace-devirtualization",
|
|
"group": "native-dynamic",
|
|
"status": "partial",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/ete-diff-tracing.md",
|
|
"scripts/vm_handler_slice.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-sampling-crash.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Dispatcher detection, segment slicing, open-tail handling, nested-dispatch diagnostics, and per-segment opcode naming are host-tested on synthetic traces and measured end to end on a real hardened fixture (fco+bcfobf+subobf+IRVM sample, ptrace instruction trace, 24.6M steps): the fla outer state machine separates as a shuttle class, round-boundary segments split the trajectory, and positional alignment against a VMP_TRACE guest log names every handler segment (all 59 in a round; counts 3232/1600/1400/200 match the guest histograms exactly; EXTENSION-sampling-crash.md SS6). Field notes: virtualized pure calls can still be LICM-hoisted by the compiling optimizer; opcode maps key by signature; frida stalker does not work in these containers (measured past the syscall layer) -- use the ptrace stepper on hosts."
|
|
},
|
|
{
|
|
"capability": "dex-sql-query-layer-dexsql",
|
|
"group": "dex",
|
|
"status": "ok",
|
|
"route_measured": true,
|
|
"strength": "observed",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/dexsql-sql-query-layer.md",
|
|
"references/toolchain.md",
|
|
"scripts/capabilities.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-dexsql.md (repository root, not shipped)"
|
|
],
|
|
"limits": "Measured on dexsql v0.1.0, Windows amd64 release asset only; no other version or platform was exercised. Class-definition sets were identical to rasc, droidasc and ddc on four archives (1,396 / 647 / 4 / 30,768 classes, zero differences either way), and a string cross-reference query reproduced ASC's hits site for site on one archive. Three boundaries are load-bearing: `decode` emits smali rather than Java, SQL `=` is not `findrefs` (ASC matches a substring, so `LIKE` is the equivalent), and the persistent cache is not a speed switch (under 20% on a 34.8 MB archive, a net loss on a small one). The MCP server was exercised to a tool listing and a resource-model inventory, not end to end from a client."
|
|
},
|
|
{
|
|
"capability": "native-vm-recovery-procedure",
|
|
"group": "native-dynamic",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "inferred",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/native-vm-recovery.md",
|
|
"references/pitfalls.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"docs/tool-verification/EXTENSION-absorption-kx.md (repository root, not shipped)"
|
|
],
|
|
"limits": "The procedure (VM-existence signals, CFF-vs-VM dispatcher separation, relocation-recovered tables, register anchoring with triple verification, nested segment stacks, STORE-backward operand slicing with byte provenance, clean-re-VM validation) is absorbed from two public write-ups; every step is inferred here. The shipped slicer's nested-loop diagnostic is host-tested on a synthetic nested fixture. The xvmp family now has a working, verified runtime on the workbench branches, making a synthetic fixture route available end to end."
|
|
},
|
|
{
|
|
"capability": "jsvmp-recovery",
|
|
"group": "unpacking",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "inferred",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/jsvmp-recovery.md",
|
|
"scripts/jsvmp_loader_decode.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"three public write-ups of one reverse-engineering series, 2024-03..2024-09 (titles and authors anonymized; the absorbed record is the reference file itself)"
|
|
],
|
|
"limits": "The recovery procedures (recognition signals, the call-it-first route, stack- and register-machine reading, AST instruction extraction with register/immediate typing, the four JS-language evaluation traps, constant folding and control-flow recovery) are absorbed from three public write-ups and never executed by this repository on any real target -- all inferred. The shipped loader decoder is host-measured only against its own round trip (2,016 values exact, known varint/ZigZag byte layouts pinned, truncation raises) and decodes the write-up's own sample literal end to end; that is corroboration of the chain's shape, not a measurement on an independent target. Engine-specific delivery (WebView, QuickJS/JSC behind JNI, mini-program containers) was never exercised."
|
|
},
|
|
{
|
|
"capability": "js-ast-pre-deobfuscation",
|
|
"group": "unpacking",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "observed",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/js-ast-deobfuscation.md",
|
|
"scripts/js_obf_detect.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"lwjjike/xbsReverseSkill (MIT), ast-deobfuscation skill: pipeline-config.js, safe-rewrite-rules.md, string-array-and-minimal-eval.md, control-flow-and-opcode-patterns.md, pattern-layering.md -- architecture and rules absorbed 2026-10-20, no code copied"
|
|
],
|
|
"limits": "The detection layer is observed against its own embedded fixtures only (four family fixtures, the hint-beats-content scoring rule, plain-code-is-generic, residue metric filter) -- no real obfuscated bundle was ever classified here. The rewriting passes (string-array restore, dispatcher inlining, array-CFF flattening, if-chain-to-switch, identifier renaming) need node plus @babel/parser/traverse/generator, which this skill does not ship; every rewrite is a documented route, unverified end to end. Residue metrics are textual proxies, valid for same-file before/after comparison only. The per-family pass-order caveat carried from the absorbed architecture (VM-heavy families skip late literal-inlining because it stalls large samples) is the upstream's measurement, not this repository's."
|
|
},
|
|
{
|
|
"capability": "kotlin-name-recovery",
|
|
"group": "dex",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "observed",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/kotlin-name-recovery.md",
|
|
"scripts/kotlin_name_recovery.py"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"SimoneAvogadro/android-reverse-engineering-skill (Apache-2.0): recover-kotlin-names.sh and references/kotlin-name-recovery.md -- re-implemented 2026-10-20 as dependency-free Python"
|
|
],
|
|
"limits": "Parsing of all three recovery sources (@DebugMetadata c=, @Metadata d2 first non-stdlib descriptor, jadx 'renamed from' comments), the third-party skip list and the map-file round trip are observed on embedded fixtures only. The upstream recovery-rate claims (30-50% of classes overall, ~100% of *Repository/*ViewModel/*Impl, ~80% of data-class DTOs) are unverified here: no real obfuscated Kotlin app was run through the script. Method and field names are never recovered; heavily inlined shapes can surface under a wrong primary class, so every mapping row is a hint. The script reads decompiled sources, not the dex: a decompiler that drops annotations removes the source entirely."
|
|
},
|
|
{
|
|
"capability": "native-dump-window-and-syscall-reader",
|
|
"group": "native",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/linker-and-soinfo-repair.md",
|
|
"references/advanced-unpacking.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"ref/vm1.md (repository root, git-ignored, not shipped): 2026-10-25 write-up on a dual-library commercial shell"
|
|
],
|
|
"limits": "Operating rules only, absorbed 2026-10-25 and never exercised here: the dump window that closes inside JNI_OnLoad when self-decryption and watchdog startup share that function, the raw-syscall reader that stays outside a self-hooked libc, and zero-filling unreadable pages so segment offsets survive repair. The zero-fill/offset consequence is observed on a synthetic three-page image (marker at 8199 zero-filled, 4103 skipped); the window, the reader and the target behaviour are unverified, and the placement rule is inferred from the linker arithmetic."
|
|
},
|
|
{
|
|
"capability": "whitebox-crypto-devirtualization-to-program",
|
|
"group": "native-dynamic",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/native-vm-recovery.md",
|
|
"references/vmp-differential-analysis.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"ref/vm2.md (repository root, git-ignored, not shipped): 2026-10-25 write-up on a white-box VM protecting one signing routine"
|
|
],
|
|
"limits": "The route -- symbolic input, constant folding, loop and branch elimination, an (op, args) straight-line program plus its constant table, output map and output template -- is absorbed from one write-up and never run. It applies only to a deterministic, input-driven function: device id, time or nonce inputs become captured constants, and the claim then degrades to reproducing one device. The program is version-bound; no extract was produced here."
|
|
},
|
|
{
|
|
"capability": "cipher-classification-by-differential-probe",
|
|
"group": "protocol",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "inferred",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/protocol-reverse.md",
|
|
"references/signature-derived-keys.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"ref/vm3.md (repository root, git-ignored, not shipped): 2026-10-25 write-up on a native signer and an encrypted request body"
|
|
],
|
|
"limits": "Three black-box probes -- header length, output determinism, and one-byte diffusion width, plus the length law -- the involution-wrapper algebra, and Java-versus-Python encoding plus compression drift. Host-checked on AES-128 through openssl and on synthetic inputs: the probes separate CTR, CBC and ECB (1 / all-following / one block changed per flipped byte), the mask identity has zero counterexamples over 65,536 eight-bit pairs and 200,000 random 16-bit pairs, the length law holds for b=16, and zlib levels 1 and 9 emit different valid streams for one payload. The probe this row originally described (prefix XOR implies a stream cipher) was falsified by that run -- CBC and ECB also show zero prefix-XOR at a fixed IV -- and the reference now carries the corrected discriminator. No target body was classified, and no server was tested for whether it compares compressed bytes or only the decompressed payload."
|
|
},
|
|
{
|
|
"capability": "websocket-long-connection-analysis",
|
|
"group": "protocol",
|
|
"status": "partial",
|
|
"route_measured": false,
|
|
"strength": "unverified",
|
|
"benchmark_rows": [],
|
|
"evidence": [
|
|
"references/protocol-reverse.md"
|
|
],
|
|
"evidence_not_shipped": [
|
|
"715494637/reverse-skill (no license file): jsr-reverse/references/protocol-and-long-connection.md -- methodology only absorbed 2026-10-20, no text copied"
|
|
],
|
|
"limits": "The state-chain method (capture handshake, first business frame, heartbeat/ack, renewal, error; record the connection as a dependency chain; separate message families; split envelope from payload before body semantics) is absorbed from a browser-WebSocket reference and was never run on an Android long-connection target here. The Android capture points in the section (OkHttp WebSocket listener surfacing, native/QUIC transports never transiting Java) are inferred from documented APIs, not measured. Frame bodies that are protobuf do inherit the measured schema-free decoder from protocol-reverse.md section 1; that is the only measured part of the route."
|
|
}
|
|
]
|
|
}
|