Guides

Change passwords after malware

Use a trusted device to recover exposed accounts, replace passwords, review sessions and recovery details, and apply Google's and Microsoft's documented controls.

When malware may have exposed a password, stored login, or active account session, secure the account as well as the computer. Removing a file does not change a stolen password or necessarily end unauthorized access. The task is to recover control, remove access you do not recognize, and protect the routes that could let someone return.

Use a separate trusted device for urgent account work. If you must use the affected computer, establish a supported cleanup or recovery plan before entering replacement credentials there. This guide covers personal Google and Microsoft accounts as examples for Windows and Mac users. Other services have their own controls; work and school accounts need their administrator’s process.

Start with the exposure you can establish

For an infostealer finding, the exposure investigation helps distinguish blocked files, possible execution, accessible data and confirmed account events. Include sessions, app grants and relevant secrets in that assessment; replacing a password answers only part of it.

Record what happened: a confirmed infostealer finding, a password entered into a deceptive page, an unfamiliar security event, or a provider notice about unauthorized changes. Keep the time and affected account privately. Do not assume every unwanted notification means all passwords were stolen, but do not dismiss recorded unauthorized activity because the device now appears quiet.

For the distinction between device symptoms and account exposure, read infostealers and infection diagnosis. An account can need recovery even when a scanner no longer finds the original file.

Reach the provider independently through a known app or its official website. Avoid a password-reset link, phone number, or recovery offer supplied by the suspicious message itself. If you cannot sign in, use the provider’s account-recovery route rather than paying an unsolicited third party to unlock the account.

Choose the order of account recovery

Start with the account that is visibly under attack and the accounts used to recover others. Your main email address often receives password-reset messages; a password manager or account used for single sign-on may also affect several services. Choose around your actual dependencies rather than an arbitrary alphabetical list.

Exposure or dependencyFirst practical actionFollow-up question
Unfamiliar changes in the main email accountUse its official compromise workflowWere recovery details or forwarding changed?
Same password used elsewhereReplace it on each affected serviceDoes each account now have a unique password?
Password-manager access may be exposedFollow that provider’s compromise processWhich stored accounts or recovery routes need attention?
Active sessions may be stolenReview and revoke access through each providerWhat exceptions or delays apply?
Work or school access is involvedNotify the responsible administratorWhich tokens and organization controls need action?

Use a strong, unique replacement password for each affected account. If a password was reused, changing it on only one service leaves the other copies unchanged. Keep a private list of accounts completed and those still pending, without writing actual passwords in the incident notes.

Google: review events, sessions, and account settings

Google’s compromised-account guide describes account recovery, security-event review, device review, and checks for unauthorized changes. From a trusted device, follow its current prompts and report security events that were not yours. Review recovery phone and email details, authentication methods, connected access, and Gmail rules or forwarding relevant to the incident.

For the device view, Google’s session documentation gives the route Google Account > Security & sign-in > Your devices > Manage all devices. Review the details and sign out sessions you do not recognize. Several sessions can belong to one device, and the displayed time can reflect background communication. A repeated device label or a recent time is therefore not a complete compromise verdict.

If a device name has several sessions and you cannot account for them, inspect all of those entries rather than removing one and assuming the rest disappeared. Keep the affected computer out of normal account use while its trust is unresolved.

Google’s password-change instructions explain that changing or resetting a password signs you out in many places, with exceptions for certain verification devices, authorized apps, and some connected devices. Do not assume a password change revokes every session or connected permission. Complete the separate access review.

If you can sign in, the documented password route is Google Account > Security & sign-in > How you sign in to Google > Password. Reauthenticate if asked, enter the unique replacement password, and select Change Password. If you cannot sign in, use the official account-recovery flow instead. Do not repeatedly try a guessed password while unauthorized account changes continue.

Microsoft: recover the account and use sign-out controls

Microsoft’s compromised-account guide provides its sign-in helper and account recovery path. It also says to address malware on the computer before changing a password there. A separate trusted device lets you perform urgent recovery without typing new credentials into a suspect installation.

Follow the provider’s current password-change or reset prompts, then review relevant account settings. Microsoft’s guidance includes connected accounts, forwarding, and automatic replies. An unauthorized forwarding rule can remain a problem even after a password changes, so include mailbox settings in the review when that account was affected.

Microsoft separately documents Sign out everywhere under the account’s Advanced security options. Its current instructions say sign-out can take up to 24 hours and exclude an Xbox console. Handle that exception through the linked Xbox guidance if relevant. Do not promise immediate removal of all access after pressing the button.

These are personal Microsoft-account controls. An organization’s Microsoft 365 access, session revocation, and identity recovery may require its administrator. Removing a device from an inventory is also not a universal substitute for revoking its sessions.

Check recovery routes and stronger authentication

Review whether recovery addresses, phone numbers, passkeys, security keys, or other sign-in methods are yours. Remove unauthorized methods through the provider’s supported process while retaining a recovery route you control. A stronger password has limited value if someone else still controls how it can be reset.

Enable the provider’s available stronger authentication and preserve its recovery information securely. Do not approve an unexpected sign-in prompt simply because you are currently working on account recovery. Keep new backup codes or recovery secrets private and avoid storing the only copy on the device being rebuilt.

Check connected applications and delegated access individually. Revoke anything unauthorized and determine whether a legitimate integration needs to be configured again. This review is broader than signing out browsers, and its controls differ between providers.

If the incident involved payment information or identity documents, use the affected service’s official support route to address that exposure. Preserve useful notices and transaction records. A password update does not reverse an earlier transaction or recover information someone already copied.

Verify account work alongside device recovery

Confirm the intended recovery details and authentication methods, review the provider’s recorded security activity, and track any remaining session-control delay. Record what you actually completed rather than treating the absence of new alerts as proof that all access ended.

Return to device recovery before signing in again on the affected computer. Check that its cleanup, protection, and updates are resolved, and bring back browser extensions and settings deliberately. Account recovery and file restoration have different acceptance checks.

This guide was researched and edited on 6 October 2026 using official Google and Microsoft documentation. It reports no site-run account compromise test, and the provider examples should be checked against the current interface when used.

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy