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/recovering-injected-code-and-shellcodeReverse engineering and fuzzing

recovering-injected-code-and-shellcode

⁨Carves injected PE images and position-independent shellcode from a memory dump or⁩

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/recovering-injected-code-and-shellcode

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

SignatureSigned, ed25519
RjqKCXgXNX…z1GIM0AQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package46574745…e0a0a979
46574745b28d…6979e0a0a9794 files · ⁦3.0 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/recovering-injected-code-and-shellcode@da7600a

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

bash
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

  • See references/api-reference.md for the identifier.
  • ATT&CK T1620 and T1055 (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, 2026da7600a46574745Signed–

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