Skip to the stories
AI & ML

Remus Stealer’s Gmail Persistence Claims Remain Unverified

  • David Williams
  • 435 reads

Remus advertises mailbox access that survives password changes, but available evidence doesn’t prove it. Account recovery still requires checking sessions, apps and devices.

Remus Stealer’s Gmail Persistence Claims Remain Unverified

Changing a password may not finish recovering an account after an infostealer infection. Remus Stealer’s developers claim their service can keep reading Gmail even after a password change and session revocation. The available evidence, however, doesn’t show that the feature works under those conditions. For Gmail users, the practical lesson is to check the account and the infected device together.

Threat intelligence company Hudson Rock examined Remus’s promotional material and spoke with its developer and a person who described using the feature. The report documents what the service advertises, but it doesn’t include a technical examination of the feature or a controlled test after account recovery. It also doesn’t establish a Gmail vulnerability.

What the service claims to do

In an announcement for version 1.3.9, Remus promoted a way for operators to open compromised Gmail mailboxes from the service’s dashboard. Screenshots show message lists and individual emails, alongside a “Mail” option associated with compromised devices.

The developers also claimed that operators could intercept email verification codes without collecting browser cookie files, retain mailbox access after password changes and session revocation, and share access with other operators through links. These are claims made by the seller of a criminal service. Screenshots of an interface can show how a product is presented, but they don’t prove what happens behind it or whether the displayed mailbox remains accessible after an account is secured.

When Hudson Rock asked how the feature worked, the developer described interacting with browser memory and said the malware executes and exits. The developer also claimed Remus avoids Google’s anti-fraud checks, but didn’t provide the technical details needed to assess that claim. Without those details, it’s unclear whether the feature depends on an active browser session, stored credentials, an account authorization, or some other path.

What the reporting establishes

A person who had publicly endorsed the feature told Hudson Rock that mailbox access continued after the browser was closed, a session reset, and a Google password change. That account is relevant, but it isn’t a controlled demonstration. The correspondence doesn’t specify which sessions were reset, what account settings were in place, or how much time passed between the password change and the later access.

The person’s independence wasn’t established, either. Hudson Rock says it didn’t reverse engineer the feature or validate access in a controlled post-recovery test. That leaves a gap between the service’s sales pitch and a verified technical finding. The report supports the conclusion that Remus is marketing mailbox access; it doesn’t establish persistent access after a thorough recovery.

That distinction matters for anyone assessing the risk. A screen showing messages could reflect access that was already available on a compromised device or through an existing authorization. It doesn’t, by itself, identify the mechanism or prove that access survives every step a user takes to secure an account.

Why a password change may not be enough

Google’s documentation says password changes ordinarily invalidate access tokens and refresh tokens used by applications with Gmail permissions. These tokens let an application make authorized requests without asking for the password every time. A stolen token alone therefore doesn’t show that Remus can continue accessing Gmail after a password change.

Account recovery can still involve more than invalidating tokens. A compromised device may retain access to an open session, and account settings or connected applications can provide other routes to information. That’s why checking signed-in devices and applications matters alongside changing the password. The Remus report doesn’t establish that the service can evade those protections; it leaves the central technical claim unresolved.

Steps to take after suspected infostealer access

If you suspect an infection or unauthorized Gmail access, use a separate, trusted device to secure the account. Disconnect the suspected infected device from the internet and remove the malware before using it to sign in again. A password change made from a compromised device may expose the new credentials to the same threat.

Change your Google password, review recent security events and signed-in devices, and remove access you don’t recognize. Check connected applications as well as device sessions. In Gmail, inspect forwarding rules, filters, delegated mailbox access and remote mail access settings for changes you didn’t make. Review your recovery email, recovery phone number and verification methods, too.

Run trusted security software on the affected device. Google also identifies resetting a computer and reinstalling its operating system as an option when dealing with harmful software. If the mailbox is used to sign in to or recover other accounts, check those accounts as well, especially if you find unfamiliar verification codes or password reset messages.

Email access can create a path to other services because inboxes receive recovery links and verification messages. Still, the Remus screenshots don’t demonstrate a general bypass of multifactor authentication, the ability to send mail, or complete control over every account associated with a Gmail address.

For now, Remus’s claim that it can maintain Gmail access after account recovery remains unverified. The useful response is to secure the account, inspect its permissions and settings, and clean the device that may have exposed it. A technical analysis or controlled test would be needed to establish how the feature works and whether its claimed persistence holds up.

Source: David Williams · www.malwarebytes.com

From the same set