On September 17, researchers at LastPass and Delphos Labs disclosed an actively distributed campaign that should concern every SOC: a fake LastPass Authenticator installer hosted on GitHub that doesn't just steal credentials — it systematically dismantles the security stack first. The installer drops a Windows kernel driver signed through Microsoft's own hardware-compatibility program, uses that driver to terminate antivirus and EDR processes, and only then executes a password stealer. At the time of discovery, the malicious driver scored zero detections on VirusTotal.
This is a Bring Your Own Vulnerable Driver (BYOVD)-adjacent technique with a nasty twist: the driver isn't merely a known-vulnerable legitimate driver — it's a purpose-built AV killer carrying a valid Microsoft signature. That signature defeats naive trust models, defeats some driver blocklists, and — as the VirusTotal result demonstrates — defeats signature-based detection entirely.
If your users install password managers or authenticator apps from search results, ads, or unofficial GitHub repositories, you have exposure. This post breaks down the attack chain and gives you the detection content to find it.
Technical Analysis
What Happened
The attack chain, based on the LastPass/Delphos Labs research:
- Lure and delivery: A convincing fake installer for LastPass Authenticator is hosted on GitHub. This weaponizes a trusted platform — GitHub's legitimacy helps the lure pass URL filtering, user scrutiny, and some reputation-based controls.
- Driver drop and load: The installer writes a malicious kernel driver to disk and loads it. The driver is signed via Microsoft's Windows Hardware Compatibility Program (WHCP/WHQL attestation signing pipeline), giving it a valid Microsoft-issued signature.
- Security product termination: From kernel mode, the driver terminates antivirus and EDR processes. User-mode self-protection mechanisms are irrelevant against a sufficiently capable kernel-mode actor — this is why driver loading is a crown-jewel control.
- Payload execution: With defenders blinded, a password stealer executes — targeting exactly the credential material a LastPass-themed lure would attract: users who store and manage credentials locally.
Why the Microsoft Signature Matters
Microsoft's hardware compatibility/attestation signing is designed to certify drivers for Windows. Threat actors have repeatedly abused this pipeline (and stolen/leaked code-signing certificates) to get malicious drivers past:
- Driver Signature Enforcement (DSE) — Windows will load the driver without complaint.
- SmartScreen and reputation checks — signed binaries inherit trust.
- Signature-based AV — zero VirusTotal detections confirms the driver was invisible to static detection.
This is not a vulnerability in LastPass itself. LastPass is the lure. The affected platform is Windows endpoints where a user executes the trojanized installer with sufficient privileges to load a driver (administrator rights required — which is exactly what installer-style lures typically coax out of users via UAC prompts).
Exploitation Status
- Actively distributed in the wild as of the September 17, 2026 disclosure.
- No CVE is associated with this campaign — it abuses legitimate Windows functionality (signed driver loading) rather than a patchable bug. The fix is behavioral detection, driver blocklisting, and installer hygiene, not a patch Tuesday update.
- Watch for Microsoft to add the driver's signature/hash to the Microsoft Vulnerable Driver Blocklist and for revocation actions via Windows Update.
Detection & Response
The highest-fidelity signals in this campaign are: (1) driver loads from non-standard paths, (2) a security product process dying abnormally, and (3) installer-like processes performing driver installation activity. Build your hunting around those three behaviors — they generalize to the entire EDR-killer family, not just this sample.
Sigma Rules
---
title: Suspicious Kernel Driver Load from User-Writable or Temporary Path
id: 3f8a1b2c-7d94-4e5b-a6c1-9f2e8d3b4a01
status: experimental
description: Detects loading of a kernel driver (.sys) from user-writable, temporary, or non-standard locations — a hallmark of BYOVD/EDR-killer campaigns such as the fake LastPass Authenticator installer that drops a Microsoft-signed AV-killing driver.
references:
- https://thehackernews.com/2026/09/fake-lastpass-authenticator-installer.html
- https://attack.mitre.org/techniques/T1068/
- https://attack.mitre.org/techniques/T1562/001/
author: Security Arsenal
date: 2026/09/18
tags:
- attack.defense_evasion
- attack.t1562.001
- attack.t1068
logsource:
category: driver_load
product: windows
detection:
selection_path:
ImageLoaded|contains:
- '\AppData\'
- '\Temp\'
- '\tmp\'
- '\Downloads\'
- '\ProgramData\'
- '\Users\Public\'
- '\$Recycle.Bin\'
selection_ext:
ImageLoaded|endswith: '.sys'
filter_signed_microsoft_system:
Signed: 'true'
ImageLoaded|contains: '\Windows\System32\drivers\'
condition: selection_path and selection_ext and not filter_signed_microsoft_system
falsepositives:
- Legitimate software that extracts drivers to ProgramData during installation (rare; verify publisher and install context)
- Some VPN, anti-cheat, and hardware monitoring tools with poor packaging hygiene
level: high
---
title: Security Product Process Terminated by Non-System Process
id: 8c2d4e6f-1a3b-4c5d-9e7f-2b8a6c4d5e02
status: experimental
description: Detects abnormal termination of antivirus/EDR processes. In the fake LastPass Authenticator campaign, a signed kernel driver kills security software before a password stealer runs. Security tools terminating outside of an expected update/uninstall path is a critical signal.
references:
- https://thehackernews.com/2026/09/fake-lastpass-authenticator-installer.html
- https://attack.mitre.org/techniques/T1562/001/
author: Security Arsenal
date: 2026/09/18
tags:
- attack.defense_evasion
- attack.t1562.001
logsource:
category: process_termination
product: windows
detection:
selection_target:
TargetImage|contains:
- 'MsMpEng.exe'
- 'MsSense.exe'
- 'SenseIR.exe'
- 'SentinelAgent.exe'
- 'SentinelServiceHost.exe'
- 'CSFalconService.exe'
- 'CSFalconContainer.exe'
- 'cylancesvc.exe'
- 'bdagent.exe'
- 'avp.exe'
- 'ekrn.exe'
- 'SophosHealth.exe'
- 'sophossps.exe'
- 'TaniumClient.exe'
- 'cb.exe'
- 'xagt.exe'
- 'elastic-endpoint.exe'
- 'elastic-agent.exe'
filter_parent:
Image|contains:
- '\Windows\System32\svchost.exe'
- '\Windows\System32\wininit.exe'
- 'MsMpEng.exe'
condition: selection_target and not filter_parent
falsepositives:
- Legitimate AV uninstall/upgrade workflows — correlate with authorized change windows and known installer hashes
level: critical
---
title: Suspicious Installer or Downloader Spawning Driver Installation Activity
id: 5e7f9a1b-3c4d-4e5f-8a9b-1c2d3e4f5a03
status: experimental
description: Detects user-context installer-style executables invoking driver/service installation tooling (sc.exe create of kernel services, pnputil, rundll32 installing INF drivers) — consistent with the fake LastPass Authenticator installer staging its signed AV-killer driver.
references:
- https://thehackernews.com/2026/09/fake-lastpass-authenticator-installer.html
- https://attack.mitre.org/techniques/T1543/003/
author: Security Arsenal
date: 2026/09/18
tags:
- attack.persistence
- attack.defense_evasion
- attack.t1543.003
logsource:
category: process_creation
product: windows
detection:
selection_sc:
Image|endswith: '\sc.exe'
CommandLine|contains|all:
- 'create'
- 'type='
CommandLine|contains:
- 'kernel'
- 'binPath='
selection_pnputil:
Image|endswith: '\pnputil.exe'
CommandLine|contains: '/add-driver'
selection_suspicious_cli:
CommandLine|contains:
- '\AppData\'
- '\Temp\'
- '\Downloads\'
- '\Users\Public\'
- '.sys'
condition: (selection_sc or selection_pnputil) and selection_suspicious_cli
falsepositives:
- IT driver deployment scripts — restrict by path and validate against software inventory
- Hardware vendor updaters with poor path hygiene
level: high
KQL — Microsoft Sentinel / Defender
This query hunts the three-stage behavior chain: a driver loaded from a suspicious path, followed by termination of a security product process, pivotable on the same device and time window. Run it across DeviceEvents (driver loads) and DeviceProcessEvents (tamper activity). A second query catches impersonation of LastPass branding in downloaded executables.
// Hunt 1: Driver loads from user-writable paths + security tool termination (BYOVD / EDR-killer pattern)
let Lookback = 7d;
let SuspiciousDriverLoads =
DeviceEvents
| where TimeGenerated > ago(Lookback)
| where ActionType == "DriverLoad" or (ActionType == "FileCreated" and FileName endswith ".sys")
| extend DriverPath = coalesce(FolderPath, FileName)
| where DriverPath has_any ("\\AppData\\", "\\Temp\\", "\\Downloads\\", "\\ProgramData\\", "\\Users\\Public\\")
| project DeviceId, DeviceName, DriverLoadTime=TimeGenerated, DriverPath, InitiatingProcessFileName, InitiatingProcessCommandLine;
let SecToolTermination =
DeviceProcessEvents
| where TimeGenerated > ago(Lookback)
| where FileName has_any ("MsMpEng.exe","MsSense.exe","SentinelAgent.exe","CSFalconService.exe","cylancesvc.exe","ekrn.exe","sophossps.exe","elastic-endpoint.exe")
or ProcessCommandLine has_any ("taskkill", "sc stop", "sc delete", "net stop")
| project DeviceId, SecEventTime=TimeGenerated, FileName, ProcessCommandLine, InitiatingProcessFileName;
SuspiciousDriverLoads
| join kind=inner SecToolTermination on DeviceId
| where SecEventTime between (DriverLoadTime .. DriverLoadTime + 30m)
| project DeviceName, DriverLoadTime, DriverPath, InitiatingProcessFileName, InitiatingProcessCommandLine, SecEventTime, FileName, ProcessCommandLine
| order by DriverLoadTime desc;
// Hunt 2: Executables masquerading as LastPass authenticator downloaded from non-official sources
DeviceFileEvents
| where TimeGenerated > ago(14d)
| where FileName has_any ("lastpass", "authenticator") and FileName endswith_any (".exe", ".msi")
| project TimeGenerated, DeviceName, FileName, FolderPath, SHA256, InitiatingProcessFileName, InitiatingProcessCommandLine
| order by TimeGenerated desc;
// Hunt 3: New kernel services registered pointing at suspicious paths
DeviceRegistryEvents
| where TimeGenerated > ago(14d)
| where RegistryKey has @"HKLM\SYSTEM\CurrentControlSet\Services"
| where RegistryValueName == "ImagePath"
| where RegistryValueData has_any ("\\AppData\\", "\\Temp\\", "\\Downloads\\", "\\Users\\Public\\", "\\ProgramData\\")
and RegistryValueData endswith ".sys"
| project TimeGenerated, DeviceName, RegistryKey, RegistryValueData, InitiatingProcessFileName, InitiatingProcessCommandLine;
Velociraptor VQL
Use this hunt artifact to sweep endpoints for recently created .sys files in non-standard locations and the kernel services that reference them — the residual artifacts of an EDR-killer drop even after the driver has done its work.
-- Hunt: EDR-killer driver artifacts — .sys files in user-writable paths and their service registrations
SELECT FullPath AS DriverFile,
Size AS DriverSize,
Mtime AS Modified,
Btime AS Created
FROM glob(globs=['C:/Users/*/AppData/**/*.sys',
'C:/Windows/Temp/**/*.sys',
'C:/ProgramData/**/*.sys',
'C:/Users/Public/**/*.sys',
'C:/Users/*/Downloads/**/*.sys'])
WHERE NOT IsDir
ORDER BY Created DESC
-- Correlate: enumerate running services/drivers whose binary lives outside System32\drivers
SELECT Name, DisplayName, PathName, State, StartMode
FROM wmi(query="SELECT Name, DisplayName, PathName, State, StartMode FROM Win32_SystemDriver")
WHERE PathName =~ '(?i)(appdata|temp|downloads|public|programdata)'
OR (PathName =~ '\.sys' AND NOT PathName =~ '(?i)system32\\\\drivers')
-- Live view: processes spawned from installer-style paths in the last hour (password stealer execution)
SELECT Pid, Name, Exe, CommandLine, Username, CreateTime
FROM pslist()
WHERE Exe =~ '(?i)(appdata\\\\local\\\\temp|downloads|users\\\\public)'
AND CreateTime > now() - 3600
Remediation / Verification Script
Run this PowerShell as an elevated triage step on any endpoint where the fake installer may have executed. It inventories suspicious drivers, checks Microsoft Defender tamper status, confirms the vulnerable driver blocklist is enforced, and collects evidence before remediation.
# === EDR-Killer / Fake LastPass Installer Triage & Hardening Script ===
# Run elevated. Review output before removing anything.
# 1) Find .sys files outside the standard driver store
$suspiciousPaths = @("$env:SystemDrive\Users","$env:SystemDrive\ProgramData","$env:TEMP")
Get-ChildItem -Path $suspiciousPaths -Recurse -Filter *.sys -ErrorAction SilentlyContinue |
Select-Object FullName, Length, CreationTime, LastWriteTime,
@{N='Signature';E={(Get-AuthenticodeSignature $_.FullName).Status}},
@{N='Signer';E={(Get-AuthenticodeSignature $_.FullName).SignerCertificate.Subject}} |
Format-List
# 2) Enumerate kernel services pointing to non-standard driver paths
Get-CimInstance Win32_SystemDriver |
Where-Object { $_.PathName -match 'AppData|Temp|Downloads|Public|ProgramData' } |
Select-Object Name, DisplayName, State, StartMode, PathName | Format-List
# 3) Check Microsoft Defender tamper protection and real-time monitoring status
Get-MpComputerStatus |
Select-Object IsTamperProtected, TamperProtectionSource, RealTimeProtectionEnabled,
AntivirusEnabled, AMServiceEnabled, BehaviorMonitorEnabled | Format-List
# 4) Verify Microsoft Vulnerable Driver Blocklist is enforced (blocks revoked/abused signed drivers)
Get-CimInstance -Namespace "root\Microsoft\Windows\Defender" -ClassName MSFT_MpPreference -ErrorAction SilentlyContinue
Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Control\CI\Config" -Name VulnerableDriverBlocklistEnable -ErrorAction SilentlyContinue
# Expected: VulnerableDriverBlocklistEnable = 1. If missing/0, enforce it:
Set-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Control\CI\Config" -Name VulnerableDriverBlocklistEnable -Value 1
# 5) Ensure Tamper Protection is on (cannot be set via script — must be enabled in Intune/Defender portal;
# flag hosts where it is off)
if ((Get-MpComputerStatus).IsTamperProtected -ne $true) {
Write-Warning "Tamper Protection is DISABLED on this host. Enable via Intune or the Defender portal immediately."
}
# 6) Collect evidence: recent service installs and driver-related events for IR handoff
Get-WinEvent -FilterHashtable @{LogName='System'; Id=7045; StartTime=(Get-Date).AddDays(-14)} -ErrorAction SilentlyContinue |
Select-Object TimeCreated, Message | Format-List
Get-ChildItem "$env:SystemDrive\Users\*\Downloads" -Recurse -Include *lastpass*,*authenticator* -ErrorAction SilentlyContinue |
Select-Object FullName, CreationTime, @{N='SHA256';E={(Get-FileHash $_.FullName -Algorithm SHA256).Hash}} | Format-List
# 7) If a malicious driver service is identified, stop and delete it (replace SERVICENAME):
# sc.exe stop SERVICENAME
# sc.exe delete SERVICENAME
# Then quarantine the .sys file, isolate the host, and open an IR case — a password stealer
# payload means credential compromise; force resets for any accounts used on the machine.
Remediation
There is no patch for this campaign — it's abuse of legitimate Windows driver-signing trust. Your remediation stack is layered:
- Enforce the Microsoft Vulnerable Driver Blocklist. Confirm
VulnerableDriverBlocklistEnable = 1(script above) via Intune or GPO. Microsoft revokes abused signed drivers through this mechanism — verify your estate actually receives and applies list updates (Windows 11 22H2+ enables it by default; older builds often don't). - Enable Tamper Protection everywhere via the Microsoft Defender portal or Intune. It won't stop a kernel driver from killing processes, but it raises the bar, generates tamper alerts, and protects against the user-mode tampering that typically accompanies these campaigns.
- Block driver loads from user-writable paths using WDAC / App Control for Business policies. Legitimate drivers load from
System32\driversor the DriverStore — deny everything else by policy. - Restrict software installation sources. The lure lives on GitHub masquerading as an official installer. Enforce application control (WDAC/AppLocker) so users can't run arbitrary installers, and publish the official LastPass distribution channels internally. Users should only obtain LastPass Authenticator from the official app stores or lastpass.com.
- Hunt retroactively. Run the KQL and VQL above across at least 30 days of telemetry. Zero VirusTotal detections means AV won't have flagged it — only behavioral telemetry will.
- If a host is hit, treat it as full credential compromise. The payload is a password stealer targeting a password-management user. Isolate the host, image it (do not clean in place — a kernel driver ran), force password resets for every credential that touched that machine, revoke sessions/tokens, and review authentication logs for anomalous use of those credentials.
- Monitor for the driver's revocation. Track Microsoft's driver blocklist updates and LastPass/Delphos Labs publications for hashes and the driver's certificate details, then sweep for those indicators fleet-wide.
The strategic lesson: a valid Microsoft signature is no longer a trust boundary. Signed-driver EDR killers are now commodity tradecraft — ransomware affiliates and initial access brokers ship them routinely. If your detection strategy still treats "signed = safe," this campaign is your wake-up call to move driver-load monitoring, tamper detection, and application control up the priority list.
Related Resources
Security Arsenal Healthcare Cybersecurity AlertMonitor Platform Book a SOC Assessment healthcare Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.