{"id":32469,"date":"2017-10-31T20:35:06","date_gmt":"2017-10-31T20:35:06","guid":{"rendered":"http:\/\/greenpages.com\/?p=7278"},"modified":"2017-10-31T20:35:06","modified_gmt":"2017-10-31T20:35:06","slug":"grim-reaper-botnet-could-come-for-your-candy","status":"publish","type":"post","link":"https:\/\/icloud.pe\/blog\/grim-reaper-botnet-could-come-for-your-candy\/","title":{"rendered":"Grim \u2018Reaper\u2019 Botnet Could Come for Your Candy"},"content":{"rendered":"

\"'Reaper'<\/span><\/p>\n

 <\/p>\n

By Tony Ramsey, Practice Manager, Networking & Security<\/em><\/p>\n

IoT devices and gadgets which are the primary target of the ‘Reaper’ botnet present a new attack vector and easy-to-exploit vulnerabilities.\u00a0<\/span>These vulnerabilities. coupled with the number of IoT devices, have certainly helped the ‘Reaper’ botnet reach the critical mass needed to deliver a massive DDoS attack or a crippling payload to its victims. But don’t fret, it hasn’t done so yet. When compared to the Mirai botnet attack last year, the good news is that security experts are more prepared for it.\u00a0<\/span><\/p>\n

The major concern is the sheer number of infected devices and their combined computing power harnessed by botnet controllers through injection of malicious code that has the potential to cause massive problems.\u00a0<\/span>\u00a0<\/span><\/p>\n

The numbers provided by 360 Netlab are impressive:<\/span><\/p>\n

Infected bots connected to\u00a0one controller: About 28,000 infected devices<\/b><\/span><\/h3>\n

Number of devices vulnerable to ‘Reaper’ botnet: As far as two million<\/b><\/span><\/h3>\n

It\u2019s important to note, however, that this botnet has already lost the element of surprise. The ‘Reaper’ botnet controllers and some of its code are now known to the internet security community. Its method of infection: exploiting known vulnerabilities and its propagation between devices are also being analyzed.<\/span><\/p>\n

Therefore, it is no longer a question of detection but prevention.\u00a0\u00a0<\/span><\/p>\n

This is certainly the time for device vendors to provide security patches for hardware and software platforms to address the specific exploitable vulnerabilities.<\/span><\/p>\n

There\u2019s much anxiety in the internet security community since we\u2019ve not yet seen any attacks or malicious activity and the Reaper botnet still seems to be in the expansion phase; its intention for a concerted malicious attack is yet unknown, but we know that its potential magnitude of damage is quite large.\u00a0<\/span><\/p>\n

Some of the infected networked devices are mainly for home and SOHO use, so education and awareness is needed by consumers who aren\u2019t necessarily accustomed to applying security patches and in-depth configurations for threat mitigation.<\/span><\/p>\n

‘Reaper’ Botnet Update:<\/b><\/span><\/h4>\n

The original claim in the security world that this is one of the largest botnet infections ever has been significantly reduced. As of today, the prediction<\/a> is that the ‘Reaper’ botnet isn’t as far reaching\u00a0as expected, but it could change at any moment. The question is, will the ‘Reaper’ botnet cause more widespread damage than the infamous Mirai?<\/span><\/p>\n

 <\/p>\n

\n<\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a>\n<\/div>\n

\"\"\/<\/p>\n","protected":false},"excerpt":{"rendered":"

  By Tony Ramsey, Practice Manager, Networking & Security IoT devices and gadgets which are the primary target of the ‘Reaper’ botnet present a new attack vector and easy-to-exploit vulnerabilities. These vulnerabilities. coupled with the number of IoT devices, have certainly helped the ‘Reaper’ botnet reach the critical mass needed to deliver a massive DDoS attack… Read more »<\/a><\/p>\n","protected":false},"author":61,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5397,3303,179,1546,3327],"tags":[],"class_list":["post-32469","post","type-post","status-publish","format-standard","hentry","category-botnet","category-cyber-security","category-featured","category-it-security","category-networking-security"],"_links":{"self":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/32469","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/users\/61"}],"replies":[{"embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/comments?post=32469"}],"version-history":[{"count":1,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/32469\/revisions"}],"predecessor-version":[{"id":32470,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/posts\/32469\/revisions\/32470"}],"wp:attachment":[{"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/media?parent=32469"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/categories?post=32469"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/icloud.pe\/blog\/wp-json\/wp\/v2\/tags?post=32469"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}