Selfishnet V0.1 Beta [work] «UPDATED | CHEAT SHEET»

SelfishNet v0.1 Beta — Quick, Practical Guide

Understanding ARP Spoofing

Selfishnet operates primarily by exploiting the Address Resolution Protocol (ARP).

What is ARP? In a local network, devices communicate using hardware addresses (MAC addresses), but software applications identify devices by their IP addresses. ARP is the protocol used to map a known IP address to an unknown MAC address.

  1. When a device wants to communicate with another IP on the LAN, it broadcasts an ARP request asking, "Who has IP X?"
  2. The device with IP X replies with an ARP response saying, "IP X is at MAC Address Y."

The Vulnerability The ARP protocol was designed for trusted networks and lacks authentication mechanisms. Devices accept ARP responses without verifying if the sender is legitimate. This allows for "ARP Spoofing" or "ARP Poisoning."

How the Attack Works In a Man-in-the-Middle (MitM) scenario using ARP spoofing, a malicious actor sends fake ARP messages to a target device (the victim) and the network gateway (the router).

  1. The attacker tells the victim: "The router's IP is associated with my MAC address."
  2. The attacker tells the router: "The victim's IP is associated with my MAC address."
  3. This causes traffic meant for the router to go to the attacker, and traffic meant for the victim to go to the attacker.

Basic workflow

  1. Select network adapter: choose the adapter used by your LAN (typically your Wi‑Fi or Ethernet adapter).
  2. Click “Start/Scan”: the tool scans the LAN and lists connected devices (IP, MAC, hostname when available).
  3. Monitor: observe current bandwidth usage per device (upload/download).
  4. Block a device: check the box next to the device and click “Block” (or use the provided button). This typically uses ARP poisoning to disrupt that device’s access.
  5. Throttle a device: some versions provide speed-limit fields — set desired upload/download caps and apply.
  6. Release/unblock: uncheck device or click “Restore” to clear ARP spoofing and restore normal network behavior.

Security & Safety Notes

Minimal test checklist before full use

  1. Confirm admin rights and Npcap installed.
  2. Verify you are on your own network or have permission.
  3. Scan and note router IP and your device IP.
  4. Block one non-critical device to observe behavior.
  5. Restore immediately to ensure recovery works.

If you want, I can:

This paper examines SelfishNet v0.1 Beta , a lightweight Windows-based utility designed for local network bandwidth management via Address Resolution Protocol (ARP) spoofing.

SelfishNet v0.1 Beta: Localized Bandwidth Control via ARP Spoofing

SelfishNet v0.1 Beta is a network management tool that provides granular control over shared internet bandwidth without requiring administrative access to a router. By utilizing ARP spoofing techniques, the software allows a single host to intercept, throttle, or block traffic from other devices on the same Local Area Network (LAN). This paper analyzes its architectural dependencies, operational mechanisms, and security implications. 1. Introduction

In shared network environments, high-bandwidth activities by a single user can degrade performance for others. SelfishNet was developed as a portable solution to this "noisy neighbor" problem. Unlike standard Quality of Service (QoS) configurations that require router-level access, SelfishNet operates entirely from the client side. 2. Technical Framework and Requirements

SelfishNet v0.1 Beta is built on a specific stack of Windows-centric utilities: Operating System: Compatible with Windows 7, 8, 10, and 11. Driver Dependency:

(or Npcap) to facilitate low-level network packet capture and injection. Framework: Necessitates .NET Framework 3.0 or higher. Privileges:

Must be executed with Administrative privileges to manipulate the local ARP table and send forged packets. 3. Operational Mechanism: ARP Spoofing The core functionality of SelfishNet relies on ARP Spoofing (also known as ARP poisoning): Network Discovery:

The tool scans the LAN to identify the IP and MAC addresses of all connected hosts. Packet Interception:

It broadcasts "bogus" ARP responses to the network, claiming that the host running SelfishNet is the default gateway (the router). Traffic Redirection: selfishnet v0.1 beta

Neighboring devices, believing the host is the router, redirect their outbound traffic to the host instead of the actual gateway. Throttling/Blocking:

