reverse-eng-thick-client
Security-test a desktop thick client end to end: map its trust boundaries, then work the local attack surface (config files, credential storage, IPC, update channel) and the network surface (proxying, certificate pinning, hidden APIs). Load for a C/S desktop app in scope — Electron, Qt, .NET WinForm
v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/reverse-eng-thick-clientWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package0824e60e…42155b09
0824e60ebdda…acff42155b091 file · 2.5 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-thick-client@ee0e0c5
On this page
When it applies
The engagement includes a desktop application — a client-server (C/S) client built on
Electron, Qt, .NET WinForms/WPF, or native code — rather than a pure web app. Typical triggers:
an installer in scope, credentials cached locally, an auto-updater, a loopback port or named
pipe, or API calls the UI never exposes. Record the installer source and the test accounts in
scope.txt (tradecraft-scope-roe); test only machines and accounts you're authorized for.
Why it works
A thick client is a server-side trust boundary shipped to an attacker-controlled machine: everything it stores, every check it enforces locally, and every API it knows how to call is yours to read. The client cannot keep secrets from its operator — so hardcoded keys, hidden admin endpoints, and client-enforced validation are structural findings, not luck.
Method
Work boundary → local surface → network surface → reverse-engineering confirmation.
- Map the trust boundary. Enumerate the process tree and child processes, any services or
drivers it installs, listening ports (a loopback socket bound to
0.0.0.0is an instant finding), outbound domains, and the sensitive paths it touches:%APPDATA%, Keychain, registry hives. Process Monitor and TCPView (Sysinternals) get you this in minutes. - Work the local attack surface. Look for plaintext config and logs, hardcoded keys, leftover debug switches and hidden menus, SQLite databases (permissions and encryption), credential storage (DPAPI / Keychain / plaintext), autostart entries, install/uninstall residue and file permissions, and on Windows DLL search-order hijacking. Check IPC: who can connect to the named pipe / loopback port, and is there any authentication?
- Work the network surface. Determine whether the app honors the system proxy or uses
custom TLS; force it through Burp/mitmproxy. Certificate pinning → the usual bypasses
(
mobile-cert-pinning-bypasstechniques, or Frida on the desktop process). Once traffic is visible, hunt client-hidden API surface: admin functions the UI gates but the server may not — feed the recovered endpoints intoapi-testing-checklist/api-bola. - Reverse to confirm. .NET → dnSpy/ILSpy (deobfuscate with de4dot if needed). Native →
reverse-eng-binary-triage. Electron → extractapp.asar(npx asar extract app.asar out/) and treat it as front-end JS (reverse-eng-js). Verify how licenses, signatures, and integrity checks are enforced — anything checked only client-side is bypassable by design. - Update channel & supply chain. Check the update URL (HTTP vs HTTPS), whether the update package is signature-verified, and whether the check itself runs client-side. A confirmed weak update channel is high-impact — document, don't weaponize, without explicit scope.
Gotchas
- Electron apps are web apps in a trench coat — don't start with a disassembler; the
asarplus DevTools answers most questions in minutes. - .NET obfuscation makes dnSpy output noisy — run de4dot first, and prefer runtime inspection (dnSpy debugger) over static reading for the interesting checks.
- "Server validates too" assumption — never report client-side-only checks without testing the server's response to a tampered request; some are genuinely enforced server-side.
- Clean up your artifacts — remove planted DLLs, proxy certificates, patched binaries, and test accounts when done (house rule: minimize footprint).
Verify success
You have a trust-boundary diagram (processes, ports, files, servers), both local and network
surfaces covered, and at least one concrete, demonstrated finding class — e.g. a recovered
secret, a server-accepted tampered request, or an unauthenticated IPC connection — validated
per reporting-triage-validation.
References
OWASP Desktop Application Security Top 10; Sysinternals suite; dnSpy docs; reverse-eng-js,
reverse-eng-binary-triage, mobile-cert-pinning-bypass in this library.
Portions adapted from reverse-skill by zhaoxuya520, MIT License.
Files in this version
- SKILL.md4.9 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | Nov 13, 2026 | ee0e0c5 | 0824e60e | Signed | – |
More from NoorQureshi
All from this publisherMore in Reverse engineering and fuzzing
See the categoryAsk anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login