Rogue Software

SafetyAntiSpyware

Published: December 9, 2009 Reading time: 1 min

SafetyAntiSpyware (branded in the wild as Safety Anti-Spyware 3) is rogue anti-spyware. The behavior matches the usual scareware pattern from that period: invent threats, then sell a license to “remove” them. What it does First it “detects” fake infections. Then it asks the user to license the product and keeps nagging until someone pays. Activation does not make the machine safer. When it showed up in the wild: New rogue: SafetyAntiSpyware. To clean an infected PC, use the Malware Removal guide for Windows. ...

Continue Reading

New social engineering technique: use Microsoft support to sell rogues

Published: December 9, 2009 Reading time: 1 min

Sunbelt analyst Adam Thomas came across this ugly new social engineering technique when he analyzed the DefenceLab rogue security product. It does the usual scare-ware stuff: a fake scan and fake “Windows Security Center” alert: Then it directs the potential victim to a Microsoft Support page, but injects html code into the page in his or her browser to make it appear as though Microsoft is suggesting the purchase of the rogue. This is the real Microsoft page: ...

Continue Reading

SecurityTool

Published: October 5, 2009 Reading time: 1 min

SecurityTool is rogue antivirus software — a scareware scam built to take money, not to protect a PC. It belongs to the same late-2000s wave of fake “security suites” that flooded Windows desktops with false positives and purchase prompts. Symptoms If a machine is infected you typically see continuous pop-ups and system warnings claiming the PC is infected, urging you to buy SecurityTool. Those alerts are false. Paying does not clean infections or prevent new ones; SecurityTool is the infection. ...

Continue Reading

WiniGuard

Published: January 12, 2009 Reading time: 4 min

WiniGuard is rogue antispyware — scareware dressed up as a legitimate security product. It exploits fear of PC infections to push a paid “cleanup.” It does not protect the machine; infected PCs should have it removed, not licensed. This page is a 2009-era field dossier: how it behaved, how it typically arrived, and the filesystem / registry fingerprints shared across the clone family. For the wider genealogy, see The biggest rogue family. ...

Continue Reading

Search