Menu

Individual skill

testing-thick-clients

0upvotes

Security-test desktop thick-client applications (.NET/WPF, Java, Electron, native Win32) against their local and network attack surface — proxying non-HTTP traffic, extracting secrets and DB connection strings from config/registry/memory, bypassing client-side trust controls, and reviewing update channels and DLL search order. Use when assessing an installed desktop app that talks to a backend, when Burp sees no traffic from a fat client, or when a two-tier app connects straight to a database.

secskills-offense/skills/testing-thick-clients/SKILL.md

Read pinned source

Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
188
Repository last updated
Sep 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Testing Thick Clients

A thick client puts part of the application on the tester's own machine, and
that is the whole opportunity: the binary, its config, its memory, and its
traffic are all reachable. The recurring failure in these apps is trusting the
client — enforcing authorization, hiding functionality, or holding secrets on a
box the user controls. The job is to enumerate that surface and show where the
trust is misplaced.

## When to Use

- Assessing an installed desktop application (.NET/WPF, Java/Swing, Electron,
  Qt, native Win32) that communicates with a backend
- A fat client where Burp shows nothing because the traffic is not HTTP or not
Back to top