Install
$ agentstack add skill-batteryshark-rekit-dex-dump ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
dex-dump — Android DEX Dumper
Dump decrypted DEX and CompactDex images from a running Android app's memory using Rekit's original dex-dumper (ptrace attach on a rooted device).
What it does
Android packers that encrypt/load DEX at runtime only materialize the real DEX in memory after their class loader decrypts it — so the on-disk APK holds an encrypted stub, not the real code. This skill pushes a device-side dumper, ptrace-attaches to the already-running app, and reads the decrypted DEX out of memory.
Does not execute a sample on the host. Invasive only on the connected device.
Prerequisites
adbon PATH (Android Platform Tools).- A rooted aarch64 Android device connected via USB (
dex-dumperusesptrace;
the runner verifies either adb root or a working su -c).
- A device binary built once with
bin/rekit install dex-dump. Building requires
Rust 1.74+, the aarch64-linux-android target, and Android NDK r25+; set ANDROID_NDK_HOME first.
- The target app must be running and past its splash screen — the packer must
have decrypted the real DEX. Launch the app and navigate past any splash/loader before running.
Usage
# explicit package
rekit run dex-dump com.example.app ./out
# auto-detect the foreground app
rekit run dex-dump auto ./out
# specific device serial (multiple devices connected)
rekit run dex-dump com.example.app ./out --device 1234567890abcdef
Result is a single JSON object on stdout: {ok, package, pid, dexFiles, fileCount, outputDir}. Multiple DEX files are normal for packed apps — pull all of them.
Notes
--keep-toolleavesrekit-dex-dumperon the device (default cleans up both the
tool and the dumped files after pulling).
- The runner never launches the target. If
pidofreturns empty, launch the app
yourself and wait until its loader has decrypted the DEX.
- Pair the pulled DEX with your Android decompiler (jadx / dex2jar) and any class
deobfuscation step.
Source and license
The dependency-free Rust source, host tests, build instructions, and clean-room provenance statement live in [scripts/dex-dumper/](scripts/dex-dumper/README.md). The implementation and binaries built from it are licensed Apache-2.0 under Rekit's root license. No panda-dex-dumper source or binary is included.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: batteryshark
- Source: batteryshark/rekit
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.