Earlier quoted context omitted.
Thanks. Question for the C folks. The author seems to have reimplemented functions such as strlen, memcpy, and atoi in 'bot/util.h' instead of using the stdlib. Anyone know why? https://github.com/0x27/linux.mirai/blob/master/mirai/bot/ut...
Because you cannot rely on some chintzy IoT device to have dynamically loadable libraries. In all likelihood, they don't. But let's assume they do have loadable stdlib, would would you trust the integrity of your botnet to dozens of poorly designed IoT devices?
Mirai Botnet Client, Echo Loader and CNC source code
31–40 of 51 posts
Re: Mirai Botnet Client, Echo Loader and CNC source code
#32Earlier quoted context omitted.
Because you cannot rely on some chintzy IoT device to have dynamically loadable libraries. In all likelihood, they don't. But let's assume they do have loadable stdlib, would would you trust the integrity of your botnet to dozens of poorly designed IoT devices?
You can statically link the binary you build, doesnt mean you need to reimplement.
Re: Mirai Botnet Client, Echo Loader and CNC source code
#33There is an irc snippet in the source - https://github.com/0x27/linux.mirai/blob/master/dlr/release/... From the full mirror linked below
Re: Mirai Botnet Client, Echo Loader and CNC source code
#34This thing's strategy for finding machines to take over is so simple it's embarrassing. It tries to open an unencrypted Telnet connection to random IP addresses. If it gets a response, it tries the following username/password combinations: root xc3511 root vizxv root admin admin admin root 888888 root xmhdipc root default root juantech root 123456 root 54321 support support root (none) admin password root root root 1…
I cannot wait for some type of top-down pressure to force IoT developers to take security seriously. The movement has been pushed into overdrive thanks to insane levels of competition where you either crush your R&D into the smallest breakneck period or you live to see your creation being sold for half of what your budget can allow by other firms lifting your efforts while you're still at the workbench.[1] I've been…
I hate this phrase. It's not like a bunch of people gathered and said "let's make shitty IoT stuff!". It's not a "community", there aren't groups around advocating against security best practices.
If anything the actual community around IoT stuff takes security more seriously than most HNers.
The problem is the companies and manufacturers that aren't part of the community.
And I take issue with your [4]. That has nothing to do with security. It was a glitch, and it happened, and I personally don't like Nest as a company very much and think they make pretty shitty products, but they take security seriously, and in a discussion about IoT security linking a non-security related software bug serves no purpose. Everything has bugs, that doesn't mean it's absolute shit when something goes wrong.
Your [3] is also incorrect. The Arduino IoT Manifesto's second point is that a dev should make sure their product can be updated, and even if it's abandoned it should be able to be repurposed in something else, or updated by someone else.
Re: Mirai Botnet Client, Echo Loader and CNC source code
#35It seems to me that destroying the vulnerable devices would solve the DDoS problem and gives a big kick in the face of the affected manufacturers plus a good press coverage.
Re: Mirai Botnet Client, Echo Loader and CNC source code
#36Since there is no way to police this and 'wack a mole' for billions of devices is not a practical strategy this security focus on IOT devices while nice does not address the core problem of vulnerable networks and ddos. It distracts and diverts from it.
Re: Mirai Botnet Client, Echo Loader and CNC source code
#37There is an irc snippet in the source - https://github.com/0x27/linux.mirai/blob/master/dlr/release/... From the full mirror linked below
Glad to see these are American hackers and not Russian.
Re: Mirai Botnet Client, Echo Loader and CNC source code
#38This thing's strategy for finding machines to take over is so simple it's embarrassing. It tries to open an unencrypted Telnet connection to random IP addresses. If it gets a response, it tries the following username/password combinations: root xc3511 root vizxv root admin admin admin root 888888 root xmhdipc root default root juantech root 123456 root 54321 support support root (none) admin password root root root 1…
Re: Mirai Botnet Client, Echo Loader and CNC source code
#39The IoT devices can be accessed over telnet. Out of curiosity: Is there a self destruct command? or a way to make one? It seems to me that destroying the vulnerable devices would solve the DDoS problem and gives a big kick in the face of the affected manufacturers plus a good press coverage.
Is there a reason this can't be done? (Other than a legal reason, which hackers don't tend to care too much about.)