Brandon Nozaki Miller and Stuxnet: How (Not) to Write Malware

The recent fiasco with Node-ipc and its developer, Brandon Nozaki Miller, is ridiculous in its implementation and sure to have consequences in the free and open source community.

One program with fewer (immediate) issues was Stuxnet, which effectively targeted Iranian centrifuges and inhibited a hostile nation from further developing their nuclear capacity. In spite of the benefits of Stuxnet, hacks and malware such as these should be treated cautiously and used judiciously.

With this in mind, Miller's injudicious shot-gun approach to his hacktivism has been met with widespread condemnation from those affected by his malware and the internet at large.

Join my Discord and follow my Twitch to guarantee wealth and happiness for you and your kin:

Chapters:
0:00 - Intro
0:47 - Node-ipc
1:46 - Stuxnet
2:51 - The Problems with Both
3:46 - Outro

Thanks:
Arisu
CTO
Joey
Walter

#nodeipc

[MechaMugen]

I barely heard about this in the periphery of consumerist tech news, hearing the specifics is mind-blowing. FOSS crazies are a completely different breed
terminally online, hacker mindset, savior complex, all rolled into one

[whitefibre]

The first, in what I hope to be many, of the Ciggy Shorts

[digitalspecter]

While actions of this individual are reprehensible I really hope this will speed up countermeasures like not granting every package all the rights that the user has, static analysis (like code obfuscation detection) maybe even npm "distros" with staged reviews/releases. I wish we were using languages that track side-effects .. things like these would be easier to spot.