LockBit 5.0, Chrome zero-day and infostealers expose identity gaps

At a glance

What this is: This weekly threat roundup highlights active ransomware, browser exploit, and infostealer activity, with the clearest identity risk coming from compromised credentials, exposed keys, and stolen AI assistant context.

Why it matters: It matters because IAM, PAM, and NHI teams need to see how everyday exposure paths like browser exploitation and secret theft translate into privilege abuse, lateral movement, and session compromise.

By the numbers:

• Since December 2025, 60 victims have appeared on the group's data leak site, primarily U.S. private sector organizations.
• Google rated CVE-2026-2441 high severity with a CVSS score of 8.8.

👉 Read Anomali's Cyber Watch on LockBit 5.0, Chrome zero-day exploitation, and OpenClaw infostealer activity

Context

This week’s threat roundup shows how quickly modern attack paths converge on identity, whether the entry point is ransomware, a browser zero-day, or an infostealer harvesting tokens and keys. For IAM and NHI teams, the key issue is not just initial compromise but how stolen credentials, session context, and unmanaged secrets expand access after the first foothold.

The article also reinforces a pattern that is now common across enterprise environments: attackers prefer the path of least resistance, and identity data often provides it. Where AI assistants, browser sessions, and infrastructure credentials sit close together, compromise can move from a single exposed file or unpatched endpoint to broader account abuse with very little friction.

Key questions

Q: What breaks when browser exploits reach identity sessions and cloud consoles?

A: A browser exploit can do more than run code in a sandbox. If the endpoint already holds SSO sessions, saved credentials, or cloud admin tabs, the attacker may inherit trusted access without needing to defeat MFA again. That shifts the problem from patching alone to session hygiene, token protection, and rapid revocation of active access artefacts.

Q: Why do compromised tokens and keys matter so much in NHI and AI tooling?

A: Tokens and keys are the practical proof of trust in NHI and AI workflows. When attackers steal them, they can impersonate services, reuse gateway access, or bypass trust checks without changing the underlying password policy. That is why secret storage, rotation, and scope control matter as much as endpoint hardening.

Q: How should teams reduce ransomware blast radius in virtualised environments?

A: Teams should separate hypervisor administration, backup systems, and recovery paths from normal endpoint operations. If ransomware reaches ESXi or similar infrastructure, a shared trust model can turn one foothold into multiple encrypted workloads. Offline backups, tested restores, and strict access boundaries are the controls that limit that spread.

Q: Who is accountable when an AI assistant overshares sensitive content?

A: Accountability sits with the team that owns the policy, the attribute feeds, and the enforcement points, because ABAC only works when all three are managed together. If any one of them is missing, the organisation has not built a defensible control path, even if the model itself appears constrained.

Technical breakdown

How LockBit 5.0 turns initial access into broader impact

LockBit 5.0 is a ransomware-as-a-service variant that uses separate builds for Windows, Linux, and VMware ESXi, which lets operators match payloads to the target environment. The ESXi build is especially disruptive because it can shut down virtual machines before encrypting files, turning a single foothold into simultaneous availability loss across multiple workloads. The Windows build adds process injection, log clearing, and self-deletion to reduce detection and complicate recovery. That mix of platform-specific execution and defence evasion makes virtual infrastructure part of the ransomware blast radius, not just a supporting asset.

Practical implication: include ESXi and other virtual platforms in backup, monitoring, and incident response planning at the same priority as endpoints.

Why a browser zero-day becomes an identity problem

CVE-2026-2441 is a use-after-free flaw in Chrome’s CSS component that allows code execution inside the sandboxed renderer after a victim simply visits a malicious page. Even though the browser sandbox limits direct system access, browser compromise can still expose authenticated sessions, saved credentials, or active web applications. For identity teams, the key issue is not the browser vulnerability itself but the trust placed in an endpoint that already holds access tokens, federation sessions, and access to cloud consoles or identity portals. A patched browser that has not restarted still leaves the vulnerable code loaded, which extends the exploitation window.

Practical implication: verify patch application and restart compliance, not just update status, for browsers that mediate access to identity and cloud services.

OpenClaw infostealer exposure and AI assistant identity

The OpenClaw case shows how a commodity infostealer can capture more than documents or passwords. By sweeping local directories for configuration files, the malware collected authentication tokens, cryptographic key pairs, and memory files that contained user context, private messages, and calendar data. That combination turns an AI assistant from a convenience layer into an identity-rich target surface. If an attacker can impersonate the user at the gateway, bypass device trust checks, or reuse local keys, they can move from theft of content to abuse of the assistant’s connected identity and services.

Practical implication: treat locally stored AI assistant configuration and signing material as high-value identity assets subject to least privilege and rapid revocation.

Threat narrative

Attacker objective: The attacker wants to convert a single exposed browser, token store, or endpoint into wider access, operational disruption, or identity impersonation at scale.

1. Entry occurs through a malicious browser page for CVE-2026-2441, or through infostealer execution that harvests local files and credentials.
2. Credential access or abuse follows when the attacker captures tokens, keys, or session context from browser and AI assistant data stores.
3. Impact arrives as ransomware encryption, virtual machine shutdown, or identity impersonation that expands access beyond the initial device.

Breaches seen in the wild

• GitHub Dependabot Breach — GitHub Dependabot tokens stolen and abused to push malicious commits to repositories.
• Shai Hulud npm malware campaign — Shai Hulud campaign: npm malware exposed secrets on GitHub.

Read our 52 NHI Breaches Analysis report for a comprehensive view of breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

