Infostealers: investigate exposure
Assess an infostealer finding by execution and accessible data, then coordinate device remediation, account sessions, exposed secrets and recovery evidence.
An infostealer investigation has two connected questions: did unwanted code execute on the device, and what information or access might already be exposed? Removing a detected file addresses one part of that event. It cannot take back a password, session token or private document already copied elsewhere.
Start urgent account recovery from another trusted device when exposure is credible; do not wait for every scan to finish before contacting the affected provider through a known route. This article covers investigation and recovery decisions for personal Windows PCs and Macs. Work accounts, organizational devices, developer secrets and wallet keys also need their responsible administrator or provider. Use the glossary definition for terminology rather than treating the threat name as a complete diagnosis.
Establish what the finding actually describes
Open the installed security product independently. Preserve the complete detection name, affected item or path, time, recorded action and completion state. Was the finding made on a downloaded archive, an extracted program, a running process or a later scan of old files? A detection can establish something about that item without establishing every action it performed.
Record what you know about execution. “The browser blocked the download and I never opened it” differs from “I ran an installer and later received a finding.” If you cannot determine whether code ran, retain that uncertainty and get appropriate help. Do not execute the item again, restore it from quarantine or recreate a deceptive command prompt to make the history clearer.
| Evidence available | What it supports | Next priority |
|---|---|---|
| Blocked download with no known execution | A prevented attempt involving that item | Verify the action and leave the item isolated |
| Suspicious installer or pasted command ran | A possible execution event needing assessment | Stop sensitive use; assess the device and exposure |
| Product identifies stealer activity in a process | A stronger lead about activity on the device | Supported remediation and prompt account/secret recovery |
| Provider records unfamiliar access or changed recovery details | An account incident | Recover access independently, even without a device finding |
| A later scan is clean | That check found nothing within its scope | Do not treat it as revocation of stolen access |
If remote control or destructive activity is continuing, use urgent triage before ordinary comparisons. On managed equipment, tell IT what ran, when and which accounts or information were involved. Keep logs, screenshots and paths private where they reveal sensitive material.
Build a timeline without assuming every capability occurred
Include the source of the download or prompt, what you opened, any permissions you granted, the security finding and subsequent account alerts. A useful timeline separates observed events from assumptions. Merely receiving a phishing email does not establish execution, and a stealer label alone does not identify exactly what left the device.
Microsoft’s February 2026 research describes Windows and Mac-related delivery through deceptive software and copy-paste prompts, with differing targets and implementation. That is a reason to examine the actual item and platform, not to apply one family’s behavior to every finding.
Microsoft’s May 2025 Lumma analysis documents browser/application data theft and the possibility of delivering additional malware. This is a specific researched example. It does not prove that your file is Lumma, that all of its capabilities occurred, or that a later account incident has only one possible cause.
Keep the exact threat name and supported product explanation for qualified assessment. Do not infer a campaign from a copied filename or a screenshot on a forum. Existing public reports provide context; submitting a private sample or full credential record is a separate disclosure decision and is not required by this guide.
Inventory access and data that could matter
From a trusted device, make a private inventory of relevant accounts and sensitive applications used or accessible on the affected device. Record account names and categories, not the secrets themselves. The purpose is to prioritize recovery, not create a new unprotected list of passwords.
| Potentially exposed category | Recovery question | Why device cleanup alone is insufficient |
|---|---|---|
| Email or central identity account | Can you regain control and correct recovery/access settings? | It may enable access to other accounts |
| Passwords stored or used in affected apps | Which credentials need replacing, including reused ones? | A copied password can be used elsewhere |
| Signed-in sessions or tokens | Which provider controls revoke current access? | Deleting the local copy does not revoke another copy |
| Authorized third-party apps | Which grants remain and are they intended? | Their access can be separate from a password |
| Developer, cloud or wallet secrets | Who can revoke, rotate or recover the exact secret? | An ordinary password screen may not control it |
| Private documents or work data | Who needs to assess disclosure and resulting harm? | Deleting malware does not recall copied information |
Not every infostealer collects every category. Exposure depends on capabilities, execution, accessible data and available evidence. Distinguish “could have been accessible” from “confirmed copied” in the record. If a crucial answer remains uncertain, explain that to the responsible provider or incident responder rather than fabricating certainty.
Recover accounts through their own controls
Prioritize the account that controls password resets or other account access. Use a known app, bookmark or independently reached official address on the trusted device. Google’s compromised-account guidance illustrates reviewing account activity, recovering access and correcting security details. Other providers have their own process; menu names and revocation behavior differ.
Change exposed credentials and any reused copies through the relevant services. Review recovery email/phone details, security methods, signed-in access and connected apps as the provider instructs. A password replacement, multifactor-authentication setup and session revocation are different actions; record which ones were completed.
For Google, the devices and sessions page explains that multiple sessions can belong to one device or several. Review details and sign out unrecognized access using its controls; signing out every session with a device name may be needed to address that named access. Its activity time can include background communication, so a recent timestamp alone is not proof of an intruder.
Use the account-recovery guide for the broader order of work. Do not assume clearing browser cookies ends a provider’s existing sessions. If business, cloud, financial or wallet access is implicated, contact the responsible team or provider through a trusted channel for that access type. Never share a recovery seed with someone claiming to “clean” a wallet.
Remediate the device and address the original entry route
Keep suspicious items closed and quarantined. On Windows, use scan and completed-action checks to review the active product’s findings. On Mac, use the platform investigation and the exact warning or product action. Windows-only scanners and cleanup helpers should not be presented as Mac instructions.
An installed program, extension, persistence mechanism or approved remote-control session needs its own assessment. Removing the downloaded installer is not the same as removing everything it installed. Get qualified help for recurring detections, continuing access, uncertain system damage or an execution event whose scope you cannot establish. Recovery or rebuilding may be appropriate, but it needs a plan for wanted data and the actual incident.
Identify the entry route so restored use does not repeat it. Safer downloads covers independent publisher checks; email verification covers suspicious messages. Do not reproduce a ClickFix-style instruction by pasting the command again. A browser extension offered as prevention is not a substitute for assessing code that already ran.
Record device and access outcomes separately
Before returning to sensitive work, record what the device assessment covered, which actions completed, and what remains unresolved. Keep a separate account/secret checklist with provider confirmations and remaining access questions. Normal browsing and zero new detections are useful observations, but they do not prove every prior disclosure was recovered.
Continue reviewing the affected services’ activity through their normal controls and seek help for new access or altered recovery settings. Avoid promising that removing a particular file guarantees no further misuse. This article is researched guidance. No stealer sample was executed, private data uploaded, account changed or independent detection test performed to prepare it.
Sources & documentation
Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.
- Microsoft Security: Infostealers across platforms (February 2026)
- Microsoft Security: Lumma Stealer capabilities (May 2025)
- Google Account Help: Secure a hacked or compromised account
- Google Account Help: Review devices and sign out of sessions
- Microsoft Support: Protection History in Windows Security
- Apple: Mac app warnings and safely opening downloaded software