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/deobfuscating-malicious-powershellReverse engineering and fuzzing

deobfuscating-malicious-powershell

⁨Deobfuscates malicious PowerShell by decoding -EncodedCommand, reversing string⁩

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/deobfuscating-malicious-powershell

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

SignatureSigned, ed25519
9Jub40PMlh…1OFt5IBg==The CLI checks the SHA-256 and the signature before it writes a file.
Package4dd88965…d95b1ce4
4dd88965f708…a5b9d95b1ce44 files · ⁦3.6 KB⁩
ScanMedium12 findings
  • command.pipe_to_shellSKILL.md:4
  • command.pipe_to_shellSKILL.md:37
  • command.pipe_to_shellSKILL.md:39
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/deobfuscating-malicious-powershell@da7600a

When to Use

  • You captured an obfuscated PowerShell command from a log, maldoc, or phishing payload.
  • You need to recover the real intent: download URLs, dropped paths, shellcode, or next stage.
  • You are unrolling layered encoding (base64 → gzip → IEX) to reach the final script.

Do not use Invoke-Expression or run the script to "see what it does" on a working host. Decode statically; only execute in the isolated lab with logging if dynamic confirmation is required.

Prerequisites

  • Python (bundled script handles base64/gzip/deflate and common transforms), or a sandbox.
  • The command/script text captured as a string.

Safety & Handling

  • Never pipe attacker PowerShell into a live shell. Replace IEX/Invoke-Expression with output (print) when transforming.
  • Treat decoded URLs/IPs as live; defang before sharing.

Workflow

Step 1: Decode -EncodedCommand

-EncodedCommand (-enc) is base64 of UTF-16LE. Decode it first:

bash
python scripts/analyst.py decode --encodedcommand "<base64>"

Step 2: Identify the obfuscation style

Common patterns:

text
String reversal      : [array]::Reverse / -join with [-1..]
Format operator      : ("{1}{0}" -f 'b','a') -> 'ab'
Char codes           : [char]104 + [char]105
Concatenation/splits : 'po'+'wer'+'shell', -split / -replace tricks
Backtick/casing noise : I`E`X, iEx, &('i'+'ex')

Step 3: Unroll encoding layers

Resolve nested FromBase64String, gzip/deflate (IO.Compression), and re-IEX layers until you reach plain script. The script peels base64/gzip layers automatically.

bash
python scripts/analyst.py deobfuscate payload.ps1

Step 4: Neutralize execution sinks

Replace IEX, Invoke-Expression, &, and .Invoke() with a print so the recovered script is rendered, not run.

Step 5: Extract IOCs

Pull DownloadString/DownloadFile URLs, C2 hosts, dropped paths, and any embedded base64 shellcode for separate analysis.

Validation

  • The fully decoded script is human-readable PowerShell with no remaining base64 blobs.
  • Execution sinks are neutralized; nothing in your workflow actually ran the payload.
  • Extracted URLs/paths are consistent with the script's logic.

Pitfalls

  • Running the script to decode it — the fastest way to get compromised.
  • Stopping after one base64 layer when several are nested.
  • Missing UTF-16LE vs UTF-8 when decoding -enc (it is UTF-16LE).
  • Ignoring -replace/-f transforms that rebuild commands at runtime.

References

  • See references/api-reference.md for the decoder/deobfuscator.
  • PowerShell encoded-command docs and PSDecode (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. MediumCommand · command.pipe_to_shellSKILL.md:4
  2. MediumCommand · command.pipe_to_shellSKILL.md:37
  3. MediumCommand · command.pipe_to_shellSKILL.md:39
  4. MediumCommand · command.pipe_to_shellSKILL.md:50
  5. MediumCommand · command.pipe_to_shellSKILL.md:73
  6. MediumCommand · command.pipe_to_shellSKILL.md:78
  7. MediumCommand · command.base64_execSKILL.md:78
  8. MediumCommand · command.pipe_to_shellSKILL.md:87
  9. MediumCommand · command.pipe_to_shellreferences/api-reference.md:6
  10. MediumCommand · command.pipe_to_shellreferences/api-reference.md:32
  11. MediumFile · Executable script shipped with the skillscripts/analyst.py
  12. 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, 2026da7600a4dd88965Signed–

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