Cybersecurity

Remus Stealer's Gmail Claim: What Is Verified and What Ends Access

The malware's sellers say mailbox access survives a password change; the security firm that examined the pitch says it never tested that.

11 min read
Silver laptop keyboard in the foreground, with its screen showing colorful lines of source code in a dark editor and a blurred black mug behind.
Image by StockSnap from Pixabay

Developers of the Remus infostealer advertise a Gmail feature they say survives password changes and session revocation. Hudson Rock, which reported the pitch, did not test it and does not call it a proven Gmail flaw. Google's own past statements show that a password change alone is not a dependable cleanup step after an infection.

The sellers of an infostealer called Remus Stealer say a feature in the product keeps a victim's Gmail mailbox readable after the victim changes the password and revokes sessions. No independent test has shown that this is true. Hudson Rock, the threat-intelligence firm that reported the advertisement on Nov 9, 2026, says it did not test the claim and does not classify it as a demonstrated Gmail zero-day.

The distinction matters because a password reset is the reflex after a suspected break-in. The record suggests it is a necessary step but not a sufficient one when malware is on the device. Google said in 2024 that stolen browser-session tokens are not immediately invalidated by a password change, and that signing out of sessions is what revokes them. The order of the cleanup steps therefore carries more weight than the headline claim does.

What the Remus sellers are claiming

Hudson Rock examined the announcement of Remus version 1.3.9 and contacted both the developer and a person who had publicly endorsed the new feature, according to its report. The feature lets operators open a compromised Gmail mailbox from the malware's dashboard. The advertisement says password changes and session revocation do not cut off access, and that access to a mailbox can be shared through links.

Hudson Rock describes the advertised capability as interception of email codes without collecting browser cookie files. Screenshots it reviewed show a webmail-style interface listing senders, subjects and message previews, with a search box. Outlets that relayed Hudson Rock's findings put the price at about $1,000 a month on an Enterprise subscription.

Two witnesses, both interested parties

The developer told Hudson Rock that the feature works by interacting with browser memory and that the malware runs and then exits. Tom's Guide reported that no technical detail accompanied the explanation. That is an unverifiable statement from someone selling the product.

A self-described customer said mail stayed accessible after the browser was closed, sessions were reset and the Google password was changed. Hudson Rock says the correspondence does not document which sessions were reset, which account settings were involved, or when the password change and the later access happened. Coverage varies on the wording: Neowin says access tokens were reset, while Malwarebytes says a session reset. Because Hudson Rock found the details undocumented, no specific recovery step can be treated as having taken place.

What Hudson Rock did and did not verify

Hudson Rock did not run a controlled test in which a newly delivered email appeared in Remus after a password change and the removal of sessions and app access. Malwarebytes reports that Hudson Rock states its report includes neither reverse engineering of the malware nor controlled validation after recovery. What exists is an advertisement, dashboard screenshots and correspondence with two interested parties.

Hudson Rock offers a hypothesis rather than a finding. Remus may acquire or establish reusable authorization while it has access to a signed-in browser, and a remote component could then request mail after the local program exits, for as long as the service honors that authorization. The firm has not identified the actual mechanism.

The report also separates two claims that headlines tend to merge. Access that continues after the malware exits could be explained by reusable authorization. That does not show access survives a proper recovery. The first is plausible on Hudson Rock's reading; the second has no supporting test.

Where coverage outran the evidence

Several outlets rewrote the single Hudson Rock report, so Malwarebytes, CyberInsider, Neowin, Cybernews, Tom's Guide and others do not amount to independent confirmation. Yahoo Tech's summary of a New York Post story states flatly that a password change will not prevent access. A Cybernews headline calls the issue a Google "zero-day." Neither framing matches Hudson Rock's cautious report or Google's response.

Hudson Rock itself sells infostealer-exposure services, so it has a commercial interest in the subject. Its report is nonetheless restrained about what it could establish. Tom's Guide suggested that the Enterprise price means most people are safe, but that is the outlet's opinion, not evidence; an infected person's mailbox could be targeted regardless of the tier a buyer pays for.

What Google has said

A Google spokesperson told Cybernews that session-theft attacks involving infostealers are "not new" and that "no Gmail or Google vulnerability" is involved. IBTimes and other outlets repeated the statement, so it traces to one outlet and is not independent confirmation. Google also said it routinely upgrades its defenses and automatically secures accounts when it detects suspicious activity.

The same spokesperson said users can invalidate stolen sessions by removing the malware and revoking active sessions, according to Cybernews. The reporting also advises reviewing forwarding rules, filters, recovery options and third-party app permissions. Google's own help pages could not be retrieved for this article, so its documentation is known here only through Hudson Rock's and Malwarebytes' descriptions.

Why a password change may and may not matter

Hudson Rock says Google's documentation states that password changes ordinarily revoke both access tokens and refresh tokens that carry Gmail permissions. Malwarebytes draws the conclusion that token theft alone therefore does not establish that Remus can persist after a password change. Both points rest on documentation that this article could not check directly.

