Opus finding
auth --force bypasses cached-token wallet-mismatch protection but still keys on cfg.network — could overwrite a session for a different wallet without warning
lowsecuritymedium
- src/commands/auth.ts:58-75
- src/state/db.ts:177-182
saveSession overwrites any prior session at the (network:name) key. If a user runs `reppo auth --force` with a different REPPO_PRIVATE_KEY than the previously cached one, the prior wallet's session is silently replaced. Not a vulnerability per se, but the docs imply per-wallet caching; nothing emits a warning that another wallet's token was overwritten.
Recommendation
Either key sessions by (network:wallet) or emit a notice when --force replaces a session belonging to a different walletAddress.