IoT Goes Nuclear: Creating a ZigBee Chain Reaction
iotworm.eyalro.net
IoT Goes Nuclear: Creating a ZigBee Chain Reaction
1–10 of 100 posts
Re: IoT Goes Nuclear: Creating a ZigBee Chain Reaction
#2Re: IoT Goes Nuclear: Creating a ZigBee Chain Reaction
#3Domain gets tagged as distributing malware by my work's security system, FYI. Dunno what list it's gone on, but it's there.
Re: IoT Goes Nuclear: Creating a ZigBee Chain Reaction
#4How else do you explain how woefully unprepared we are?
Re: IoT Goes Nuclear: Creating a ZigBee Chain Reaction
#5Re: IoT Goes Nuclear: Creating a ZigBee Chain Reaction
#6This is also why you're starting to see more and more devices opt to a completely device to cloud infrastructure instead of local communication. More control of the stack on device and in the air.
Re: IoT Goes Nuclear: Creating a ZigBee Chain Reaction
#7Earlier quoted context omitted.
http://archive.is/gRSfN
This too is not immune. I get it here too.
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
#8Clearly, absolutely no one saw this coming, nor did anyone warn us. :-) How else do you explain how woefully unprepared we are?
Re: IoT Goes Nuclear: Creating a ZigBee Chain Reaction
#9Re: IoT Goes Nuclear: Creating a ZigBee Chain Reaction
#10Clearly, absolutely no one saw this coming, nor did anyone warn us. :-) How else do you explain how woefully unprepared we are?
It's a little hard to distinguish worthwhile warnings from the near-constant din of finger-wagging