A separate Google position dates from January 2024. Google said then that it is not a bug for stolen tokens to remain valid after a password change, because that behavior is part of how users stay signed in when they change a password, as TechTarget reported. Users can sign out other sessions at g.co/mydevices, Google said, and signing out of the affected browser revokes the session cookies.

One more distinction keeps the picture straight. The Mallory.ai aggregator, a weaker source, lists Remus as stealing saved passwords, cookies, session tokens and browser encryption keys, among other data. The Gmail feature, however, is advertised specifically as working without cookie files. Those descriptions are not contradictory, but they refer to different capabilities.

The 2023–24 precedent: cookies that came back

Remus is not the first infostealer to be marketed on this idea. In late November 2023, the Lumma and Rhadamanthys stealers claimed they could restore expired Google authentication cookies, according to BleepingComputer. CloudSEK later reported that stealers abused an undocumented Google OAuth endpoint called MultiLogin, extracting token and account-ID pairs from Chrome profiles to regenerate cookies that stayed effective after a password reset.

CloudSEK, a security vendor that reverse-engineered the malware, added a caveat: regeneration after a password reset works only once. It advised logging out of all sessions and revoking suspicious connections. Google disputed part of the account, saying the API manages signed-in sessions in Chrome and does not allow revoked or signed-out sessions to be revived, as TechTarget and 9to5Google reported.

The episode cuts both ways. Sellers' claims about Google sessions were partly borne out in 2023–24, so dismissing Remus's pitch outright would be unsupported. Yet Google's account was that sign-out and revocation do end such sessions. Malwarebytes' 2024 guidance followed that logic: sign out of all browsers, reset the password, then sign back in to generate fresh tokens.

Browser defenses and their limits

Chrome's App-Bound Encryption debuted in Chrome 127 in July 2024 to protect cookies from infostealers on Windows. SpyCloud independently confirmed a bypass in the Phemedrone stealer and listed many families that bypassed it, including Lumma, Vidar and StealC. Elastic Security Labs observed bypass code in StealC and Vidar around Sept 20, 2024.

The cycle continued in 2026. CSO Online reported a bypass in the VoidStealer malware on Mar 23, 2026, and Kaspersky described a debugger-based technique that extracts the master key from memory. The Mallory.ai page says Remus and Lumma use impersonation of a SYSTEM token as one way around the protection, though that source is an aggregator and its claim awaits confirmation from underlying vendor reports.

Device Bound Session Credentials

The newer defense is Device Bound Session Credentials, or DBSC. According to Help Net Security, it ties a session to a hardware-held key, a TPM on Windows or the Secure Enclave on macOS, that cannot be exported. Cookies become short-lived and cannot be renewed without that key, so a stolen cookie should lose value quickly. Public availability began in Chrome 146 on Windows.

Reports on rollout differ. Cyber Security News says a gradual rollout to Workspace and personal accounts began May 25, 2026. NewsBytes says it is automatically on from June 1, 2026 for Chrome 146 and later on Windows. Corbado, which sells passkey products, says that as of Oct 3, 2026 the rollout covers Windows and macOS, while Linux, Android and iOS are unsupported. The sources disagree on the macOS Chrome version (147 per Corbado, 148 per NewsBytes), so that detail is unresolved.

No source addresses whether Remus's Gmail feature works against sessions bound by DBSC. How common the problem is also remains unclear. NordVPN researchers analyzed more than 52.4 billion cookies in infostealer logs from June 2025 to June 2026 and found that a small percentage were still active, according to TechNewsWorld's account of the study.

Key dates in the Remus, cookie-theft and Chrome-defense story, 2024–2026
Date Event
Jul 2024 Chrome 127 ships App-Bound Encryption
Jan 2, 2024 Google says signing out revokes stolen sessions, in response to the cookie-revival reports
Mar 2026 VoidStealer bypass of App-Bound Encryption reported
Apr 2026 DBSC becomes publicly available in Chrome 146 on Windows
May 25, 2026 Gradual DBSC rollout to Google accounts begins
Nov 9, 2026 Hudson Rock publishes its report on Remus 1.3.9
Nov 11, 2026 Malwarebytes publishes its article on the claim

What actually ends an attacker's access

No test of Remus specifically exists, so the steps below reflect what Google and security outlets recommend for infostealer incidents in general. The common thread is that the infected device comes first. Cybernews reports a security-vendor view that malware still running when a password is reset can capture the new session, though the attribution of that point, to Google or to Cybernews's own analysis, is unclear.

  1. Clean the infected device. Malwarebytes advises running trusted security software, and notes that Google lists resetting and reinstalling the operating system as an option.
  2. Revoke active sessions, for example by signing out other devices at g.co/mydevices, as Google has said users can do.
  3. Change the password from a device known to be clean, which is the advice Cybernews gives.
  4. Remove unfamiliar third-party app permissions and review forwarding rules, filters and recovery options in Gmail.
  5. Check other accounts that depend on the mailbox for sign-in or recovery, especially if unfamiliar verification or reset emails appear, as Malwarebytes suggests.

