agentsclimarketplace
Sign in

Recovering injected code and shellcode

Skill meltedinhex/analyst-ai-pack/skills/recovering-injected-code-and-shellcode

Carves injected PE images and position-independent shellcode from a memory dump or carved region, identifies the payload type, and prepares it for disassembly or emulation. Activates for requests to recover injected code, carve shellcode from memory, or reconstruct a dumped payload for analysis.From its SKILL.md

Install
npx -y skills add meltedinhex/analyst-ai-pack --skill recovering-injected-code-and-shellcode

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 21 stars21 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, 480 tokens by cl100k_base, as published. Nobody here has run it

Recovering Injected Code and Shellcode

When to Use

  • You have a carved memory region (from malfind/vaddump) and need to identify and extract the payload — an injected PE or raw shellcode.
  • You need to locate likely shellcode entry points (egg hunters, GetPC stubs) before disassembly.

Do not use this to execute the payload — it prepares code for static disassembly/emulation in a controlled tool, not for running.

Prerequisites

  • A carved binary region (raw bytes) from a memory image.

Safety & Handling

  • The carved region is live malicious code; store it password-protected and never execute it.

Workflow

Step 1: Identify payload type

python scripts/analyst.py identify region.bin

Detects an embedded MZ/PE (with offset) versus raw shellcode, and reports the PE's architecture if present.

Step 2: Locate shellcode entry hints

Finds common position-independent code markers: GetPC stubs (call $+5/fldz/fnstenv), PEB access (fs:[30]/gs:[60]), and API-hashing loops.

Step 3: Extract for analysis

Carve the PE at its offset (or keep the raw shellcode) and hand it to a disassembler/emulator at the detected base/entry.

Step 4: Document

Record offsets, architecture, and entry hints for the downstream RE workflow.

Validation

  • An embedded PE is confirmed by MZ + valid e_lfanew → PE\0\0.
  • Shellcode entry hints reference real PIC patterns, not arbitrary bytes.
  • Architecture detection matches the PE Machine field (or PIC heuristics for raw shellcode).

Pitfalls

  • Assuming everything carved is a PE; much injected code is headerless shellcode.
  • Wrong base address breaking relocations when loading a dumped PE — note it for rebuilding.
  • Treating compressed/encrypted stages as final shellcode without a decode pass.

References

What ships with it: 3 files

3.8 KB alongside SKILL.md, 1 of them executable

references/

scripts/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.