thick-client

Tests desktop thick clients for local storage, IPC, traffic, and trust boundary weaknesses.

21|8|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/chengzongcai/reverse-skill-backup --skill thick-client-chengzongcai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: thick-client
Source: https://github.com/chengzongcai/reverse-skill-backup/tree/main/skills/thick-client
Command: npx skills add https://github.com/chengzongcai/reverse-skill-backup --skill thick-client-chengzongcai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Security testers assessing desktop applications often lack a repeatable methodology, leading to missed attack surfaces like local credential storage, IPC endpoints, and update channels. This Skill provides a structured workflow for authorized thick client security testing. ## Core Features & Use Cases - Trust Boundary Mapping: Enumerate process trees, listening ports, outbound domains, and sensitive local paths such as %APPDATA%, Keychain, and the registry. - Local and Network Attack Surface Coverage: Check plaintext configs, hardcoded keys, DLL hijacking, SQLite permissions, IPC authentication, TLS pinning, and hidden admin APIs. - Reverse Engineering Routing: Direct .NET targets to dnSpy, native binaries to IDA/Ghidra, and Electron apps to asar plus JS analysis. - Use Case: Given an authorized engagement against an Electron-based desktop client, follow the checklist to intercept its traffic with Burp, extract the asar archive, and verify whether its auto-update channel validates code signatures. ## Quick Start Ask the AI to perform an authorized security assessment of a desktop thick client application covering local storage, IPC, network traffic, and update channels.

Frequently Asked Questions about thick-client

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I security test a desktop thick client application?▼

Start by mapping trust boundaries: process trees, listening ports, outbound domains, and sensitive local paths. Then cover the local attack surface (plaintext configs, DLL hijacking, SQLite permissions, IPC authentication) and the network surface (TLS pinning, hidden APIs) before reverse engineering verification.

What tools are used for thick client penetration testing?▼

Use Process Monitor or API Monitor for behavior analysis, Burp or mitmproxy for traffic interception, and Sysinternals for Windows-specific surfaces. For reverse engineering, use dnSpy for .NET, IDA or Ghidra for native binaries, and asar extraction for Electron apps.

How do I intercept traffic from an Electron desktop app?▼

Route the app through Burp or mitmproxy using a system or upstream proxy. If the app enforces certificate pinning, combine JS reverse engineering on the extracted asar archive or use Frida-based instrumentation to bypass the pinning checks.

Does this methodology apply to web applications?▼

No, it targets desktop thick clients with local components such as GUI processes, services, local storage, and IPC. Pure web applications should be handled with web and API security testing methodologies instead.

What local storage risks should I check in thick clients?▼

Check credential storage in DPAPI, Keychain, or plaintext files, hardcoded keys, debug switches, and SQLite database permissions and encryption. Also review install/uninstall remnants, auto-start entries, and update URL signature validation.