Skip to content
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
meltedinhex/reverse-engineering-arm-binariesReverse engineering and fuzzing

reverse-engineering-arm-binaries

⁨Reverse engineers ARM/AArch64 malware by identifying the architecture and instruction⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/reverse-engineering-arm-binaries

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
XT+X2hhj3n…796JhCAw==The CLI checks the SHA-256 and the signature before it writes a file.
Packagecec24d1c…9a805fd7
cec24d1c62a7…77369a805fd74 files · ⁦2.9 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/reverse-engineering-arm-binaries@da7600a

When to Use

  • You have an ARM (32-bit) or AArch64 (64-bit) binary — IoT/mobile/Linux malware — and need to identify the architecture, instruction-set state, and entry point before disassembly.
  • You need to handle ARM/Thumb interworking correctly.

Do not use an x86 mindset for calling conventions/registers — ARM differs. This skill reads the binary statically and executes nothing.

Prerequisites

  • The ARM binary (ELF or Mach-O), read inertly. Capstone optional for instruction decoding.

Safety & Handling

  • Read bytes statically; analyze on an isolated host (and emulate via QEMU separately if needed).

Workflow

Step 1: Identify architecture and format

bash
python scripts/analyst.py identify sample.bin

Parses ELF/Mach-O headers to report ARM vs AArch64, endianness, entry point, and (for ELF) whether the entry is Thumb (low bit set in e_entry or $t mapping symbols).

Step 2: Set the correct disassembly mode

Disassemble AArch64 as A64; for 32-bit ARM, switch between ARM and Thumb per the entry/mapping symbols.

Step 3: Orient around the calling convention

Track arguments in r0-r3/x0-x7, return in r0/x0, and syscalls via svc with the syscall number in r7/x8.

Step 4: Proceed with analysis

Identify functions, strings, and syscalls; pair with emulation if dynamic insight is needed.

Validation

  • Architecture (ARM/AArch64) and endianness are read from the header.
  • The entry point and ARM/Thumb state are reported.
  • Disassembly mode matches the detected state.

Pitfalls

  • Missing Thumb state and decoding Thumb as ARM (garbage output).
  • Big-endian ARM (rare but real) mis-parsed as little-endian.
  • Statically linked musl/uClibc inflating the function set on IoT samples.

References

  • See references/api-reference.md for the identifier.
  • Arm ARM and AAELF references (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600acec24d1cSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login