Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Stealer
Cyber Security

Stealer

← Back to Glossary
By NHI Mgmt Group Updated October 30, 2026 Domain: Cyber Security

A stealer is malware built to collect sensitive information from an endpoint and send it to an attacker. Typical targets include browser passwords, session cookies, API tokens, crypto wallet data, and saved credentials. Unlike ransomware or destructive malware, its main goal is theft, usually with minimal noise and fast exfiltration.

What Makes a Stealer Different from Other Malware

A stealer is built for speed, secrecy, and theft rather than destruction. That design matters because it targets data that is immediately usable by an attacker, including browser-stored passwords, active sessions, API tokens, wallet material, and other authentication artefacts. Even when the endpoint appears to keep working normally, the attacker may already have what they need to impersonate the user or pivot into connected systems.

The key distinction is intent. Many malware families try to lock systems, disrupt services, or maintain persistence. A stealer usually aims to take something valuable and leave quickly, which makes it especially effective in environments where stolen browser state or saved secrets can be reused outside the original device.

What Stealers Commonly Collect

Stealers are typically interested in anything that can be replayed, sold, or used to escalate access. Browser passwords and cookies are especially attractive because they can bypass the normal login journey, while API tokens and saved credentials can expose cloud consoles, developer tools, messaging platforms, and internal applications. Crypto wallet data is also a frequent target because it can convert directly into financial loss.

Collection is often broad rather than selective. Many stealers enumerate local files, browser profiles, password stores, and application directories in search of whatever sensitive material is present. The operational danger is that one compromised endpoint can yield access to many unrelated services if secrets are reused or poorly isolated.

How Stealers Steal Access Without Obvious Noise

Stealers are dangerous because they often abuse legitimate user context. If malware can read a browser profile, session cache, token store, or locally saved secret, it does not need to defeat stronger authentication controls in real time. It can simply export the material and let the attacker replay it elsewhere, sometimes long after the original infection is removed.

This is why the fallout is often broader than the initial endpoint compromise. A stolen session cookie may act like a live login, and a stolen API token may let an attacker script actions directly against a service. The loss is not only data exposure, but also delegated access, trust, and continuity of identity state.

Why Stealers Matter for Detection and Recovery

Stealer investigations should focus on both the infected endpoint and the accounts or services the endpoint could reach. Endpoint telemetry may show suspicious archive creation, browser profile access, unusual child processes, or outbound exfiltration, but the more important question is which credentials, tokens, sessions, or keys may now be compromised. If compromise is confirmed or strongly suspected, organisations should treat the incident as an access event, not just a malware cleanup.

Recovery often requires more than reimaging the device. Credentials and sessions exposed during collection may need to be revoked or rotated, and downstream systems should be reviewed for suspicious logins or abuse from unfamiliar locations. Where browser cookies or long-lived tokens were harvested, attackers may continue to use them until they expire or are invalidated.

Risk and Threat Considerations

Stealers create a high-consequence exposure because the stolen material is often immediately reusable. The attacker does not need to break a password policy or exploit a fresh vulnerability if the endpoint already contains active sessions, stored secrets, or authentication material that can be replayed elsewhere.

Failure mechanism: The malware extracts credentials or session artefacts from the local environment, then transfers them to an attacker who can use them for account takeover, lateral movement, or direct service abuse.

Impact: Organisations can lose access continuity, see unauthorised actions under trusted identities, and face wider compromise if reused secrets unlock additional systems or cloud services.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKT1555 — Credentials from Password StoresCovers stealing saved secrets and browser-stored credentials from endpoints
T1528 — Steal Application Access TokenDirectly maps to theft of session cookies and API tokens used for replay
Recommendation — Monitor endpoints for credential-store access and hunt for follow-on account abuse. Detect token theft indicators and revoke exposed sessions quickly.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementAuthenticator lifecycle applies when stealer malware exposes passwords, tokens, and related secrets
AU-6 — Audit Record Review, Analysis, and ReportingSupports review of suspicious logins and use of stolen credentials after compromise
SI-3 — Malicious Code ProtectionStealers are malware, so this control supports prevention and detection on endpoints
Recommendation — Rotate exposed authenticators and invalidate compromised sessions promptly. Correlate authentication logs for anomalous use of potentially stolen secrets. Deploy malware defenses that block or flag stealer execution and exfiltration.
CIS Controls v8CIS-10 — Malware DefensesAddresses endpoint malware prevention, detection, and containment for stealer infections
Recommendation — Harden endpoint malware defenses and alert on suspicious exfiltration behavior.

Practitioner Guidance

Why practitioners should care: Stealer incidents are often underestimated because the endpoint may not be visibly encrypted or destroyed. The real event is usually the theft of trust material, which means response has to include identity and session invalidation, not only malware removal.

What to watch for: Prioritise review of browser stores, saved passwords, active sessions, API keys, and any application or developer credentials present on the device. If those artefacts were exposed, assume they may be abused outside the endpoint and verify whether downstream systems show unusual sign-in or token use.

Practitioner takeaway: Treat stealers as credential-exposure incidents with malware as the delivery mechanism. The safer assumption is that anything the endpoint could authenticate with may already be in attacker hands.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org