Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Data Storage Security IT

Synolocker 0-Day Ransomware Puts NAS Files At Risk 150

Deathlizard (115856) writes "Have a Synology NAS? Is it accessible to the internet? If it is, You might want to take it offline for a while. Synolocker is a 0-day ransomware that once installed, will encrypt all of the NAS's files and hold them for ransom just like Cryptolocker does for windows PC's. The Virus is currently exploiting an unknown vulnerability to spread. Synology is investigating the issue."
This discussion has been archived. No new comments can be posted.

Synolocker 0-Day Ransomware Puts NAS Files At Risk

Comments Filter:
  • Interesting (Score:4, Interesting)

    by rebelwarlock ( 1319465 ) on Tuesday August 05, 2014 @05:54AM (#47605531)
    So between TOR and bitcoin, they think they finally have a viable method of collecting on ransomware. Also, I found it interesting that they're asking specifically for 0.6BTC - that is, double what Cryptolocker is asking. I wonder if there's an intentional correlation there.
  • /.ed (Score:5, Interesting)

    by simplypeachy ( 706253 ) on Tuesday August 05, 2014 @09:22AM (#47606169)

    Forum post so far:

    Hello Everyone,

    We’d like to provide a brief update regarding the recent ransomware called “SynoLocker,” which is currently affecting certain Synology NAS servers.

    Based on our current observations, this issue only affects Synology NAS servers running some older versions of DSM (DSM 4.3-3810 or earlier), by exploiting a security vulnerability that was fixed and patched in December, 2013. At present, we have not observed this vulnerability in DSM 5.0.

    For Synology NAS servers running DSM 4.3-3810 or earlier, and if users encounter any of the below symptoms, we recommend they shut down their system and contact our technical support team here: https://myds.synology.com/supp... [synology.com].

    -When attempting to log in to DSM, a screen appears informing users that data has been encrypted and a fee is required to unlock data.
    -A process called “synosync” is running in Resource Monitor.
    -DSM 4.3-3810 or earlier is installed, but the system says the latest version is installed at Control Panel > DSM Update.

    For users who have not encountered any of the symptoms stated above, we highly recommend downloading and installing DSM 5.0, or any version below:
    -For DSM 4.3, please install DSM 4.3-3827 or later
    -For DSM 4.1 or DSM 4.2, please install DSM 4.2-3243 or later
    -For DSM 4.0, please install DSM 4.0-2259 or later

    DSM can be updated by going to Control Panel > DSM Update. Users can also manually download and install the latest version from our Download Center here: http://www.synology.com/suppor... [synology.com].

    If users notice any strange behavior or suspect their Synology NAS server has been affected by the above issue, we encourage them to contact us at security@synology.com.

    Apologies for any problems or inconvenience caused. We will keep you updated with latest information as we address this issue.

  • by Dutch Gun ( 899105 ) on Tuesday August 05, 2014 @09:36AM (#47606261)

    A NAS device is not a toaster. It's a file server running a lightweight but fully-featured operating system. You don't need to be a professional network administrator, but you do need to be careful enough to at least check in regularly for updates. One presumes such hardware was purchased because you had valuable data you wished to manage or protect. Honestly, a NAS is really not a purchase for "normal" people. Power-users and up, I'd say, are the minimum personnel requirements.

    Even so, Synology machines are not hard to patch. They download OS updates automatically by default. All you have to do is log in via the administration page once in a while and click the "update" button, since it pops up right on the page after it sees you have an update to install. And every update has a link right next to it that points to a web page detailing exactly what changed or what was fixed. I'd suppose the reason there's no "auto-update" is because an update requires a 5-10 minute patch and reboot cycle, and you generally don't want your file server automatically rebooting at it's own convenience.

    I'm presuming (since information is a bit scarce) that users either failed to patch their machines for six months or longer due to neglect, or they made a deliberate choice not to do so for some reason, yet kept their internet-facing services wide open (note that these are not installed or enabled by default). Unfortunately, that's pretty much a guaranteed recipe for an attack of this sort. It's a crappy way to have to learn a lesson.

Perfection is acheived only on the point of collapse. - C. N. Parkinson