AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL unreviewed Apache-2.0 Self-run

Analyzing Webshells

skill-meltedinhex-analyst-ai-pack-analyzing-webshells · by meltedinhex

Analyzes suspected webshells (PHP, ASPX/ASP, JSP) by detecting dynamic-execution

No reviews yet
0 installs
32 views
0.0% view→install

Install

$ agentstack add skill-meltedinhex-analyst-ai-pack-analyzing-webshells

Open-source listing, not yet scanned by AgentStack. Follow the source repository for install instructions.

Reliability & compatibility

Not yet reviewed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Analyzing Webshells? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Analyzing Webshells

When to Use

  • You found a suspicious server-side script (.php, .aspx, .jsp, .asp) and need to confirm

it is a webshell and understand its command interface.

  • You are triaging a web-server compromise and want to classify dropped scripts.

Do not use a live web server to execute the script to "test" it — that runs attacker code. Analyze the source statically.

Prerequisites

  • The suspect script file(s), read inertly.

Safety & Handling

  • Read the file statically; never deploy or request it on a live server. Defang any URLs.

Workflow

Step 1: Detect execution sinks and input flow

python scripts/analyst.py scan shell.php

Flags dynamic-execution sinks (eval, assert, system, exec, passthru, Runtime.exec, ASPX eval()/Process.Start) and whether request input ($_GET/$_POST/Request) reaches them.

Step 2: Identify obfuscation/encoder chains

Detects base64_decode, gzinflate, str_rot13, eval(chr(...)), hex \x strings, and FromBase64String chains commonly wrapping the payload.

Step 3: Decode obvious layers

Apply base64/rot13/gzinflate where present to reveal the inner command interface (best-effort, non-executing).

Step 4: Classify and report

Note the language, the password/parameter gate (if any), and capabilities (file manager, command exec, SQL, upload); defang IOCs.

Validation

  • A flagged file pairs an execution sink with attacker-controlled input.
  • Encoder chains are identified and, where safe, decoded statically.
  • Capability classification is backed by concrete code evidence.

Pitfalls

  • Legitimate admin tools that also use eval/system — corroborate with input flow.
  • Multi-stage shells that fetch the real logic remotely.
  • Deeply nested or runtime-built obfuscation that static decode only partly unwinds.

References

  • See [references/api-reference.md](references/api-reference.md) for the scanner.
  • ATT&CK T1505.003 (linked in frontmatter).

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.