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/analyzing-position-independent-codeReporting and compliance

analyzing-position-independent-code

⁨Analyzes position-independent code and shellcode by identifying GetPC/PEB-walk⁩

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

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/analyzing-position-independent-code

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

SignatureSigned, ed25519
rpqHmsySEx…Bo+6gSCQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package9e2c0e43…a3a3fbde
9e2c0e43a70f…b2dda3a3fbde4 files · ⁦2.8 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/analyzing-position-independent-code@da7600a

When to Use

  • You have a PIC blob/shellcode that resolves its own addresses and APIs without imports, and you need to understand its technique before disassembly.
  • You want to identify the base-resolution (GetPC), PEB-walk, and API-hashing mechanics.

Do not use this to execute the code — analyze it statically (and emulate separately if needed). Treat the blob as malicious.

Prerequisites

  • The PIC/shellcode blob (read inertly).

Safety & Handling

  • Read bytes statically; store the blob password-protected and never execute it.

Workflow

Step 1: Identify PIC techniques

bash
python scripts/analyst.py analyze shellcode.bin

Detects GetPC stubs (call $+5/fnstenv), PEB access (fs:[30]/gs:[60]), API-hash loops (lodsb + ror), and stack-string construction.

Step 2: Determine architecture and base behavior

Confirm 32- vs 64-bit PEB access and how the code computes its own base for relative addressing.

Step 3: Map API resolution

Note the hashing algorithm and that resolved APIs are obtained by walking the PEB→LDR→export tables (pair with the API-hash resolver skill).

Step 4: Disassemble at the right base

Load the blob at the inferred base/entry in a disassembler/emulator and proceed.

Validation

  • PIC technique hits reference real patterns (GetPC/PEB/API-hash), not arbitrary bytes.
  • Architecture is consistent with the PEB-access form detected.
  • The analysis points to a concrete entry/base for disassembly.

Pitfalls

  • Encoded/staged shellcode where the PIC patterns appear only after decoding.
  • Mixed 32/64-bit (WoW64) transitions.
  • Custom GetPC variants not matching common signatures.

References

  • See references/api-reference.md for the analyzer.
  • PEB/LDR and ATT&CK T1027.007 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, 2026da7600a9e2c0e43Signed–

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