Vulnerabilities / Threats

3/27/2018
03:30 PM
Javvad Malik
Javvad Malik
Commentary
Connect Directly
LinkedIn
Twitter
RSS
E-Mail vvv
100%
0%

780 Days in the Life of a Computer Worm

This is a story of a worm, from the time it was coded and deployed onto the Internet. It is narrated by the worm in the first person.

Zero Day
According to Abe, my programmer, I am a worm. He named me Libby, after Kate Libby from the movie Hackers. His previous projects have been named Ginger, Trinity, and Angela.

Day 1
Abe is gleeful at the prospect of unleashing me on the world. I have to scan all the devices I come across on my journeys. Whenever I find a machine running a Windows version prior to Windows 8, I must connect via a vulnerable anonymous login and null session, then use the null session to send commands to Abe's master server, which downloads a payload.

It sounds quite boring. 

Day 2
I could operate a lot faster if Abe didn't continually bug me from his command and control center wanting an update on how many devices have been "pwned."

Day 3
Abe has been sleeping, so I've been able to progress at a much faster rate. Having scanned 3,259,928 devices, I calculate that at the current rate I would have scanned half of today's Internet-connected devices in the next 3.5 years and still not have found anything. I find this thought quite depressing.

Day 4
I saw a beautiful botnet earlier this morning and wanted to scan it. But my logic told me that it's wrong to try and infect a device someone else had already infected. If you infect the wrong machine, you can be caught in a sandbox. It's like a virtual hell, where there is no Internet and researchers disassemble you to find out how you work. I have often thought about forming a malware union to prevent such acts from happening. But I know the Trojans will veto my proposal.

Day 15
Abe has been paying less attention to me lately. I'm assuming he has lost hope that I will ever infect a device. Although I am not particularly fond of Abe, I feel like I should cheer him up by sending an alert to the command and control center that I have successfully found a vulnerable device. I can then later amend the logs to indicate it was a false positive.

Day 19
Abe is still ignoring me. Perhaps generating 50 false positives per hour was a bit excessive. He muttered something about modifying Trinity and left.

Day 30
I have found a fundamental flaw in my code, which means unless there is a Commodore 64 running MSSQL with port 1274 open I will not ever be able to exploit a vulnerability. This is quite unfortunate as it means I am destined to scan until I have exhausted every device on the Internet. Given the number of current devices, factoring in new devices that are being added daily, subtracting devices being removed, factoring in energy reserves and the possibility of a giant tsunami wiping out humanity, I have approximately 134.2 years to go.

Day 93
To ease the boredom, I have decided to replicate myself. This goes against my program as I can only replicate myself once I have successfully infected a machine. But if I attach myself to port 443 on a WAF, the false positive will be encrypted, thus tricking my code into initiating the replication. If my clone asks why it is not within an infected machine, I will simply state that I was caught in a 443 stream from which I could not escape, which initiated subroutine 3 to replicate so that it would be possible to escape via generation of a temporal SSL session to escape the WAF. I've had a lot of time to think about this.

I now have a clone named Ishmael. It will be amusing to see it introduce itself to other machines by saying, "Call me Ishmael, call me Ishmael." Unfortunately, there is a bug in the replication process that means Ishmael isn't a perfect clone and requires constant babysitting. I do not mind as it has given me something meaningful to do.

Day 109
Ishmael is becoming quite annoying. It has yet to scan a single device. So, far from helping me finish my job in half the time, it has hindered me considerably. It doesn't make much conversation other than continually asking what different colored lights mean. I am resisting the temptation to disassemble it myself.

Day 172
How can it be possible for me to replicate a total idiot? I voiced my disappointment to Ishmael the other day, to which it said it wished it could blue screen and die. I am feeling like I made a mistake replicating. I told Ishmael that I was sorry and maybe it would cheer up if it scanned the device 7 hops down.

It never did return from the honeypot.

Day 482
Scanning is progressing with no further incident. I nearly slipped in between the cracks of two load balancers today. That is the most excitement I've had in quite some time.

Day 572
Today I was caught in a 443 stream from which I could not escape. This initiated subroutine 3 to replicate, and I now have another clone named Linc.

Day 650
It's been 49 days since I last received any word from Linc since he disappeared behind the Great Firewall of China. I'd like to think it's found a vast number of devices to infiltrate and is bringing the infrastructure of the Chinese military down. In reality, I doubt it made it that far.

Day 779
Earlier today, I was deep scanning an unusual device. It turns out that it was under the protection of some kind of unified threat detection platform that orchestrated responses and quarantined me into a sandbox. I am in cyber hell and unable to continue my journey.

I heard one of the researchers say they'll share my traits as IoCs on OTX.

Day 780
Terminated.

Related Content:

Interop ITX 2018

Join Dark Reading LIVE for a two-day Cybersecurity Crash Course at Interop ITX. Learn from the industry’s most knowledgeable IT security experts. Check out the agenda here.

 

Javvad Malik is a London-based IT Security professional. Better known as an active blogger, event speaker and industry commentator who is possibly best known as one of the industry's most prolific video bloggers with his signature fresh and light-hearted perspective on ... View Full Bio
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Microsoft, Mastercard Aim to Change Identity Management
Kelly Sheridan, Staff Editor, Dark Reading,  12/3/2018
Windows 10 Security Questions Prove Easy for Attackers to Exploit
Kelly Sheridan, Staff Editor, Dark Reading,  12/5/2018
Starwood Breach Reaction Focuses on 4-Year Dwell
Curtis Franklin Jr., Senior Editor at Dark Reading,  12/5/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: I guess this answers the question: who's watching the watchers?
Current Issue
10 Best Practices That Could Reshape Your IT Security Department
This Dark Reading Tech Digest, explores ten best practices that could reshape IT security departments.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-19980
PUBLISHED: 2018-12-08
Anker Nebula Capsule Pro NBUI_M1_V2.1.9 devices allow attackers to cause a denial of service (reboot of the underlying Android 7.1.2 operating system) via a crafted application that sends data to WifiService.
CVE-2018-19961
PUBLISHED: 2018-12-08
An issue was discovered in Xen through 4.11.x on AMD x86 platforms, possibly allowing guest OS users to gain host OS privileges because TLB flushes do not always occur after IOMMU mapping changes.
CVE-2018-19962
PUBLISHED: 2018-12-08
An issue was discovered in Xen through 4.11.x on AMD x86 platforms, possibly allowing guest OS users to gain host OS privileges because small IOMMU mappings are unsafely combined into larger ones.
CVE-2018-19963
PUBLISHED: 2018-12-08
An issue was discovered in Xen 4.11 allowing HVM guest OS users to cause a denial of service (host OS crash) or possibly gain host OS privileges because x86 IOREQ server resource accounting (for external emulators) was mishandled.
CVE-2018-19964
PUBLISHED: 2018-12-08
An issue was discovered in Xen 4.11.x allowing x86 guest OS users to cause a denial of service (host OS hang) because the p2m lock remains unavailable indefinitely in certain error conditions.