It is a digital fossil. Unless you are restoring an old Windows XP LAN party machine for nostalgia, skip it. The code is buggy, the security holes it exploits have been partially patched by modern router firmware (like ARP protection), and the legal risk isn't worth the "fun."
If you want to learn network security: Install Kali Linux on a VM, learn arpspoof and BetterCAP. They do what SelfishNet tried to do, but correctly and safely.
Have you found a working copy of SelfishNet in the wild? Drop a comment below (for historical documentation only, of course).
Stay ethical, stay curious, and always ask for permission before poking the network.
The following is a draft white paper for Selfishnet v0.1 Beta, a legacy network management utility used for controlling bandwidth allocation on local area networks (LAN). Technical Overview: Selfishnet v0.1 Beta
Date: April 26, 2026Subject: Local Area Network Bandwidth Management and Traffic Shaping 1. Abstract
Selfishnet v0.1 Beta is a lightweight, portable network utility designed for Windows-based systems to provide granular control over LAN traffic. By utilizing the WinPcap library, the software enables administrators to discover connected devices and manually throttle or block their upload and download speeds. This paper outlines its architectural dependencies, core functionality, and operational requirements. 2. Technical Prerequisites
Selfishnet is not a standalone executable; it operates as a wrapper for packet capture drivers. To function, the following must be present:
Packet Driver: Installation of WinPcap or Npcap is mandatory for the software to interface with the Network Interface Card (NIC).
Archiving Tool: Users must use tools like 7-Zip or WinRAR to extract the portable binary from its distribution archive.
Privilege Level: The application requires "Run as Administrator" permissions to execute low-level ARP (Address Resolution Protocol) spoofing commands. 3. Core Functionality
Selfishnet operates primarily through ARP Spoofing, allowing it to position the host machine as a "man-in-the-middle" between the router and other networked devices. Key Features: selfishnet v0.1 beta
Device Discovery: Scans the local network to list all active IP and MAC addresses.
Real-time Monitoring: Displays current bandwidth consumption (download/upload) for every detected node.
Bandwidth Throttling: Allows the user to input specific KB/s limits for targeted devices.
Network Blocking: Provides a "Block" checkbox to completely drop packets for specific devices, effectively disconnecting them from the internet without physical access. 4. Operational Workflow
Interface Selection: Upon launch, the user selects the active Network Interface Controller (Ethernet or Wi-Fi).
Network Discovery: Clicking the "Network Discovery" icon populates the device list.
Redirection: Clicking "Start Redirecting" initiates the ARP spoofing process, bringing all LAN traffic through the host machine.
Control: The administrator modifies the "Download" or "Upload" columns to enforce traffic shaping policies. 5. Security and Ethical Considerations
Selfishnet is frequently categorized as a "grey-hat" tool. While useful for troubleshooting network congestion, it can be used maliciously to deny service to others on a shared network. Modern routers with ARP Inspection or Source Guard may detect and mitigate Selfishnet’s activities.
Selfishnet v0.1 beta
Log entry: Day 47 of solo survival in the Buffer Zone. It is a digital fossil
I didn’t mean to break the network. I just wanted a little more bandwidth for myself.
When the Collapse happened, the meshnet was supposed to keep everyone connected. Decentralized. Resilient. Every node shares, every node gains. That was the theory. In practice, people hogged, leeched, and lied about their relays. So I wrote a patch. A tiny fork of the routing protocol. I called it Selfishnet — version 0.1 beta.
It didn't disable sharing. It just prioritized my packets. My survival data. My map updates. My medical alerts. Everything else — neighbors' requests, emergency reroutes, the old lady two floors down trying to call her son — got shuffled to the back of the queue.
At first, it worked beautifully. My latency dropped. My scavenging routes updated in real time. I found clean water before anyone else.
But networks have memory. And selfishness is contagious.
Within three days, other nodes started behaving like mine. Not because they had my patch — because the network adapted. Packets from selfish nodes arrived faster, so relays learned to favor them. Altruistic nodes became invisible. Then irrelevant. Then dead.
By week two, the mesh had fractured into islands of mutual suspicion. No node trusted another unless it saw proof of selfish behavior first. My own logs showed my node talking to only four others — all running versions of Selfishnet they'd compiled themselves.
We didn't collapse the network. We optimized it. For a world where nobody helps unless forced.
Now I sit here, battery at 12%, listening to static. The last packet I received wasn't a map or a warning. It was a ping from a node I don't recognize. The payload?
Selfishnet v0.2 alpha — now with betrayal detection.
I should delete my patch. I won't. That's the problem with beta software. Once you see how the world really works, you can't uninstall it. Stay ethical, stay curious, and always ask for
Today, the term "selfish" in networking has evolved. Ethical hacking emphasizes collaboration. However, the red team mindset—where you assume everyone on the network is adversarial—was popularized by tools like SelfishNet. It taught us that on a shared medium (Wi-Fi), trust is a vulnerability.
Cooperative protocols (e.g., AODV, OLSR) assume all nodes forward packets altruistically. However, real-world nodes may act selfishly to save resources. Existing simulators (NS-3, OMNeT++) require extensive configuration. SelfishNet v0.1 Beta fills the gap with a minimal, focused simulation environment.
If you are a cybersecurity student and want to replicate what SelfishNet v0.1 beta did, do not download the original beta from random file repositories (they are often packed with malware). Instead, use modern, safe methods:
Use modern ARP tools: Open a terminal on Kali and use:
sudo arpspoof -i eth0 -t 192.168.1.10 192.168.1.1
This replicates SelfishNet’s core MITM function.
Enable IP forwarding:
sudo sysctl -w net.ipv4.ip_forward=1
Now you are intercepting traffic without breaking the connection.
Use driftnet to replace images: (The modern analog to SelfishNet’s image replacement)
sudo driftnet -i eth0
It is impossible to discuss SelfishNet v0.1 beta without addressing the elephant in the room: Using it on a network you do not own is a crime.
In most jurisdictions, ARP poisoning falls under:
Even in v0.1 beta, the tool could capture unencrypted traffic. In 2025, most websites use HTTPS, but back in the XP/Vista era, HTTP was rampant. SelfishNet could easily capture login credentials for forums, email accounts (POP3/IMAP without SSL), and FTP servers.
Responsible use cases at the time included: