News

Fizzer Bubbles Up

A mass-mailing worm known as Fizzer broke out late last week and is getting more attention from a prominent security vendor Monday.

Fizzer sends itself to all contacts in the Windows Address Book, contains a backdoor that uses mIRC to communicate with a remote attacker and contains a keylogger. The worm affects all versions from Windows 95 through Windows XP.

The message has dozens of possible subject lines, several different body texts and randomly generated attachment names.

While security vendor F-Secure gives Fizzer its highest alert status, both Symantec and Trend Micro started it out on a lower rung. Symantec, however, bumped up the severity of the alert Monday.

"Due to the number of submissions received from customers, Symantec Security Response is upgrading this threat from a Category 2 to a Category 3 threat," the company said in a statement.

For comparison, Klez.H, which is still on top of Symantec's threat list despite being released more than a year ago, currently ranks higher as a Level 4 threat on Symantec's threat scale.

About the Author

Scott Bekker is editor in chief of Redmond Channel Partner magazine.

Featured

  • Microsoft Starting To Roll Out New Excel Connected Data Types

    Microsoft on Thursday announced some Excel and Power BI enhancements that add "connected data types" on top of the standard strings and numbers options.

  • Windows 10 Users Getting New Process for Finding Optional Driver Updates

    Accessing Windows 10 drivers classified as "optional updates" will be more of a manual seek-and-install type of experience, starting on Nov. 5, 2020, Microsoft explained in a Wednesday announcement.

  • Microsoft Changes Privacy Platform Name to SmartNoise

    Microsoft Research has changed the name of its "differential privacy" platform from "WhiteNoise" to "SmartNoise," according to a Wednesday announcement.

  • Why Restarting a Failed SCVMM Job Might Be a Bad Idea

    Occasionally, restarting a failed System Center Virtual Machine Manager job can leave your virtualization infrastructure in an unknown state. Here's how to avoid that.

comments powered by Disqus