Light bulb Limited Spots Available: Secure Your Lifetime Subscription on Gumroad!

Nov 08, 2026 · 6 min read

Fake GitHub Security Tools Are Backdooring Security Pros

A two year old GitHub malware operation has swapped crypto game lures for scanner helpers and log parsers. Open the project in Visual Studio, hit build, and the backdoor installs before your code compiles.

You find a small repo that cleans up Fscan output. You clone it, open the solution and press build. That single click is the infection.

Russian antivirus vendor Doctor Web published the research on November 5, 2026, under the title "Insolence beyond belief. Threat actors target information security developers on GitHub." The people who usually dissect malware are now the intended victims.

Key Takeaways

  • Doctor Web reported on November 5, 2026 that "more than 2,000 PCs were infected" by a GitHub campaign whose first infected repositories appeared two years ago.
  • Fscan, the internal network scanner, is one named lure: a bogus repo offered a script to parse, clean and format its output.
  • Trojan.Loader.3261, an Electron app saved as Microsoft.exe, disables Windows Defender and System Restore, then deploys the BackDoor.AsyncRAT.115 backdoor, a crypto clipper and JS.Stealer.191.
  • JS.Stealer.191 takes browser data, FileZilla and MobaXterm configs, VPN settings and Discord tokens, then sends them out through a Telegram bot.
  • Doctor Web names no repository count or account names, so no list of repos to avoid exists yet.
A security analyst's dark desk at night with two monitors showing code and a terminal, lit in cool indigo light, representing malicious GitHub repositories aimed at security professionals

Who Is Being Targeted?

Security practitioners are the new target: the latest repositories pose as scanning automation, security system testing and log analysis projects. According to the Doctor Web report, early repositories went after crypto wallet users with Visual Studio projects for blockchain games, game bots and cheats. Then "the perpetrators have switched their attention to another large target group."

The 2,000 infected PCs count covers the whole operation, not only the security tool phase. Doctor Web does not split the number by lure, and BleepingComputer's coverage gives no repository total either.

This is a separate operation from two GitHub lures covered here before: the fake LastPass repos that pushed Rapuncel in September and the fake VS Code security alerts posted to GitHub in March. Different payloads, same bet: a developer trusts code because it sits on GitHub.

How Does Building the Project Trigger the Infection?

The .csproj file carries a PreBuildEvent that, in Doctor Web's words, "runs malicious code before the project gets compiled." Visual Studio treats this as a normal feature: Microsoft's documentation describes custom build commands that "run automatically before a build starts."

Python and Go files use a cruder trick, hiding malicious code "behind a large number of whitespaces" so it sits far off the right edge of the editor. The chain then runs like this:

  1. PowerShell first stage. PowerShell.Packed.270 runs from paths like C:\Users\Public\Pictures\t.ps1, queries attacker servers plus YouTube, Telegram, Google Docs, GitCode and Pastebin, and decrypts a download link for Quixo.7z.
  2. Electron loader. The archive unpacks to C:\ProgramData\Windows.Microsoft.Photos and starts Microsoft.exe (Trojan.Loader.3261, latest version 1.4.5).
  3. Defense teardown. The loader gains persistence and admin rights, disables Defender, UAC, System Restore and VSS, removes ESET, McAfee and Malwarebytes, and edits the hosts file to block antivirus domains.
  4. Evasion, Mode3. PPID spoofing under explorer.exe, a Smart App Control bypass via the VerifiedAndReputablePolicyState registry value, ntdll unhooking, Halo's Gate direct syscalls, and ETW and AMSI patching.
  5. Payloads. Modules are injected into legitimate processes such as RegAsm.exe and dwm.exe, which then run the backdoor, clipper and stealer.

What Do the Backdoor and Stealer Take?

BackDoor.AsyncRAT.115 gives the operators remote control; Doctor Web found two identical copies that differ only in network ports, which may let two operators control the same machine. Trojan.Clipper.688 swaps crypto wallet addresses on the clipboard and sends screenshots with the active window title, username and IP address to a Telegram bot.

JS.Stealer.191 first checks whether it runs in a sandbox or virtual machine, then collects:

  • Browser data
  • FileZilla XML files, MobaXterm.ini and Total Commander's wcx_ftp.ini
  • VPN settings and messenger files
  • Game and gaming platform account data, plus Discord tokens

Read that list as a pentester would. FileZilla and Total Commander store FTP hosts, MobaXterm holds saved SSH and RDP sessions, and VPN profiles open client networks. On a consultant's laptop, those files are keys to other people's infrastructure. That is a much bigger prize than the gamer wallets this crew started with, and it likely explains the pivot.

Doctor Web lists these attacker addresses (defanged): muckanthropic[.]com, muckduck.duckdns[.]org, muckcoding[.]com, muckdeveloper[.]com and 130.12.182[.]172. Hashes are in the vendor's Trojan.Loader.3261 IOC file.

What This Means for Your Inbox

Doctor Web writes "browser data" and stops there. It does not say whether that means saved passwords, cookies or both, and neither source mentions webmail. So no one can confirm Gmail sessions were stolen. Still, on a machine where an attacker holds a live AsyncRAT shell, the operator can open your signed in browser directly.

That puts your email account in scope if you built one of these repos. Your mailbox is the reset channel for GitHub, cloud consoles and client portals. Session theft has already turned into account takeover elsewhere; see how infostealers hijacked Claude sessions without a password.

How Should You Vet a GitHub Repo Before Running It?

Treat any unfamiliar repo as untrusted code and read the parts that execute before you run anything. Doctor Web's own advice is to "update your antivirus databases regularly and scan all of the files you download," but this campaign removes antivirus, so add these steps:

  1. Read build hooks first. Search .csproj and .vcxproj files for PreBuildEvent, PostBuildEvent and Exec tasks. Check setup.py, Makefiles and package scripts too.
  2. Expose hidden code. Turn on word wrap or run grep -nE '\s{100,}' to catch payloads pushed off screen by whitespace. Flag any PowerShell call or Base64 blob in a log parser.
  3. Build in a throwaway box. Windows Sandbox is a disposable VM where "closing it deletes all software, files, and state." Microsoft notes networking is on by default, so disable it. Because the stealer checks for VMs, a clean run proves nothing; the point is to keep it off your real machine.
  4. Check the history, not the star count. A new account, one squashed commit and stars that arrived in a burst are warning signs. Doctor Web says nothing about fake stars here, but a popular look is cheap to buy.
  5. Prefer source over release binaries. An .exe or .7z in Releases that cannot be rebuilt from the code shown is a red flag.
  6. Hunt for the artifacts. Look for C:\ProgramData\Windows.Microsoft.Photos, Microsoft.exe outside system folders, new Defender exclusions for regasm.exe or dwm.exe, and traffic to the domains above or to Telegram's bot API.

If you built a match, reimage the machine instead of cleaning it, then rotate SSH keys, FTP and VPN credentials, sign out every email and cloud session, and revoke GitHub tokens. Leaked tokens tend to stay live for years, as 543,699 exposed GitHub credentials showed.

What Comes Next?

Doctor Web found an unfinished Electron project that would add service based persistence and download Microsoft.exe again if removed, so the operators are still building. Expect more lures shaped like whatever security pros clone this month. The Doctor Web write up is the place to check for updated indicators.

Stop Email Tracking in Gmail

Spy pixels track when you open emails, where you are, and what device you use. Gblock blocks them automatically.

Try Gblock Free for 30 Days

No credit card required. Works with Chrome, Edge, Brave, and Arc.