TL;DR: Infostealer malware turns endpoint infections into structured credential logs that are aggregated, enriched and resold, according to Cyble, so exposure often begins on a device rather than at the perimeter. Security teams need to treat credential theft as a pipeline, not a single breach event.
At a glance
What this is: NHI Mgmt Group's analysis, drawing on Cyble's blog post: Infostealer malware turns endpoint infections into structured credential logs that are enriched and sold.
Why it matters: Identity teams need to detect the infection and enrichment stages early, because by the time stolen credentials appear in a listing, attackers may already have tested or reused them.
Context
Infostealer activity is a credential supply chain, not a single event. The infection on the endpoint is only the first mechanical step, followed by collection, log structuring, enrichment and resale. Infostealer logs matter because they show how stolen access becomes a tradable asset before most organisations realise a device was compromised.
That changes the governance problem for IAM and SOC teams. Traditional breach response assumes a clean boundary between compromise and disclosure, but infostealers blur that boundary by stealing browser credentials, session cookies and device fingerprints well before any alert arrives.
For identity programmes, the practical question is no longer whether a password was stolen. It is how quickly exposed credentials can be identified, invalidated and replaced once a stealer log exists somewhere outside the organisation's control.
Key questions
Q: How do stealer logs lead to account takeover?
A: Stealer logs capture reusable identity material such as passwords, cookies and tokens from infected devices, then package it for resale or direct abuse. An attacker can replay that material to sign in as the victim without needing to defeat the original password again, which turns a device compromise into account compromise.
Q: What should teams do first when stolen credentials are driving breach entry?
A: Start by identifying the accounts and journeys where reused secrets still grant the highest reach, then replace those paths with phishing-resistant authentication. The first goal is not broader MFA coverage, but removing the easiest replay path before an attacker can use harvested credentials at scale.
Q: Why are browser cookies so valuable to credential thieves?
A: Browser cookies are valuable because they often hold session tokens that let a site recognise an already authenticated user without re-entering a password. If a thief steals a persistent cookie, they may bypass login, MFA prompts and password resets until the session expires or is revoked. HttpOnly, Secure and SameSite flags, plus short session lifetimes and server-side revocation, reduce this exposure.
Q: How should security teams monitor illicit marketplaces effectively?
A: They should combine infrastructure monitoring, actor tracking, and relationship analysis. A forum’s sections, rank structure, sponsorships, and migration history often reveal more than isolated posts. The practical goal is to preserve continuity across platforms so intelligence stays useful when criminal communities move to a new site.
Technical breakdown
How infostealer malware turns a device into a credential source
Infostealer malware is designed for fast credential collection on an infected endpoint. It targets browser stores, saved passwords, autofill data, session cookies, payment details and application configurations that already exist on the machine. Many families also collect device fingerprinting data such as IP address, hardware identifiers and installed software, which helps attackers make later access attempts look familiar. The output is usually a compact log, which is not just stolen data but a structured bundle that can be reused, enriched and traded. See the T1555 Credentials from Password Stores Defensive Guide.
Practical implication: Treat endpoint compromise as an identity event, because the useful payload is often session material rather than only passwords.
Why log aggregation changes credential theft economics
A single stolen log has limited value, but hundreds or thousands of logs create inventory. Operators of stealer campaigns collect incoming logs through dashboards, bundle them by date or campaign and sort them by apparent value. That aggregation step turns isolated theft into a marketable catalogue of access paths. It also explains why attackers can move quickly from commodity infection to selective targeting, because the log set already contains enough structure to prioritise corporate portals, admin consoles and reusable logins. See the Infostealer Threat Guide.
Practical implication: Monitor for patterns that show mass log collection and triage, not only for individual exposed accounts.
How enrichment turns stolen credentials into a reuse problem
Raw credentials are often incomplete, so stealer ecosystems enrich them with context from previous leaks and other datasets. That enrichment can add employer details, job role hints, related accounts and the URLs needed to test access. Once enriched, the same stolen secret can feed credential stuffing, session replay or resale to another buyer. The key point is that the attacker is not just holding a password; they are building a usability layer around it that increases conversion into access. See the API Key Management Guide.
Practical implication: Prioritise exposed accounts that can be linked to privileged roles, reused passwords or active session tokens.
Threat narrative
Attacker objective: The attacker wants reusable access material that can be sold, replayed or converted into account compromise at scale.
- Entry begins when infostealer malware runs on an endpoint through a cracked installer, phishing lure, malicious extension or similar delivery path.
- Credential harvesting follows as the malware pulls browser secrets, cookies, saved logins and device fingerprints from the infected machine.
- Escalation occurs when operators aggregate, enrich and package those logs into a marketable set that can support credential stuffing or direct resale.
- Impact comes when a buyer uses the exposed access for account takeover, fraudulent sign-in or broader access to corporate services.
Breaches seen in the wild
- CircleCI breach 2023: Malware stole a CircleCI engineer's SSO session; attackers exfiltrated customers' CI/CD secrets and keys, forcing a platform-wide rotation.
- ClawHub malicious skills 2026: Hundreds of malicious ClawHub skills for the OpenClaw agent pushed credential stealers in early 2026; Koi found 341 of 2,857 in the ClawHavoc campaign.
Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
Infostealer exposure is a credential pipeline, not a discrete breach. Cyble's breakdown shows that value is created in stages: infection, harvesting, aggregation, enrichment and resale. That matters because each stage gives defenders a different interception point, and waiting for the final listing is the least efficient place to respond. The practitioner conclusion is that exposure management has to start at the endpoint and extend into marketplace intelligence.
Session cookies change the meaning of credential theft. Password theft alone already weakens identity controls, but cookie theft can bypass the login ceremony entirely. That means the control failure is not just weak password hygiene; it is the assumption that authentication is a single moment rather than a reusable artefact. Practitioners should treat active session material as a first-class identity asset, because that is what turns commodity malware into immediate access.
Identity governance fails when it stops at account ownership. Enriched logs often include enough context to map access to a person, role or device, which makes them more valuable to buyers and harder to contain after the fact. The named concept here is exposure-to-utility conversion: the process by which raw theft becomes usable access through parsing and enrichment. The practitioner conclusion is that governance must account for whether stolen material can still function, not only whether it was taken.
Marketplace visibility belongs in identity security, not only threat intelligence. When logs are sold with timestamps, URLs and samples, the market itself becomes a sign of compromised identity material. That shifts the relevant question from whether a breach happened to how quickly exposed credentials can be identified before they are operationalised. The practitioner conclusion is that credential monitoring needs to include resale signals as part of the identity control plane.
Credential compromise becomes durable when organisations ignore device-origin exposure. Infostealers usually start on unmanaged or personal endpoints, which means the organisation may never see the original infection but still inherits the access fallout. That breaks the assumption that perimeter visibility is enough to manage identity risk. The practitioner conclusion is that endpoint-originated credential exposure has to be handled as a standing identity threat, not an isolated endpoint incident.
What this signals
Exposure detection has to move upstream. Credential theft now emerges from endpoint infections, not only from perimeter breaches, so identity teams need to watch for the signs that stolen access is being assembled before it is sold. That means pairing identity telemetry with endpoint signals and marketplace intelligence, because waiting for a breach notice leaves the organisation reacting after reuse has already started.
Exposure-to-utility conversion: stolen credentials become operational risk only after they are parsed, enriched and tested. That is why the practical unit of defence is no longer the password alone but the full package of session state, device context and account privilege that makes reuse possible.
Account recovery flows, session revocation and privileged access review all matter more when stolen credentials can travel from a personal device to a resale forum without a visible perimeter event. Organisations that treat credential theft as a pipeline will identify and contain exposure earlier than those that wait for the final alert.
For practitioners
- Expand credential exposure monitoring Track stealer-log indicators, marketplace listings and enrichment artefacts alongside traditional breach notifications so exposed access is found earlier.
- Invalidate active session material quickly Revoke cookies, refresh tokens and related sessions as soon as exposed access is confirmed, because stolen session state can bypass password resets.
- Prioritise privileged and reusable accounts Rank exposed credentials by privilege, password reuse potential and business criticality so remediation begins with the accounts most likely to convert into access.
- Harden endpoints that store identity artefacts Reduce the amount of reusable authentication material sitting on browsers and local applications, especially on unmanaged or personal devices.
Key takeaways
- Infostealer campaigns turn endpoints into credential sources, which means identity risk often starts on unmanaged devices rather than at the perimeter.
- The main evidence of scale is the pipeline itself: harvested secrets are aggregated, enriched and resold before most organisations see a formal breach signal.
- Containment works best when teams revoke active session material, prioritise privileged accounts and watch for resale indicators as part of identity monitoring.
Related NHI Mgmt Group resources: Infostealer Threat Guide · API Key Management Guide · Secrets Management Guide · T1555 Credentials from Password Stores Defensive Guide
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and MITRE ATT&CK address the attack and risk surface, while CIS Controls v8 sets the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-02 — Secret Leakage | Stealer malware exfiltrates passwords, cookies and tokens from endpoints, making secret leakage the core issue. |
| NHI-07 — Long-Lived Secrets | The article shows how reusable credentials and session artefacts remain valuable long after theft. | |
| NHI-10 — Human Use of NHI | Personal devices and browser-stored identity material become attack paths when humans reuse access on them. | |
| Recommendation — Scan endpoints and log sources for exposed authentication material and revoke any leaked secrets immediately. Reduce the shelf life of credentials by shortening validity and revoking stale sessions fast. Separate human browsing environments from sensitive access paths and limit stored credentials on endpoints. | ||
| MITRE ATT&CK | TA0006; TA0010 — Credential Access; Exfiltration | The pipeline starts with credential theft and ends with data export to resale infrastructure. |
| Recommendation — Map stealer activity to credential access and exfiltration techniques, then hunt for collection and packaging stages. | ||
| CIS Controls v8 | CIS-5 — Account Management | Account lifecycle control is central when stolen credentials are rapidly reused and resold. |
| Recommendation — Apply account management controls to disable exposed accounts and remove stale access paths quickly. | ||
Key terms
- Infostealer Malware: Infostealer malware is designed to quietly capture credentials, browser sessions, cookies, and other authentication artifacts from an endpoint. It creates downstream identity risk because the stolen data often remains usable even after the initial infection is removed.
- Stealer Log: A stealer log is data collected by malware that records credentials, browser sessions, or other sensitive information from an infected device. The stolen data is then uploaded to an attacker-controlled system for later use or resale. In credential incidents, stealer logs often explain why plaintext passwords appear in leaked datasets.
- Credential Stuffing: Credential stuffing is an attack that uses stolen username and password pairs from previous breaches to try logging into other services. It works because many people reuse credentials, and because the login attempt uses valid information, it can look ordinary until the surrounding behavior gives it away.
- Session Cookie: A session cookie is a small piece of data a website stores in a browser to remember that a user has already authenticated. Technically, it carries a session identifier that links the browser to server-side state, enabling continuity across requests until logout, expiry, or invalidation.
Deepen your knowledge
NHI governance, agentic AI identity, and machine identity lifecycle are core topics in our NHI Foundation Level course, the industry's only accredited NHI security programme. If you are building or maturing an IAM programme, it is worth exploring.
Published by the NHIMG editorial team on November 9, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org