Technology Popular

Changing your Gmail password does not lock an attacker out

The order of operations is the whole thing. Change the password on the infected machine and you have handed the attacker a fresh key, not taken one away.

Changing your Gmail password does not lock an attacker out

Changing your Gmail password does not, on its own, make the account safe. If the computer or phone you use is infected with malware, criminals can still get in afterwards.

Google has issued advice on this following renewed concern about a data-stealing malware referred to as Remus Stealer.

What a session token is, and why it defeats a password change

A session token is a digital pass your browser holds so you do not have to type your password on every visit. It is what keeps you signed in.

Because it works instead of the password, stealing it bypasses the password entirely — and a new password does not invalidate a token an attacker already holds unless the sessions are also ended.

The trap is sharper than that. Google says that when you change the password from an infected device, the new session token issued at that moment can be stolen too.

So the single action most people take first — reset the password on the machine in front of them — can hand the attacker a fresh key rather than take one away.

A new password, a new stolen token
Reset it on the infected machine and the fresh session token leaks too. Graphic: Tech BD.

Google's position on whose fault it is

A Google spokesperson told the technology outlet Cybernews that stealing session tokens from personal devices is not new, and that there is no security flaw in Gmail or Google involved.

That is a fair description of the mechanism. The weakness is on the device, not in the mail service — which is also why no amount of waiting for Google to patch something will help.

The makers of Remus Stealer go further and claim they can reach a Gmail inbox even after every account recovery step has been completed. Security researchers have not found sufficient evidence for that claim.

Treat it as unproven marketing by criminals, which is what it currently is — while noting that the underlying technique it exaggerates is real.

What Google says to do, in order

The sequence matters more than any individual step.

1. Remove the malware completely from the infected device. Nothing after this works until this is done.

2. From a different, clean device, change the password and run Google's Security Checkup.

3. Open Google's device management page and look at which devices have your account signed in. Sign out any you do not recognise — this is the step that kills stolen tokens.

4. Turn on Enhanced Safe Browsing in Chrome for stronger ongoing protection.

Where this fits

We covered the scale of this trade on 3 November: billions of stolen session cookies circulating from infostealer infections. This is the same problem arriving as practical guidance rather than a statistic.

Two further checks are worth doing while you are in there. Look at third-party apps with access to the account and remove anything you do not actively use, because an old integration is a second door with its own key. And remember that two-factor authentication does not stop this: a stolen session token was issued after the second factor was satisfied, so it sails straight past it.

The useful habit to take from it is small. When an account is compromised, do not start by changing the password. Start by asking which machine is dirty — because every other step is wasted until that one is answered.

Source: Prothom Alo

Written by

Tech BD

Tech BD is an independent technology publication based in Dhaka, published in English and Bangla. Articles appear under the masthead rather than under individual bylines; corrections and source questions reach the editor at info@tech-bd.com.