An infostealer log is not just a list of passwords: it holds live session cookies, cached cloud CLI tokens and API keys that let an attacker walk straight into SaaS and cloud tenants, often without ever seeing an MFA prompt. This guide follows the path from a stealer log to a data breach, using the 2024 Snowflake campaign and the CircleCI incident as reference cases. It explains why passwords, browser sessions and non-human tokens need different responses, which binding and revocation controls actually stop replay, and what to monitor. It is written for identity engineers, cloud and SaaS administrators and SOC teams. Malware families and infection routes are covered in the Infostealer Threat Guide, and this page does not repeat them.
Key takeaways
- Three kinds of loot need three responses. Passwords need rotation and MFA, browser sessions need server-side revocation, and NHI tokens (cloud CLI caches, personal access tokens, API keys) need revocation at the issuer plus an audit of what they touched.
- Old logs stay dangerous. Mandiant found that at least 79.7 percent of accounts used in the Snowflake campaign had prior credential exposure, with the earliest linked infection dating to November 2020.
- MFA protects the login, not the session. A cookie or refresh token issued after MFA is replayed as an already authenticated session (ATT&CK T1550.004), which is how the CircleCI attacker used an engineer's SSO session.
- Binding beats lifetime tuning. Device-bound tokens (Entra Token Protection, Device Bound Session Credentials) make a stolen token useless elsewhere; short lifetimes only shrink the window.
- Password reset is not a session kill. Revocation is a separate action in every identity provider and cloud platform, and some caches (such as the AWS CLI cache) survive it.
How the attack works
The chain has four stages. Only the first involves malware.
- Harvest: a stealer runs on a device, often an unmanaged personal or contractor laptop, and collects credentials from web browsers (T1555.003), session cookies (T1539), credential files on disk (T1552.001) and application tokens (T1528). Microsoft's analysis of Lumma lists saved passwords, session cookies and autofill from Chromium and Gecko browsers, VPN configuration files, email and FTP clients and Telegram data.
- Package and sell: the output is packaged as a log per infected device and sold or shared. Buyers filter logs by domain, for example every entry containing a SaaS tenant's login URL. See the Initial Access Brokers Guide.
- Replay: the buyer either signs in with the password (T1078.004 Cloud Accounts where no MFA is required) or imports cookies into a browser to resume an authenticated session (T1550.004 Web Session Cookie). Cached CLI tokens and personal access tokens are used directly against APIs.
- Act on objectives: data is enumerated, staged and exported, and new persistence is added (new tokens, OAuth consents, MFA methods or access keys) so that access survives the original credential being rotated.
| Item in the log | What the attacker gets | Does MFA stop it? | Correct response |
|---|---|---|---|
| Saved password for an SSO or SaaS login | A new sign-in | Yes, if MFA is enforced on every surface | Reset, enforce MFA, check for MFA method changes |
| Session cookie for an IdP or SaaS app | An existing authenticated session | No, MFA already happened | Revoke sessions at the IdP and in each app |
| Refresh token or primary refresh token material | New access tokens until revoked | No | Revoke refresh tokens, require device-bound tokens |
| Cloud CLI cache (AWS, Azure, Google Cloud) | API access as the developer | No | Revoke sessions or keys at the cloud provider, review audit logs |
| Personal access token or API key in a file or env var | Non-interactive API access | No | Revoke at the issuer, rotate, audit use |
| Service account password (static) | Sign-in as a workload | Usually not enforced | Replace with key pair, OAuth or workload identity |
The ATT&CK techniques and their defences are covered in depth in the MITRE ATT&CK T1550 Guide and the Session Hijacking and Cookie Theft Guide.
Where it shows up
- Cloud data platforms: in the Snowflake campaign (UNC5537), Mandiant found three root causes: accounts without MFA, credentials that had not been rotated (some valid for up to four years), and no network allow lists. Access came through the Snowsight web interface and the SnowSQL client, followed by reconnaissance, staging of table data and download. See the Snowflake Security Guide.
- Developer platforms and CI/CD: a stolen session for an engineer who can mint production tokens is a supply chain incident. CircleCI's 2022 compromise began with malware on one laptop stealing an SSO session that was already backed by two-factor authentication.
- Contractors and third parties: Mandiant observed that several Snowflake-related infections were on contractor systems also used for gaming and pirated software, and that one such laptop can reach several clients. See the Contractor Identity Lifecycle Guide.
- Microsoft 365 and Google Workspace: stolen cookies and refresh tokens give mailbox, file and chat access, and an attacker can register a new MFA method or OAuth consent to persist.
- Cloud consoles and CLIs: developer machines hold cached credentials for AWS, Azure, Google Cloud, Kubernetes, GitHub and package registries. These are non-human identity credentials in practice, even when they belong to a person, because they authenticate API calls with no interactive step. See the Service Account Security Guide.
Impact
- Data theft and extortion: the Snowflake campaign led Mandiant and Snowflake to notify about 165 potentially exposed organisations, and data was used for extortion. See the Snowflake breach analysis.
- Secrets theft at scale: at CircleCI the attacker exfiltrated customer environment variables, tokens and keys, and customers were told to rotate every secret stored on the platform. See the CircleCI breach analysis.
- Persistence beyond the stolen item: new API keys, OAuth grants and MFA registrations made during the session outlive the stolen cookie, so cleaning up only the original credential leaves the attacker in.
Detection
Detection works at three points: the exposure (the log exists), the replay (an unusual session) and the follow-on activity (new persistence or bulk export).
| Signal | Source | Notes |
|---|---|---|
| Corporate domain or SaaS login URL in stealer log feeds | Threat intelligence or breach notification services | Compare the infection date with the last password change and session revocation, not the date of the alert |
Leaked credentials risk detection (leakedCredentials) | Microsoft Entra ID Protection | Available without a premium licence; always high risk |
Anomalous token (anomalousToken) and unfamiliar sign-in properties (unfamiliarFeatures) | Microsoft Entra ID Protection (P2) | Microsoft notes a higher than normal false-positive rate for anomalous token at low and medium risk |
| Non-interactive sign-ins from a new ASN, country or device for an existing session | IdP sign-in logs | Replayed refresh tokens appear as non-interactive sign-ins; review those logs, not only interactive ones |
| Unusual client application IDs or tool names | SaaS login history (for Snowflake, login and query history views) | Mandiant listed client strings such as DBeaver_DBeaverUltimate and specific SnowSQL and connector versions for UNC5537 |
| Same session cookie used from two IP ranges | SaaS audit logs, secure web gateway, CASB | Only possible where the app logs a session identifier |
| New MFA method, OAuth consent, API key or PAT shortly after a sign-in anomaly | IdP and SaaS audit logs | The strongest indicator that a replay turned into persistence |
| Bulk export, stage creation or mass download | Data platform and file service audit logs | Snowflake view retention covers 365 days, which supports lookback hunting |
| Chrome Event ID 257 (source Chrome) | Windows Application log | Emitted when App-Bound Encryption verification fails, a sign of a process trying to decrypt cookies |
Metrics that show it is working
- Exposure to revocation time: hours from a stealer log alert to sessions, tokens and passwords being invalidated, target under 24 hours.
- Coverage of device-bound tokens: percentage of sign-ins to priority apps that satisfy a token protection policy.
- Password-only accounts: count of human and service accounts on SaaS and data platforms that can still sign in with a password alone, target zero.
- Static NHI credentials older than policy: count of PATs, access keys and API keys past their rotation date.
- Allow list coverage: percentage of data platform accounts restricted by network policy.
Prevention and hardening
Bind sessions to the device
- Entra Token Protection: a Conditional Access session control that accepts only device-bound sign-in session tokens such as the primary refresh token. Native apps for Exchange Online, SharePoint Online and Teams are generally available on Windows, macOS and iOS; browser support is in preview and limited to selected web apps accessing Azure Resource Manager. Microsoft recommends a pilot group and a report-only policy first. See the Conditional Access Guide.
- Device Bound Session Credentials (DBSC): the browser generates a key pair, stored in a TPM where available, and short-lived cookies are refreshed only when the browser proves possession of the private key. It covers HTTPS only, and Google notes malware present during session registration could still extract the key. The specification is a W3C WebAppSec draft, so check its current status before depending on details.
- Chrome App-Bound Encryption: from Chrome 127 on Windows, cookies are encrypted so that only Chrome can decrypt them; malware needs SYSTEM privileges or code injection into Chrome. It breaks roaming profiles and can be controlled with the
ApplicationBoundEncryptionEnabledpolicy. Keep it on and prevent users running downloads as Administrator.
Make revocation fast and complete
- Continuous Access Evaluation (CAE): in Entra, disabling a user, resetting a password, enabling MFA, revoking refresh tokens or high user risk are critical events that CAE-aware services such as Exchange Online, SharePoint Online and Teams act on, with Microsoft stating propagation latency of up to 15 minutes. CAE-capable clients can hold tokens for up to 28 hours, so revocation, not expiry, is the control.
- AWS: revoking a role's active sessions attaches an
AWSRevokeOlderSessionsdeny policy based onaws:TokenIssueTime. It does not affect IAM user access keys, IAM Identity Center permission set roles (revoke there instead) or service-linked roles, and users must clear the local CLI cache. - Tokens with issuers: GitHub's guidance on a leaked secret is to revoke it with the provider first, then rotate and review audit logs; deleting the file or commit does not stop use.
Remove what a stealer can usefully take
- No password-only access to data platforms: Snowflake is phasing out single-factor password sign-in between September 2025 and October 2026 on a rolling, per-account basis: MFA for human users with passwords, and no passwords for
TYPE=SERVICEusers. Do not wait for your enforcement date. - Replace static NHI credentials: use workload identity federation, OIDC and short-lived tokens for pipelines, so nothing long-lived sits on a laptop. See the Token and Session Security Guide.
- Network allow lists: restrict data platforms and admin consoles to corporate egress or named networks; this alone would have blocked replay from attacker infrastructure in the Snowflake campaign.
- Phishing-resistant MFA: required for every human sign-in, including BI tools and contractors. It does not stop cookie replay but removes password-only reuse. See the Phishing-Resistant MFA Guide.
- Managed devices for privileged and developer access: require compliant devices for admin portals and code platforms, and keep personal browser profiles from syncing corporate sessions. See the Browser Storage Security Guide.
Response sequence after a log hit
- Identify the device, the infection date and every corporate domain, cookie and token file in the log.
- Revoke all sessions and refresh tokens for the user at the IdP, then in each SaaS app that keeps its own sessions.
- Revoke at the issuer every NHI credential in the log or reachable from the device: cloud sessions and access keys, PATs, registry tokens, kubeconfig credentials. Use the Secrets Rotation Runbook Template.
- Reset the password and confirm MFA methods, OAuth consents and API keys created since the infection date; remove anything unexplained.
- Hunt audit logs from the infection date (not the alert date) for use of each item, and treat confirmed use as an incident. The OAuth Token Theft Incident Playbook covers the SaaS side.
- Rebuild or remove the infected device from corporate access before reissuing credentials, or the new ones are stolen too.
Roll back carefully: a tenant-wide session revocation or a strict token protection policy can lock out unsupported clients. Run token protection in report-only mode, analyse interactive and non-interactive sign-in logs over a full business cycle, and keep an excluded break-glass group.
Framework mapping
| Framework | Reference | Relevance |
|---|---|---|
| MITRE ATT&CK v20 | T1539, T1555.003, T1552.001, T1528 | Harvesting cookies, browser credentials, credential files and tokens |
| MITRE ATT&CK v20 | T1550.004, T1078.004 | Replay of web sessions and use of cloud accounts |
| MITRE ATT&CK v20 | M1032 Multi-factor Authentication | Mitigation for password reuse, not for session replay |
| NIST SP 800-53 Rev. 5 | SC-23 Session Authenticity, AC-12 Session Termination, IA-11 Re-authentication | Bound sessions, revocation and re-authentication |
| NIST SP 800-53 Rev. 5 | IA-2, SI-4 | Authentication of users and monitoring for anomalous use |
| NIST CSF 2.0 | PR.AA-03, DE.CM-01, RS.MI-01 | Authenticate users and services, monitor, contain |
Lessons from incidents
- Snowflake 2024: credentials stolen years earlier still worked because nobody rotated them, and no MFA or network policy stood in the way. The fix was ordinary hygiene applied to every account, including service accounts with no owner.
- CircleCI 2022: MFA had been completed, so the stolen session carried it. The engineer's ability to generate production tokens turned one laptop into exposure of every customer's secrets.
- Common failure: responders reset the password and close the ticket, leaving refresh tokens, app sessions, CLI caches and newly created API keys valid.
- Common failure: monitoring covers employees only, while contractor and personal devices, are where infections happen.
Practitioner checklist
- Subscribe to stealer log monitoring for every corporate and SaaS tenant domain, and record infection dates.
- Write a stealer log runbook that separates password, session and NHI token actions, with named owners for each app.
- Pilot Entra Token Protection or equivalent device binding in report-only mode for Exchange, SharePoint and Teams, then enforce for administrators first.
- Confirm CAE is active and that your SOC knows how to revoke refresh tokens for a user in one step.
- Remove password-only sign-in from data platforms and admin consoles, and convert service users to key pair, OAuth or workload identity.
- Apply network allow lists to data platforms and cloud admin access.
- Inventory long-lived PATs, access keys and API keys held on developer machines and replace them with short-lived federated tokens.
- Alert on new MFA methods, OAuth consents and API keys created after a sign-in anomaly.
- Require managed, compliant devices for privileged, developer and contractor access to sensitive tenants.
- Track exposure to revocation time and report it monthly.
Standards and references
- MITRE ATT&CK: Steal Web Session Cookie
- MITRE ATT&CK: Use Alternate Authentication Material: Web Session Cookie
- Google Cloud (Mandiant): UNC5537 Targets Snowflake Customer Instances for Data Theft and Extortion
- Microsoft Learn: Token protection in Microsoft Entra Conditional Access
- Microsoft Learn: Continuous access evaluation
- Chrome for Developers: Device Bound Session Credentials
- AWS: Revoke IAM role temporary security credentials
- Snowflake: Deprecation of single-factor password sign-ins
Related NHI Mgmt Group resources: Infostealer Threat Guide · Session Hijacking and Cookie Theft Guide · Lumma Stealer Guide · Snowflake Breach 2024 · Token and Session Security Guide