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-loaders-and-droppersMobile, firmware and hardware

analyzing-loaders-and-droppers

⁨Analyzes loader and dropper samples by identifying staging behavior — embedded 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/analyzing-loaders-and-droppers

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

SignatureSigned, ed25519
2IwNDeyoPf…OE4CQ1Cg==The CLI checks the SHA-256 and the signature before it writes a file.
Package3b5a0a3c…6b6fe0a8
3b5a0a3c7cc7…77116b6fe0a84 files · ⁦3.4 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-loaders-and-droppers@da7600a

When to Use

  • You have a first-stage loader/dropper and need to find the next stage: an embedded resource, an appended overlay, or a download URL.
  • You need to identify the decode/decrypt routine and the execution mechanism (process creation, injection, scheduled task, DLL side-loading).

Do not use this to run the loader and fetch live stages — characterize staging statically and retrieve next stages only in an isolated sandbox.

Prerequisites

  • The loader/dropper sample (read inertly).

Safety & Handling

  • Read bytes statically; defang download URLs; never execute to pull live payloads.

Workflow

Step 1: Locate staged payloads

bash
python scripts/analyst.py stage sample.bin

Detects embedded PE/archive signatures, an appended overlay beyond the PE's mapped size, large high-entropy blobs, and download URLs.

Step 2: Identify decode/execution mechanism

Scan imports/strings for decode APIs (CryptDecrypt, base64), download APIs (URLDownloadToFile, WinHttp, InternetReadFile), and execution (CreateProcess, ShellExecute, WinExec, side-loading hints).

Step 3: Map the delivery chain

Document stage-1 → decode → stage-2 → execution and map each step to ATT&CK.

Step 4: Defang and report

Defang URLs and produce IOCs for the staging infrastructure.

Validation

  • Embedded/overlay stages are confirmed by signature or entropy, with offsets recorded.
  • Download URLs and execution mechanism are identified from imports/strings.
  • The multi-stage chain maps cleanly to ATT&CK techniques.

Pitfalls

  • Treating a benign overlay (installer data, signature) as a payload without corroboration.
  • Missing stages fetched at runtime when no URL is in plaintext (obfuscated/encoded).
  • Confusing the decode routine for the payload itself.

References

  • See references/api-reference.md for the stager.
  • ATT&CK T1105 and T1140 (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
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, 2026da7600a3b5a0a3cSigned–

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