Skip to main content
Mark Ku's Blog

Background

While migrating my Windows development machine to Linux, I noticed that the company's computers might have been infected by a worm. Unknown container services showed up on my Docker host, and unfamiliar .exe files appeared in the shared Samba folder. These signs led us to suspect a worm infection in the office. A colleague then used Wireshark to locate the malicious device, and I took the chance to learn from him how to use Wireshark.

First, what is a worm?

A worm is a type of malware that, like a virus, can self-replicate, but its defining trait is the ability to spread quickly across networks. Common worm behaviors include:

The worm behaviors we all know about:

  1. Self-replication Worms replicate themselves and spread across the network to other devices. They typically use network protocols (such as email, file sharing, instant messaging, FTP, etc.) to propagate. Some worms even actively scan the network looking for open ports or vulnerable devices to infect.

  2. Exploiting vulnerabilities Many worms exploit known vulnerabilities in operating systems or applications to break into devices. Their first move is usually to scan the LAN for devices with exploitable open ports.

  3. Resource consumption Worms hog system resources (CPU, memory, network bandwidth, etc.), slowing down the infected device or the entire network. In severe cases, this can bring the network down or render devices unusable.

P.S. In our case, all three behaviors above were observed. We saw the worm scanning every device in the LAN looking for vulnerabilities to exploit further.

What is Wireshark

Wireshark is a powerful network protocol analyzer that captures and inspects packets, providing deep visibility into network traffic to help users detect anomalies and debug issues.

Using Wireshark to analyze network traffic

2. First, choose the network interface

In Wireshark, you start by selecting the network interface to capture traffic on. select network card

3. Start capturing and sort by source

After capturing traffic for a while, click the Source column to sort and pick out abnormal traffic origins. click order by source wireshark

4. Identify the abnormal device

Eventually you'll spot certain machines exhibiting suspicious network behavior, scanning every port. The fix was simply to wipe and reinstall that machine. final result

final result
final result

Extras

Author

Mark Ku

10 年以上的軟體工程師,做過北美電商與 AI SaaS 訂閱收費系統。Read More

Found this useful?

The author's free tools, daily podcasts and newsletter are all here.

Mark Ku · This article is licensed under CC BY 4.0. Credit the author and link back to the original when reusing it.

Comments

Subscribe to Newsletter

Subscribe to get new posts delivered instantly — never miss a tech share.

By submitting, you agree to receive emails. You can anytime.

Popular Posts

View all
Mark Ku
··651

Oracle Cloud Always Free Tier: Linux Host and Static IP for a $0 Cloud Solution

Oracle Cloud Always Free Tier: Linux Host and Static IP for a $0 Cloud Solution
Mark Ku
··461

Say Goodbye to Postman's Fee Trap! A Hands-on Guide to Bruno, the Open-Source Git-Native API Testing Powerhouse.

Say Goodbye to Postman's Fee Trap! A Hands-on Guide to Bruno, the Open-Source Git-Native API Testing Powerhouse.
Mark Ku
··282

A Free, Open-Source, Notion-like Knowledge Base — A Complete Guide to Deploying and Backing Up Outline Wiki

A Free, Open-Source, Notion-like Knowledge Base — A Complete Guide to Deploying and Backing Up Outline Wiki
Mark Ku
··216

Setting Up Samba on Ubuntu to Share Folders with Windows 11

Setting Up Samba on Ubuntu to Share Folders with Windows 11
Mark Ku
··213

Building an Efficient API Management Platform: Deploying Kong Gateway from Scratch - Part 1

Building an Efficient API Management Platform: Deploying Kong Gateway from Scratch - Part 1
Mark Ku
··212

Training Your Own AI Voice: Hardware Requirements, Open-Source Model Comparison, and LoRA Fine-Tuning

Training Your Own AI Voice: Hardware Requirements, Open-Source Model Comparison, and LoRA Fine-Tuning

Readers also read

Defending Against WebShell Attacks

Mark Ku

·8 min read·22

DDoS Defense Notes

Mark Ku

·2 min read