GKRootWire
Cloud & Sysadmin Microsoft Confirms Preview Update Wipes Out Desktop SettingsAI Nvidia to Acquire Hugging Face for $12.9 BillionDev Tools A Deep Dive Into Intrusive Linked ListsGadgets DJI's Romo 2 Robovac Adds Local-Only Mode After Privacy ScareAI Nvidia Reportedly Moves to Acquire Hugging FaceAI Anthropic Launches Claude Tools for AI Shopping AgentsCloud & Sysadmin Microsoft Confirms Preview Update Wipes Out Desktop SettingsAI Nvidia to Acquire Hugging Face for $12.9 BillionDev Tools A Deep Dive Into Intrusive Linked ListsGadgets DJI's Romo 2 Robovac Adds Local-Only Mode After Privacy ScareAI Nvidia Reportedly Moves to Acquire Hugging FaceAI Anthropic Launches Claude Tools for AI Shopping Agents
Security

An Employee's Password Turned Up in an Infostealer Log — Here's What to Do Next

Stolen credentials from malware logs often include live session tokens that can let attackers skip MFA entirely.

Infostealer malware doesn't just harvest passwords — it can also grab browser cookies and authentication tokens, effectively capturing a logged-in session. That means even if a compromised account has multi-factor authentication enabled, an attacker holding a valid session token may not need to pass MFA at all to take it over.

Security researchers at Flare outline a practical response process for defenders who spot employee credentials surfacing in these logs. The key steps: quickly figure out which exposed accounts and sessions are still active, prioritize based on access level and business risk, and revoke or rotate credentials and sessions before an attacker acts on them.

The underlying message is that finding a leaked password is just the start of the investigation, not the end of it.

Why it matters: Most password-reset workflows ignore the session-hijacking angle entirely, leaving a false sense of security after a routine credential rotation. Teams that don't also kill active sessions and tokens tied to infostealer-exposed accounts may be leaving the door open even after they think they've locked it.

Sources: BleepingComputer