The order reflects the mechanics described above. A password change addresses the credential and, per Google's relayed documentation, Gmail-scoped app tokens. Sign-out addresses browser sessions. Removing the malware keeps a fresh login from being copied again. Skipping the first step leaves the other two exposed.

What the claim means, and what to watch

The Remus story is best read as an advertisement under scrutiny, not a confirmed breach of Gmail. The sellers say their feature outlasts a password change; the only outside account supporting it is an anonymous customer's. Google says no Gmail or Google vulnerability is involved. Hudson Rock, the firm that brought the pitch to light, stops short of both endorsing and refuting it.

The practical lesson comes from the older record rather than from Remus. Stolen sessions can outlast a password change unless they are signed out, and infostealer makers have repeatedly found ways around browser protections. Two developments will settle more than any advertisement: an independent controlled test of the Remus feature, and evidence on whether hardware-bound sessions in Chrome blunt it.

Frequently asked questions

Does changing your Gmail password lock out an infostealer?

Not reliably on its own. Google said in 2024 that a password change does not immediately invalidate stolen browser-session tokens, and that signing out of sessions revokes them. According to Hudson Rock's reading of Google's documentation, password changes do revoke Gmail-scoped app tokens. Cleaning the device and revoking sessions are the steps that close the gaps.

Is the Remus Gmail feature a Google zero-day?

That has not been established. Hudson Rock says it does not classify the claim as a demonstrated Gmail zero-day, and a Google spokesperson told Cybernews that no Gmail or Google vulnerability is involved. The zero-day label appeared in a Cybernews headline.

Has anyone confirmed that Remus keeps Gmail access after a password reset?

No independent confirmation exists. Hudson Rock did not run a controlled test, and its report includes no reverse engineering. The supporting account comes from the developer and one self-described customer, whose details Hudson Rock says are not documented.

What should someone do after an infostealer infection?

Reports citing Google and Malwarebytes advise removing the malware first, using trusted security software or an operating-system reset. Then revoke sessions at g.co/mydevices, change the password from a clean device, and review app permissions, forwarding rules, filters and recovery options. Accounts that rely on the mailbox for recovery should be checked too.

Do Chrome's newer protections stop stolen cookies?

They are designed to blunt cookie replay. Device Bound Session Credentials tie sessions to a hardware-held key that cannot be exported, and the rollout covers Chrome on Windows and, per Corbado, macOS. Earlier protections such as App-Bound Encryption were bypassed by several stealers, and no source says whether Remus works against DBSC-bound sessions.

Sources (24)

  1. Remus Stealer Markets Persistent Gmail Access: Hudson Rock Investigates , Hudson Rock (infostealers.com) (2026-11-09)
  2. Remus malware claims Gmail access even after you change your password , Malwarebytes (2026-11-11)
  3. A week in security (November 2 - November 8) , Malwarebytes Labs (2026-11-09)
  4. Remus Stealer advertises Gmail access that survives password changes , CyberInsider
  5. Google's "zero-day": Attackers say they have access to Gmail even after password change , Cybernews
  6. Google Password Changes May Not Be Enough to Stop Gmail Hackers: Researchers Alert , IBTimes Singapore
  7. Dangerous new Gmail exploit lets hackers read your emails for a monthly fee of $1,000 — and it even works after a password reset , Tom's Guide
  8. Remus malware claims to retain Gmail account access even after a password change , Neowin
  9. Google's Gmail users warned of new hacking threat , Yahoo Tech
  10. Remus , Mallory.ai
  11. Malware abuses Google OAuth endpoint to 'revive' cookies, hijack accounts , BleepingComputer
  12. Compromising Google Accounts: Malwares Exploiting Undocumented OAuth2 Functionality for session hijacking , CloudSEK
  13. Google, researchers in dispute over account hijacking attacks , TechTarget
  14. New malware restores cookies to break into your Google Account [U: Google responds] , 9to5Google (2024-01-02)
  15. Info-stealers can steal cookies for permanent access to your Google account , Malwarebytes
  16. How Infostealer Malware Bypassed Chrome's App-Bound Cookie Encryption , SpyCloud
  17. Katz and Mouse Game: MaaS Infostealers Adapt to Patched Chrome Defenses , Elastic Security Labs
  18. Chrome ABE bypass discovered: New VoidStealer malware steals passwords and cookies , CSO Online (2026-03-23)
  19. How VoidStealer bypasses Chrome's protections to hijack sessions and steal data , Kaspersky (2026-05-06)
  20. To counter cookie theft, Chrome ships device-bound session credentials , Help Net Security (2026-04-10)
  21. Google Chrome's Device-Bound Session Credentials Now GA to Block Account Takeovers , Cyber Security News
  22. Device Bound Session Credentials (DBSC) explained , Corbado
  23. Google auto-enables device bound session credentials in Chrome on Windows , NewsBytes
  24. Billions of Stolen Browser Cookies Expose Users to Account Hijacking , TechNewsWorld

Share this article

Back to list