Original topic:

Google Account Session Logouts While Using A53 5G with Windows Chrome Browser

(Topic created: 07-07-2025 05:21 AM)
912 Views
wp35npzdfon4jfgls
Cosmic Ray
Options
A Series & Other Mobile

Today while using my Samsung Galaxy A53 5G (One UI 7.0), 3 of my 4 Google accounts were unexpectedly logged out from the Windows Chrome browser, each at a different time — and always while I was using that account on the phone. All accounts remained signed in on the A53 5G.

Windows Logouts
All 4 accounts were signed in on both the Windows Chrome browser and the A53 5G, and both devices were connected to the same home Wi-Fi network the entire time.

Each time, I received the same security warning on my phone:

"You've been signed out of your account on a Windows device due to suspicious activity."
It also warned that my password might have been stolen (but that doesn't make sense).

Details for each account:

  • Accounts 1 & 2: I was likely using the Gmail app on the A53 5G at the time of logout.
  • Account 3: Logged out immediately after scanning my fingerprint in the Google app while accessing the Account Security page.
  • Account 4: Received the same warning after I manually signed out from Chrome on Windows during a cache clearing.

Strange Cloning of Smartphone Sessions
For all 4 accounts:

  • Every time I use fingerprint authentication in the Google app to access account security, a duplicate smartphone session appears in the device list, labeled "SM-A536B". The current session at the top of the list is labeled "Galaxy A53 5G".
  • However, when accessing the same page via the Chrome browser on Android and a fingerprint scan is required, a “Linux” session appears instead: it updates rather than duplicates after further fingerprint scans, but the current session is still assigned to the topmost smartphone session in the list. Oddly, the “first sign-in date” for that Linux session is months old.
  • All these sessions — smartphone clones, Windows, and Linux — appear with the same city location.

Malware, Session Bugs, or False Alerts?
I’ve scanned the Windows PC using:

  • Windows Defender
  • Another virus scanner
  • A malware scanner

No threats were found.

If this were cookie or token theft, why would the Windows logout happen exactly when I’m actively using the account on the A53 5G phone?

2FA is enabled for all accounts. And I've already changed passwords to force reauthentication for all sessions, and uninstalled Windows browser extensions.

Related Discussions but no connection
Some reddit users report either duplicate sessions on their Smartphones, or Google warning logouts from their Windows browsers, but no one seems to connect both sides of the issue. I haven't found anything in the Samsung forums.

Has Anyone Else Experienced This?

0 Likes
3 Replies
LongHiker
Galactic Samsung Care Ambassador
Options
A Series & Other Mobile

@wp35npzdfon4jfgls I'm confused about the "Windows Chrome Browser" reference.

The Chrome browser on your phone is made by Google. And on your phone it would be the Android version of the Chrome browser. 

0 Likes
wp35npzdfon4jfgls
Cosmic Ray
Options
A Series & Other Mobile

Yes, the windows PC chrome browser is on a windows PC.

There are 2 devices logged into 4 Google accounts. A windows PC and a Samsung a53 5g.

 

The issue is why did some specific interaction with a Google account on the a53 cause each of 3 of the Google accounts to forcefully log out of the Windows PC Chrome browser?

And does it have anything to do with the strange phenomenon where I can create more than 15 open device sessions by triggering the fingerprint sensor in the Google app on the a53,  one new session for each trigger? 

The strangest interaction was the third account when I used the fingerprint sensor to access the Google account on the a53, I immediately got the security alert and forced logout of that account on the Windows PC Chrome browser.

 

0 Likes
LongHiker
Galactic Samsung Care Ambassador
Options
A Series & Other Mobile

@wp35npzdfon4jfgls I'm guessing that this is a Windows issue. You might want to reach out to Google Chrome support. 

0 Likes