The fake security tools GitHub campaign relies on booby-trapped repositories that pose as scanners or log analyzers, and that install a backdoor and data stealers on the machine of whoever builds them. Dr.Web researchers published their analysis on November 5, 2026, and BleepingComputer relayed it on November 6, as BleepingComputer reports. The victims are Windows systems, and the campaign’s author has not been identified.
According to Doctor Web, more than 2,000 computers were infected at the time of the investigation, and the campaign has run for about two years, starting with lures tied to blockchain games, bots and cheats. Here is what is known, what the sources do not confirm and how to protect yourself.

What are the fake security tools GitHub repositories?
They are public repositories that imitate tools useful to professionals: scan automation, security testing, log analysis. As BleepingComputer reported, one claimed to clean up and format the output of the Fscan network scanner. They hide code that downloads malware.
The actor changed targets: it first aimed at crypto wallet users and gamers, then at cybersecurity specialists. According to Doctor Web, some repositories even include step-by-step guides to install Visual Studio and clone the project, for inexperienced users. Neither BleepingComputer nor Doctor Web gives the number of repositories or accounts involved.
How does the fake security tools GitHub infection start?
The malicious code runs when the victim opens, builds or runs the project, not on a simple clone, according to DEV Community, which summarizes the Dr.Web report. In Visual Studio projects, a pre-build event launches PowerShell before the compilation even starts, according to BleepingComputer.
Doctor Web details other hiding places: commands in Visual Studio option files, and Python or Go code concealed behind long runs of spaces. PowerShell then fetches an encrypted download link, which leads to a modular loader named Microsoft.exe. That loader sets up persistence, tries to raise its privileges, weakens Windows protections and injects the next stage into legitimate processes.
Which malware do fake security tools on GitHub install?
The chain drops three final payloads: the AsyncRAT backdoor, a clipper that swaps copied crypto wallet addresses, and an information stealer, according to BleepingComputer. The stolen data is sent to a Telegram bot.
The stealer collects browser data, VPN settings, FTP client files, gaming accounts and Discord tokens. Doctor Web found two copies of AsyncRAT on different ports, which suggests, according to SecurityLab, that two operators could control the same machine. The loader also tries to remove ESET, McAfee and Malwarebytes, and it neutralizes mechanisms such as AMSI and event tracing. An unfinished component able to relaunch the loader if it is deleted points to active development, but SecurityLab specifies that no use is confirmed.
Where sources differ on fake security tools GitHub
The sources agree on the essentials, but several points differ or are missing. Here is what we noticed when comparing BleepingComputer, Doctor Web, SecurityLab, DEV Community and WindowsForum.
- Date: the Doctor Web page is dated November 5, while BleepingComputer and SecurityLab publish on the 6th. The research is therefore a day older than the coverage.
- Number of loader modes: BleepingComputer describes two (Mode3 by default, Mode2 as fallback), while Doctor Web lists four, including Mode3non and a Handler mode that may be a legacy method.
- Infection figure: “more than 2,000 Windows systems” for BleepingComputer, “more than 2,000 PCs” for Doctor Web. WindowsForum notes that the counting method is not explained and that the share caused by security-themed lures is not given.
- Repository names: WindowsForum names a repository and accounts that appear in neither BleepingComputer nor Doctor Web. That site says it mixes in AI-assisted content, so we do not repeat them.
- Fake exploits and SEO: none of the sources we read mentions fake vulnerability exploits or artificial search ranking on GitHub for this campaign.
Our analysis: why fake security tools on GitHub target professionals
This section is our analysis. Security specialists handle third-party code and run unfamiliar tools to test them, which turns a routine gesture into an opening. They also hold valuable secrets: VPN access, FTP clients, browser sessions. That targeting is plausible, but the sources do not say how many professionals were actually hit.
The pattern is not isolated. BleepingComputer had already described a fake LDAPNightmware exploit on GitHub, and we covered in the compromised OVHcloud CLI case how a booby-trapped binary circulated through GitHub. In every case, trust in the platform replaces checking the content.
How to protect yourself from fake security tools GitHub
Treat any third-party repository as untrusted code: read it and test it in an isolated virtual machine, never on your main workstation. Doctor Web also recommends keeping antivirus databases up to date and scanning everything you download. Here are concrete steps:
- Test in isolation: a virtual machine with no access to your sessions, credentials or wallets.
- Read before building: inspect Visual Studio project files (pre-build events, option files) and look for abnormally long lines in scripts.
- Assess the repository: account age, commit history, number of contributors, consistency between the README and the code.
- Keep your protections on: do not disable your antivirus to “make a tool work”.
- Look for traces: compare your machine with the indicator list published by Doctor Web, for example a ProgramData folder imitating a Windows component or an unexpected Microsoft.exe executable.
- If in doubt: isolate the machine, change passwords and tokens from another device and move your crypto funds.
Frequently asked questions about fake security tools GitHub
Researchers at the company Doctor Web (Dr.Web) published the analysis on November 5, 2026, relayed by BleepingComputer on November 6. No threat actor name is given.
According to BleepingComputer, the AsyncRAT backdoor, a cryptocurrency clipper and an information stealer that exfiltrates to a Telegram bot, delivered by a loader named Microsoft.exe.
Not according to DEV Community: the victim must open, build or run the project. Cloning alone would not be enough.
Isolate the machine, check Doctor Web’s indicator list, change passwords and tokens from another device and reinstall the workstation if the traces are confirmed.

