Slash Boxes

SoylentNews is people

posted by robind on Friday February 14 2014, @01:39AM   Printer-friendly
from the entry-level dept.

AudioGuy writes:

"Researchers say they have uncovered an ongoing attack that infects home and small-office wireless routers from Linksys with self-replicating malware, most likely by exploiting a code-execution vulnerability in the device firmware.

The worm works by injecting vulnerable devices with a URL-encoded shell script that carries out the same seek-and-hijack behavior. The exploit may also change some routers' domain name system server to or, which are IP addresses used by Google's DNS service. Compromised routers remain infected until they are rebooted. Once the devices are restarted, they appear to return to their normal state. People who are wondering if their device is infected should check for heavy outbound scanning on port 80 and 8080, and inbound connection attempts to miscellaneous ports below 1024.

This blog post at Sans contains more technical details including a way to test if you have a vulnerable device."

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1) by Foobar Bazbot on Friday February 14 2014, @06:13PM

    by Foobar Bazbot (37) on Friday February 14 2014, @06:13PM (#87) Journal

    Okay, I get it, but is "- inbound connection attempts to misc ports 1024." an indicator of anything? I get that's the delivery mechanism, but have you looked at your firewall logs lately? Everyone is constantly getting probed by something at this point.

    Well, actually I haven't looked at firewall logs for anything internet-facing in a long time. But I assume those probes are mainly targeted at the well-known ports for common services. TFA says the propagation connections of this malware are on random (seems to imply uniformly-distributed) ports <1024, though "misc" certainly doesn't communicate that distinction. These patterns should be distinguishable after you collect enough data.

    But it really doesn't matter; TFS says this infection doesn't survive a reboot, so if I had a vulnerable model of router in a vulnerable configuration (i.e. remote admin enabled), my steps would be:

    1. Fix the configuration.
    2. Reboot the router.
    3. Shoot myself in the head, making the world a better place. (Seriously, I don't know any question to which "expose a consumer router's web administration page to the WAN interface" is the right answer)

    At no point did I actually need to check whether it was currently infected; rebooting it regardless of infection status is easier than checking the logs and trying to infer infection status, and then possibly rebooting anyway.

  • (Score: 1) by AudioGuy on Saturday February 15 2014, @12:51AM

    by AudioGuy (24) on Saturday February 15 2014, @12:51AM (#128) Journal
    +5, Correct Answer