A useful page for a media app says that refresh-token reuse has crossed the investigation threshold, identifies the affected device session, and gives the responder enough context to revoke that session without signing every subscriber out. Treat this as a proposed alert design, not a report of an incident. A spike in failed logins alone doesn't tell the on-call engineer which phone to remove.
Short answer: issue a short session to the mobile app, keep refresh operations behind the Node.js backend, and associate each device with a session ID that the owner can revoke from settings. Rotate refresh credentials as part of that backend workflow. For bot and abuse resistance, define what happens to a reused credential before deciding how many refresh requests the service can absorb.
Keep the blast radius small.
How should a Node.js backend detect stolen mobile sessions before login complaints?
Start with the missing signal: a refresh credential that was already consumed appears again.…