Identity exposure now begins long before explicit account takeover. Browser exploits, infostealers, and ransomware all increasingly intersect with identity data that sits in sessions, tokens, device files, and AI assistant configuration stores. That means the control surface is no longer just passwords and MFA prompts. Practitioners need to treat access-bearing artefacts as operational assets with defined ownership, revocation paths, and monitoring expectations.

AI assistants create a new class of identity-adjacent exposure. The OpenClaw case shows that locally stored gateway tokens, pairing keys, and memory files can collectively function like a portable identity bundle. That is a governance gap, not just a malware issue, because the security model for many AI tools still assumes benign local storage and weakly scoped trust. NHI teams should recognise this as a form of machine identity sprawl with user-context leakage attached.

Blast radius control is becoming the decisive resilience metric. LockBit 5.0’s ESXi targeting shows that one compromise can disable dozens of workloads at once, while browser exploitation can pivot into cloud and identity portals already open in the session. The practical lesson is that recovery scope and access containment matter more than isolated patch counts. Organisations that can segment credentials, sessions, and virtual infrastructure will recover faster and lose less.

Credential theft is now a cross-domain problem, not a siloed NHI issue. This roundup ties together endpoint compromise, cloud session abuse, and AI-assistant token theft, which means IAM, PAM, SOC, and endpoint teams must share the same exposure view. The category is moving toward unified identity observability across humans, workloads, and software agents. Teams that still manage these as separate workstreams will miss the attacker’s chaining logic.

Named concept: identity-adjacent blast radius. This describes the way a non-identity event, such as a browser exploit or infostealer infection, becomes an identity incident once the attacker reaches tokens, sessions, keys, or assistant context. The concept matters because it changes triage priorities. Security teams should investigate what identity artefacts were present on the affected system, not only what malware executed.

From our research:

• Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared to nearly 1 in 4 for securing human identities.
• From our research: 85% of organisations lack full visibility into third-party vendors connected via OAuth apps, according to The State of Non-Human Identity Security.
• Forward look: Read Ultimate Guide to NHIs , Key Challenges and Risks for the governance gaps that let exposed tokens, sprawl, and over-privilege persist.

What this signals

Identity teams should expect more incidents where the first visible event is not account takeover but secondary abuse of the artefacts that surround identity. Browser sessions, AI assistant files, and application tokens are now attractive targets because they let attackers move directly into trusted workflows. That makes session revocation, secret governance, and device-level visibility part of the identity programme, not separate concerns.

Identity-adjacent blast radius: organisations need a way to measure how far a compromised browser, endpoint, or assistant can reach before containment begins. The control question is no longer only whether a secret exists, but whether it can be revoked, rotated, and traced quickly enough to limit misuse. That is where IAM, PAM, and NHI governance now intersect with endpoint and SOC operations.

For practitioners

• Harden browser restart enforcement Verify that Chrome and other managed browsers are not just updated but fully restarted after patching, especially on endpoints used for cloud consoles, SSO portals, and admin tooling.
• Inventory identity artefacts on endpoints and AI tools Map where access tokens, pairing keys, API keys, and assistant configuration files are stored locally, then move them out of unmanaged file paths wherever possible.
• Segment virtual infrastructure from endpoint trust Assume ransomware targeting ESXi or similar platforms will attempt to widen impact quickly, and separate backup, monitoring, and administrative access for hypervisors from general endpoint workflows.
• Treat local AI assistant files as sensitive identity material Apply least privilege, encryption, and rapid revocation procedures to assistant memory files, gateway credentials, and device keys so compromise of a workstation does not expose the wider assistant identity.

Key takeaways

• This roundup shows that ransomware, browser exploitation, and infostealers now intersect directly with identity artefacts such as sessions, tokens, and keys.
• The clearest scale signal is that active ransomware campaigns, confirmed browser exploitation, and credential-harvesting malware are already operating in the wild.
• Practitioners should focus on browser restart compliance, secret inventory, and blast-radius control across virtual and AI-adjacent identity surfaces.

Key terms

• Identity Blast Radius: The amount of damage a compromised identity can cause across systems, data, and infrastructure. In NHI environments, it is shaped by permissions, network reach, and administrative capability rather than by the credential alone. Reducing blast radius is a containment strategy that limits lateral movement and data exposure.
• Session artefacts: Temporary access material such as active login sessions, cookies, tokens, and cached credentials that prove trust without requiring the original password again. These artefacts are often the shortest path from endpoint compromise to cloud or SaaS account abuse.
• Machine Identity Sprawl: Machine identity sprawl is the uncontrolled growth of non-human identities across teams, platforms, and business processes. It becomes a governance problem when identities are created faster than they can be inventoried, reviewed, rotated, or retired, leaving security teams with incomplete visibility and weak accountability.

What's in the full analysis

Anomali's full article covers the operational detail this post intentionally leaves for the source:

• The specific threat intelligence links and external references behind each campaign summary, useful if you need to validate IOC and attribution context.
• The full analyst commentary on LockBit 5.0, including the ESXi-specific behaviour and the monitoring signals defenders should prioritise.
• The browser zero-day details around CVE-2026-2441, including update timing and restart requirements for affected endpoints.
• The OpenClaw infostealer analysis with the exact files targeted and the identity artefacts that were captured.

👉 The full Anomali Cyber Watch post includes the threat links, analyst notes, and platform-specific detail behind each item.

Deepen your knowledge

The NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, machine identity security, secrets management, and workload identity. It helps identity and security practitioners align operational controls with the way modern access artefacts are actually used and abused.