The host then applies user-defined limits on upload/download speeds or drops packets entirely ("Blocking") before forwarding legitimate traffic to the real router. 4. Features and Limitations Key Features Real-time Monitoring:

Displays active IP addresses, MAC addresses, and current bandwidth usage. Capacious Control:

Users can manually input specific KB/s limits for both upload and download streams. Access Revocation:

A toggle switch to completely sever a device’s internet connection. Limitations Volatility:

Settings are not persistent; they revert to default if the application is closed or the host machine is rebooted. Platform Lock-in: Native support is restricted to Microsoft Windows. Resource Intensity:

Redirecting all network traffic through a single PC can consume significant CPU and local bandwidth. 5. Security and Ethical Considerations

SelfishNet is frequently classified as a "grey-hat" tool. While useful for personal bandwidth management, its underlying mechanism is a form of network attack. Detection:

Modern antivirus programs often do not flag the binary itself, but sophisticated Network Intrusion Detection Systems (NIDS) can identify the ARP poisoning signatures. Mitigation:

Network administrators can defend against SelfishNet by implementing static ARP entries, port security, or Dynamic ARP Inspection (DAI) on managed switches. 6. Conclusion

SelfishNet v0.1 Beta remains a popular utility for users seeking immediate, router-less network control. However, its reliance on ARP spoofing makes it a disruptive tool that can be easily mitigated in professional or secured network environments. Users are advised to use such tools only on networks they own or manage to avoid violating acceptable use policies. defensive strategies

to protect your own devices from being throttled by SelfishNet, or would you prefer a step-by-step setup guide for the software?

Control your internet bandwidth with SelfishNet v3. - GitHub SelfishNet v0

Mac Spoofing. See how many devices are connected to your network. Check the IP's and Mac addresses of the devices on your network.

SelfishNet v0.1 Beta is a legacy network management utility designed to give users granular control over bandwidth distribution on a local area network (LAN). Originally developed for Windows, it gained notoriety as a "net-cut" style tool that allows an individual to prioritize their own connection by restricting or completely blocking the internet access of other devices on the same Wi-Fi or Ethernet network. Functionality and Mechanism

At its core, SelfishNet operates using ARP Spoofing (Address Resolution Protocol poisoning). By intercepting the communication between the router and other connected devices, the software can trick the network into routing traffic through the user’s computer. This allows the user to see every device currently connected to the network, including their IP and MAC addresses.

Once the devices are identified, the "v0.1 Beta" interface offers two primary controls:

Cap: Users can set a specific limit (in KB/s) on the download and upload speeds of any device.

Block: Users can check a "Block" box to completely sever a device's connection to the gateway. The Appeal of the Beta Version

Despite being an early beta release, version 0.1 remains the most widely circulated version of the software. Its appeal lies in its simplicity and portability. It does not require a complex installation process—often running as a simple executable—and features a utilitarian interface that requires no technical expertise to navigate. For users in shared living spaces or public Wi-Fi environments struggling with "bandwidth hogs," SelfishNet provides an immediate, albeit aggressive, solution. Ethical and Technical Risks

The use of SelfishNet is controversial and carries significant risks:

Ethical Concerns: Manipulating a shared resource without consent is generally considered a breach of social and digital etiquette. In professional or educational environments, it may violate Acceptable Use Policies (AUP).

Security Risks: Because the software is old, unmaintained, and often hosted on third-party "freeware" sites, downloads are frequently bundled with malware or adware.

Network Stability: ARP spoofing can cause network instability or "IP conflicts," which may alert a network administrator to the presence of unauthorized management tools. Conclusion

SelfishNet v0.1 Beta represents a "quick-fix" era of network tools. While it remains a powerful instrument for personal bandwidth management, its reliance on intrusive protocols like ARP spoofing makes it a double-edged sword. It serves as a reminder of the inherent vulnerabilities in local network protocols and the ongoing tension between individual utility and collective access.

Selfishnet v0.1 beta

Log entry: Day 47 of solo survival in the Buffer Zone.

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.