<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Visual Studio on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/visual-studio/</link><description>Recent content in Visual Studio on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 09 Nov 2026 11:07:29 +0100</lastBuildDate><atom:link href="https://hackingpassion.com/tags/visual-studio/index.xml" rel="self" type="application/rss+xml"/><item><title>Fake GitHub Security Tools Infected Over 2,000 Windows Machines</title><link>https://hackingpassion.com/fake-github-security-tools-malware/</link><pubDate>Mon, 09 Nov 2026 11:07:29 +0100</pubDate><guid>https://hackingpassion.com/fake-github-security-tools-malware/</guid><description>&lt;p>&lt;strong>More than 2,000 Windows machines have been taken over by the security tools their owners cloned from GitHub and built themselves.&lt;/strong> The people getting hit are cybersecurity professionals, paid to stop exactly this. The fake repositories have been going up for two years, and some are still online today.&lt;/p>
&lt;p>The trap works the way these people already work. A researcher needs a scanner, a reverse proxy, a script to clean up the output of another tool. They search GitHub, they find a repository that looks right, they clone it, and they build it. That last step is the one that ends it. &lt;strong>The moment they build it, or even only open it, the machine is no longer theirs.&lt;/strong>&lt;/p></description></item></channel></rss>