Glossary

Infostealers: stolen data and browser sessions

Learn what infostealer malware takes, why saved passwords and session tokens matter, and how device cleanup differs from securing exposed accounts and secrets.

Definition

An infostealer is malware designed to collect and steal sensitive information from a device, such as saved credentials, browser session data, documents, or other accessible secrets.

Also called: information stealer, information-stealing malware, credential stealer, stealer malware

Information theft is the purpose

An infostealer collects sensitive information accessible on a device and attempts to send it to an attacker. The category describes the theft objective; it does not identify one file format, operating system, or delivery method.

The information can already be present. A saved browser password or accessible document may be targeted even if it was never typed while the malicious program was running. That is the main distinction from interpreting every theft as keyboard recording.

Consider an illustrative fake utility that runs once, collects accessible account data, and stops. A later scan might address remaining code, but it cannot take back data already transferred. The event’s duration and visible symptoms are therefore different questions from the exposure it created.

Microsoft’s February 2026 infostealer research describes observed campaigns across platforms and delivery channels. Infostealer is a cross-platform concept, although any particular sample has its own targets and requirements.

What an infostealer may collect

Capabilities differ between families and versions. Do not assume that every detected stealer collects every item listed below.

InformationWhy it can matterRelevant recovery question
Saved credentialsMay allow new account sign-insWhich credentials need changing or replacing?
Session cookies or tokensMay represent an existing signed-in sessionHow does the provider revoke that access?
Documents and application dataMay expose private or work informationWhat disclosure needs assessment?
Wallet or developer secretsMay grant access beyond an ordinary passwordWhich keys or credentials require specialist recovery?
Device informationCan describe the environment to an attackerWhat additional activity needs investigation?

Microsoft’s Lumma Stealer analysis documents collection of browser data, documents, wallet information, and other application data. It is a concrete example of capabilities, not a claim that every infostealer works exactly like Lumma.

The useful exposure assessment combines the detected threat’s documented behavior, what was accessible, and whether it executed. A family name alone cannot establish exactly which data left your device.

Why a stolen session differs from a password

After signing in, a service commonly maintains a session so that you do not enter your password for every action. Session cookies or tokens can represent that already-authenticated access.

If a service accepts a stolen token, an attacker may be able to reuse the session without performing a fresh password-and-MFA sign-in. That possibility does not make multifactor authentication useless. It explains why recovery must consider existing sessions as well as new-login credentials.

Changing a password, clearing local browser data, and revoking a session are different actions. Their effect depends on the service. Deleting a cookie on your device does not tell the provider to reject a copy already obtained elsewhere.

Google’s device and session guidance shows how its users can review sessions and sign out of them. Other providers have their own controls. Follow the affected provider’s recovery process rather than assuming a password change automatically ends every type of access.

Infostealer, keylogger, and spyware compared

A keylogger records input. An infostealer can collect stored information directly. A malicious program may do both, but a password exposed through saved browser data does not prove that keyboard input was recorded.

Spyware is the broader monitoring and unauthorized collection concept. A Trojan describes a concealed malicious purpose behind an apparently useful program. An infostealer can also fit those descriptions.

Stolen access may enable a later intrusion or ransomware event. That is a possible consequence, not an inevitable outcome for every infection. Keep confirmed actions separate from capabilities and potential follow-on risks.

How a useful-looking download can create exposure

Stealers can arrive through deceptive applications, messages, or prompts that claim a problem must be fixed. Microsoft’s 2026 research includes fake software and misleading instructions as delivery routes. A polished page and a familiar application’s name do not establish that the downloaded file is authentic.

An unsolicited verification or repair page asking you to paste commands into a terminal deserves independent verification. Running a command is execution, even if the page calls it a check. Do not follow those instructions merely to make the page proceed.

The incident question is whether code executed, not just whether a file reached the downloads folder. A stopped download and a running stealer require different exposure assessments.

What to do with a stealer detection

The fuller infostealer investigation turns a finding into an execution timeline, a private exposure inventory and separate device/account recovery records. Use it when you need to decide what a particular alert supports and which access may need revoking.

Read the exact detection, affected path, time, and completed action. Keep isolated items in quarantine while the event is investigated. Record whether the file ran and which accounts or sensitive applications were in use.

Use the security product’s supported response and the site’s Windows scanning route where applicable. A scan result addresses the device within that scan’s scope. It does not revoke remote access obtained with stolen data.

For a work or school device, report the event to IT promptly, including relevant accounts and data. Avoid sharing private files or complete credential records with public analysis services. The responsible team can assess execution and exposure through an appropriate process.

Secure accounts from a trusted device

When there is credible exposure, use a separate trusted device and follow affected providers’ recovery steps. Prioritize the email or identity account that can reset other accounts. Review account activity, sessions, recovery settings, and connected applications alongside changing compromised credentials.

Google’s compromised-account guidance provides one provider’s workflow. It illustrates why recovery extends beyond a new password. For work credentials, developer secrets, or wallet keys, use the responsible service or security team’s process; do not assume every secret can be handled through an ordinary account-password screen.

Device cleanup and account recovery need both outcomes recorded. A cleaned computer can coexist with exposed access, while secured accounts can coexist with unresolved malicious code. The incident is understood when those scopes are assessed together and remaining uncertainty is explicit.

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