Back to catalog
Static reviewDevelopment

Skill dossier

performing-bandwidth-throttling-attack-simulation

Source declaration

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.

The author's original description, preserved in English. It describes intent, not verified performance.

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.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

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. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/performing-bandwidth-throttling-attack-simulation/SKILL.md:L56]
  • Step 1: Establish Baseline Bandwidth Measurements [Source statement; provisional, not tested. Evidence: skills/performing-bandwidth-throttling-attack-simulation/SKILL.md:L58]
  • Step 2: Simulate Bandwidth Throttling with tc/netem [Source statement; provisional, not tested. Evidence: skills/performing-bandwidth-throttling-attack-simulation/SKILL.md:L81]
  • Step 3: Simulate Progressive Degradation [Source statement; provisional, not tested. Evidence: skills/performing-bandwidth-throttling-attack-simulation/SKILL.md:L112]
  • Step 4: Simulate Slowloris-Style Connection Exhaustion [Source statement; provisional, not tested. Evidence: skills/performing-bandwidth-throttling-attack-simulation/SKILL.md:L150]
  • Step 5: Measure Impact and Detect Anomalies [Source statement; provisional, not tested. Evidence: skills/performing-bandwidth-throttling-attack-simulation/SKILL.md:L212]
  • Step 6: Clean Up and Document [Source statement; provisional, not tested. Evidence: skills/performing-bandwidth-throttling-attack-simulation/SKILL.md:L239]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-bandwidth-throttling-attack-simulation/SKILL.md:L1-L31]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
31.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-bandwidth-throttling-attack-simulation/LICENSEOther11 KB
skills/performing-bandwidth-throttling-attack-simulation/references/api-reference.mdReference2.2 KB
skills/performing-bandwidth-throttling-attack-simulation/scripts/agent.pyScript6 KB
skills/performing-bandwidth-throttling-attack-simulation/SKILL.mdInstruction12.2 KB

SKILL.md frontmatter

{
  "name": "performing-bandwidth-throttling-attack-simulation",
  "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.\n",
  "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"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Establish Baseline Bandwidth Measurements

    Source-described action candidate under “Step 1: Establish Baseline Bandwidth Measurements”; not verified execution.

  4. 04
    Action

    Step 2: Simulate Bandwidth Throttling with tc/netem

    Source-described action candidate under “Step 2: Simulate Bandwidth Throttling with tc/netem”; not verified execution.

  5. 05
    Action

    Step 3: Simulate Progressive Degradation

    Source-described action candidate under “Step 3: Simulate Progressive Degradation”; not verified execution.

  6. 06
    Action

    Step 4: Simulate Slowloris-Style Connection Exhaustion

    Source-described action candidate under “Step 4: Simulate Slowloris-Style Connection Exhaustion”; not verified execution.

Inspect all extracted workflow candidates (19 candidate steps)
  1. 07
    Action

    Step 5: Measure Impact and Detect Anomalies

    Source-described action candidate under “Step 5: Measure Impact and Detect Anomalies”; not verified execution.

  2. 08
    Action

    Step 6: Clean Up and Document

    Source-described action candidate under “Step 6: Clean Up and Document”; not verified execution.

  3. 09
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  4. 10
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  5. 11
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  6. 12
    Action

    Establish baseline call quality using iperf3 UDP tests measuring jitter (<30ms) and packet loss (<1%) on the VoIP VLAN

    Source-described action candidate under “Scenario: Testing VoIP System Resilience to Bandwidth Degradation”; not verified execution.

  7. 13
    Action

    Set up MITM position between VoIP endpoints using ARP spoofing

    Source-described action candidate under “Scenario: Testing VoIP System Resilience to Bandwidth Degradation”; not verified execution.

  8. 14
    Action

    Progressively introduce latency (50ms, 100ms, 200ms, 500ms) using netem and measure MOS (Mean Opinion Score) at each level

    Source-described action candidate under “Scenario: Testing VoIP System Resilience to Bandwidth Degradation”; not verified execution.

  9. 15
    Action

    Introduce packet loss (1%, 3%, 5%, 10%) and measure call quality degradation

    Source-described action candidate under “Scenario: Testing VoIP System Resilience to Bandwidth Degradation”; not verified execution.

  10. 16
    Action

    Throttle bandwidth from 1 Mbps to 100 Kbps to determine the minimum usable bandwidth for G.711 codec (requires 87.2 Kbps)

    Source-described action candidate under “Scenario: Testing VoIP System Resilience to Bandwidth Degradation”; not verified execution.

  11. 17
    Action

    Verify that QoS policies on the network prioritize VoIP traffic and restore quality when throttling affects the shared link

    Source-described action candidate under “Scenario: Testing VoIP System Resilience to Bandwidth Degradation”; not verified execution.

  12. 18
    Action

    Document the degradation thresholds and recommend minimum QoS guarantees for the VoIP VLAN

    Source-described action candidate under “Scenario: Testing VoIP System Resilience to Bandwidth Degradation”; not verified execution.

  13. 19
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

53 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

6 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

27 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 27 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

20 occurrences

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 20 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-bandwidth-throttling-attack-simulation/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/performing-bandwidth-throttling-attack-simulation/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-bandwidth-throttling-attack-simulation
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.