Re:IoT Goes Nuclear: Creating a ZigBee Chain Reaction
by davimack on Monday November 07, 2016 @02:42PM
(#12894272)
Domain gets tagged as distributing malware by my work's security system, FYI. Dunno what list it's gone on, but it's there.
[ Parent
| on HN ]
Re:IoT Goes Nuclear: Creating a ZigBee Chain Reaction
by Mister_Snuggles on Monday November 07, 2016 @05:19PM
(#12895756)
uMatrix doesn't allow this site to show either.
View Source reveals that this site is actually an iframed version of http://www.wisdom.weizmann.ac.il/~eyalro/iotworm/.
Re:IoT Goes Nuclear: Creating a ZigBee Chain Reaction
by toomuchtodo on Monday November 07, 2016 @03:01PM
(#12894467)
Re:IoT Goes Nuclear: Creating a ZigBee Chain Reaction
by cordite on Monday November 07, 2016 @03:46PM
(#12894885)
This too is not immune. I get it here too.
Re:IoT Goes Nuclear: Creating a ZigBee Chain Reaction
by jakobdabo on Monday November 07, 2016 @03:57PM
(#12895001)
Well, the HTML contains some very shady (encoded and obfuscated) JavaScript code.
If you want to investigate further replace the "return r;" in the very end of those two "evals" with "console.log(r);" then get the decoded code from the browser's console. Then run through code beautifier (built-in in Firefox JS debugger) to get readable code. But there are more code obfuscations later, though easy to reverse but I don't have the time right now.
Re:IoT Goes Nuclear: Creating a ZigBee Chain Reaction
by bpicolo on Monday November 07, 2016 @04:21PM
(#12895249)
OpenDNS blocks the domain it looks like
Re:IoT Goes Nuclear: Creating a ZigBee Chain Reaction
by ep3998 on Monday November 07, 2016 @04:47PM
(#12895494)
There is what looks like another site hosted by the other person who partnered on this: http://colinoflynn.com/iotworm/
Re:IoT Goes Nuclear: Creating a ZigBee Chain Reaction
by enzanki_ars on Monday November 07, 2016 @04:45PM
(#12895467)
You can use http://archive.is/gRSfN/image to get a screenshot of the page.
Re:IoT Goes Nuclear: Creating a ZigBee Chain Reaction
by midwestcode on Tuesday November 08, 2016 @12:02AM
(#12897802)
... shouldn't this be higher up?