Fake LastPass Downloads Spread Stealer That Kills 145 Security Tools
A kit impersonating 40+ brands on GitHub used a Microsoft-signed driver to disable security software before installing the Rapuncel infostealer.
A fake LastPass Authenticator on GitHub led researchers to a campaign impersonating at least 40 companies, SecurityWeek reports.
Timeline of the discovery
- August 13, 2026 — LastPass's Threat Intelligence, Mitigation, and Escalation (TIME) team spotted a fake GitHub organization impersonating LastPass Authenticator, ranking high in search results for "LastPass Authenticator download" (Security Affairs).
- Following weeks — LastPass brought in malware-analysis partner Delphos Labs, which found the same infrastructure spoofing more than 40 other companies, confirming this was a shared, reusable malware-as-a-service kit rather than a one-off fake page.
- September 10, 2026 — The attackers' Cloudflare-fronted payload server was still active and serving a JavaScript redirect, with content that LastPass confirmed had changed between August 27 and September 10, showing the operators were actively maintaining the campaign.
- September 17–21, 2026 — LastPass and Delphos Labs published their joint findings, which were then covered by BleepingComputer, SecurityWeek, The Hacker News, Security Affairs and others.
How it worked
- LastPass spotted the fake GitHub page on August 13, 2026. It ranked highly in searches for "LastPass Authenticator download" and showed fake "VirusTotal Approved" badges, along with slogans like "Secure," "Verified Access" and "Secure Connection" designed purely to reassure visitors (heise online).
- Victims downloaded an archive containing a renamed Microsoft debugging tool (`vsdbg.exe`, the Visual Studio CoreCLR Debugger) that sideloaded a malicious DLL named `vsdbg.dll` placed in the same folder — a technique known as DLL side-loading (The Hacker News).
- The archives were deliberately padded to be large — up to 148MB and 127.9MB in samples researchers reviewed — specifically to dodge security scanners that skip oversized files.
- The installer attempted three separate methods of escalating to administrator rights before reaching SYSTEM-level privileges, the highest level of access on a Windows machine, and then installed a kernel driver as a Windows service.
- That driver, named `Alinubx.sys` and disguised as an NVIDIA component called `nvfsflt64.sys` registering as the "NvFsFilter" service, carried a legitimate chain signature from Microsoft's Windows Hardware Compatibility Publisher program and scored zero detections on VirusTotal when researchers checked it in August.
- The driver contained a hardcoded list of 145 antivirus and EDR processes it was built to terminate, and it was not on Microsoft's official list of blocked, vulnerable drivers at the time it was found.
- With defences disabled, it deployed an infostealer LastPass calls Rapuncel, which steals credentials from browsers, as well as data from crypto wallets, Steam, Discord, Telegram and Windows itself (heise online).
LastPass stresses that none of its own systems were compromised, Security Affairs notes.
How the driver bypasses security software
According to LastPass's own technical writeup, the driver calls a low-level Windows function, `ObOpenObjectByPointer`, with kernel-mode access — "bypass[ing] the normal user-mode SeAccessCheck path at handle-open time," in the company's words. "It asks the kernel to open the process as kernel code, then kills it," LastPass explained, which is why the driver can defeat Protected Process Light (PPL), a Windows feature "many security vendors" rely on to stop their own processes from being killed (BleepingComputer).
This class of attack is widely known in the security industry as "bring your own vulnerable driver" (BYOVD): rather than writing malicious code that Windows would block from running at the kernel level, attackers abuse a driver that is technically legitimate and properly signed, but can be repurposed to kill security tools once installed.
The scale of the impersonation campaign
LastPass's report, quoted by Security Affairs, states: "LastPass Threat Intelligence, Mitigation, and Escalation (TIME) Team, in partnership with Delphos, identified and disrupted a multi-stage malware delivery campaign impersonating at least 40 companies on GitHub." The report adds that "the payload it delivered survived controls that were built to stop exactly this, with a Microsoft Windows Hardware Compatibility Publisher chain signature and a clean VirusTotal score."
Researchers noted that similar techniques — fake GitHub repositories optimized to rank in search engines, bundled with kernel-level EDR killers — had already been seen a few months earlier by security firms Trend Micro and Arctic Wolf, suggesting this is an evolving, recurring tactic rather than an isolated incident (heise online).
Why it matters
Signed drivers are trusted by Windows, so this technique — known as "bring your own vulnerable driver" — lets malware disable protection quietly. Search engine poisoning means even careful users can land on fake download pages, since the fraudulent GitHub repository appeared among the very top results for a search any real LastPass Authenticator user might run.
The use of GitHub itself as a hosting and distribution platform is notable: GitHub is widely trusted by developers and IT professionals, and corporate web filters that might block unknown download sites typically allow GitHub traffic through without a second look, making it an effective launchpad for this kind of brand impersonation.
How to stay safe
- Download software only from the vendor's official site or app store, not from search results or GitHub mirrors. The real LastPass Authenticator comes from lastpass.com and official app stores, not GitHub.
- Be wary of "trust badges" on download pages such as "VirusTotal Approved" — they are easy to fake and carry no independent verification.
- Businesses should block known vulnerable drivers using Microsoft's driver blocklist (Windows Defender Application Control's "Vulnerable Driver Blocklist"), and should keep that list updated as new abused drivers are discovered.
- Treat unusually large installer archives with suspicion, since padding files to inflate size is a known scanner-evasion trick.
- Watch for installers that request administrator rights through unusual or repeated prompts, which can indicate multiple privilege-escalation attempts.
What readers should do
- If you downloaded a "LastPass Authenticator" or similar security app from GitHub rather than an official app store, treat the device as potentially compromised.
- Run a full scan with security software from a vendor not on the known-killed list, ideally after booting from trusted external media, since the malware is designed to disable most installed security tools.
- Change passwords for any accounts accessed on the affected device, starting with email, banking and cryptocurrency accounts, from a separate clean device.
- Revoke and regenerate API keys, browser-saved passwords and any crypto wallet seed phrases that may have been exposed.
- Report suspicious GitHub repositories impersonating known brands directly to GitHub's abuse team.
- IT administrators should check endpoint logs for the Alinubx.sys driver, the NvFsFilter service name, or unexpected vsdbg.exe/vsdbg.dll pairs, and should add the known indicators of compromise to detection rules.
Background: who is LastPass and why it is a frequent target
LastPass is one of the most widely used password managers, which makes its brand especially valuable to criminals: anyone searching for "LastPass" is, by definition, someone who cares about online security and is likely managing logins for many other accounts. That makes a compromised LastPass user a high-value target, and it is why LastPass itself has previously disclosed real breaches of its own infrastructure in past years, separate from this impersonation campaign, prompting the company to invest heavily in a dedicated threat-intelligence team capable of finding and dismantling look-alike campaigns like this one before they spread further.
Sources & Verification
Additional reporting
- SecurityWeeksecurityweek.com
- Security Affairssecurityaffairs.com
- BleepingComputerbleepingcomputer.com
- The Hacker Newsthehackernews.com
- heise onlineheise.de



