Skip to content
cccskills
FreePublished on GitHub

analyzing-malicious-lnk-files

Analyzes weaponized Windows shortcut (.lnk) files: parsing the shell link structure for the target command, arguments, icon, and working directory, and recovering hidden PowerShell/cmd payloads and embedded content used in phishing. Activates for requests to analyze a malicious LNK, parse a shortcut file, or extract a command from a .lnk.

The English summary is being prepared. Showing the original description.

See how to install

Files included (4)

  • SKILL.md3.2 KB
  • LICENSE340 B
  • references/api-reference.md1.3 KB
  • scripts/analyst.py3.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Analyzing Malicious LNK Files

When to Use

  • You have a .lnk delivered via phishing (often in an archive or ISO) and need its real action.
  • You must recover the target command line, arguments, and any embedded/hidden payload.
  • You are extracting IOCs (commands, URLs, file paths) from a shortcut.

Do not use Windows Explorer to inspect or double-click the shortcut — that executes its target. Parse the binary structure statically.

Prerequisites

  • An LNK parser (Python struct, or lnkparse/LECmd); the sample handled inertly.

Safety & Handling

  • Never double-click or hover-load the shortcut in Explorer; parse raw bytes only.
  • Defang recovered URLs and store any embedded payload password-protected.

Workflow

Step 1: Confirm and parse the header

Verify the LNK magic (4C 00 00 00 + the link CLSID) and read LinkFlags to know which optional structures are present.

python scripts/analyst.py parse sample.lnk

Step 2: Recover the target and arguments

Extract the relative/local path and, crucially, the COMMAND_LINE_ARGUMENTS string — malicious LNKs hide powershell -enc ... or cmd /c ... here.

Step 3: Inspect icon and metadata

Read the icon location (often spoofed to look like a document) and metadata (machine ID, timestamps) useful for attribution/clustering.

Step 4: Find appended/embedded payloads

Check for data appended after the LNK structure (some campaigns embed scripts/binaries past the parsed end) and extract it.

Step 5: Decode and extract IOCs

Decode encoded commands (UTF-16LE base64), defang URLs, and route extracted payloads to the right analysis workflow.

Validation

  • The full command line, including arguments, is recovered (not just the target path).
  • Encoded commands are decoded to cleartext.
  • Appended/embedded payloads are detected and extracted, and IOCs are defanged.

Pitfalls

  • Reading only the target path and missing the malicious arguments.
  • Inspecting in Explorer and executing the shortcut.
  • Ignoring data appended past the LNK structure.

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Reverses Android malware: unpacking APKs, decompiling DEX bytecode to readable Java, auditing the manifest for abused permissions and components, and locating dynamically loaded or native payloads. Activates for requests to analyze an APK, decompile DEX, or investigate a suspicious Android app.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes API call traces from a sandbox or API monitor (JSON) to group calls by category, reconstruct high-level behaviors (process injection, file drops, network, crypto), and flag suspicious call sequences. Activates for requests to analyze an API trace, interpret sandbox API logs, or identify behavior from Win32/Native API calls.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes Windows Authenticode signatures on PE files: checking for a signature, reading the signer certificate chain, detecting revoked/expired/stolen certs, and recognizing signature-stripping and catalog-signing abuse. Activates for requests to analyze a code signature, verify Authenticode, or assess signer trust on a PE.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes banking trojan webinject configurations to extract targeted institutions, injected JavaScript/HTML, and data-theft hooks, mapping the fraud workflow. Activates for requests to analyze banking trojan webinjects, parse a webinject config, or map targeted banks and credential-theft injections.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes Python-based malware packaged as PyInstaller/py2exe executables by detecting the packer, locating the embedded archive, and identifying bundled .pyc modules for extraction and decompilation. Activates for requests to analyze compiled Python malware, unpack a PyInstaller binary, or extract pyc modules from a frozen Python executable.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

Analyzes cryptojacking/coinminer malware by extracting mining pool endpoints (stratum), wallet addresses, algorithm and miner identifiers (XMRig and forks), and persistence or resource-control settings from static strings and config. Activates for requests to analyze a cryptominer, extract mining pool and wallet IOCs, or identify coinminer configuration.

The English summary is being prepared. Showing the original description.

meltedinhex/analyst-ai-pack22Updated Jul 7, 2026

See all skills by meltedinhex

Report a problem with this skill