Attribution of Malicous Code:
By MZL
I just spent the last couple of weeks spinning up (meaning developing curriculm) for class on Malicious Code. Up until until three weeks ago, I knew the basics. Having worked in the IT department of a public facing Organization, I have had much practice mitigating Malicous software. -Conficker was a mess.
In late 2010 and early 2011, the world found out about a new very serious threat. Code could be weaponized into a WMD derivative. Specifically, StuxNet targeted PLC (Programmable Logic Controllers) which run just about everyting humans rely on. Everything from elevators to water treatment plants. Stuxnet changed the world as we knew it. Until then, Malicious Code did things like:
steal your money
format your HDD (Hard Drive)
Just pull pranks, like the Monkey Virus - caused the screen to change shades. (Yes, I caught that one, maybe circa 1994 or 1995. -I might still have a copy on a floppy disk somewhere.)
Stuxnet set the stage and provided a blueprint to attack critical infrastructure. A true Asymetric warfare tool. What good is money if the lights don't come on for 18 months?
I wanted to look at Attribution of Malicious Code. There are many tools to aid in this hunt.
https://talosintelligence.com (It's possible to get a real time map by country of servers hosting Malicious code. Does this list all of them. Nope. With Bullet proof hosting, many sites are hidden or officated. But to learn and interact with some of the tools. Talos Intelligence by Cisco is brilliant. Simply Zoom into a region of interest, then click on a Red, Green or Blue circle. Talos will flag the site as:
Red Spam
Green Malware
Blue Legitimate
You can zero in and get either IP or Domain information.