Back to catalog
Static reviewDevelopment

Skill dossier

exploiting-bgp-hijacking-vulnerabilities

Source declaration

Analyzes and simulates BGP hijacking scenarios in authorized lab environments to assess route origin validation, RPKI deployment, and BGP monitoring defenses against prefix hijacking and route leak attacks on internet routing infrastructure.

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

Analyzes and simulates BGP hijacking scenarios in authorized lab environments to assess route origin validation, RPKI deployment, and BGP monitoring defenses against prefix hijacking and route leak attacks on internet routing infrastructure.

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.

Analyzes and simulates BGP hijacking scenarios in authorized lab environments to assess route origin validation, RPKI deployment, and BGP monitoring defenses against prefix hijacking and route leak attacks on internet routing infrastructure. 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/exploiting-bgp-hijacking-vulnerabilities/SKILL.md:L50]
  • Step 1: Build an Isolated BGP Lab Environment [Source statement; provisional, not tested. Evidence: skills/exploiting-bgp-hijacking-vulnerabilities/SKILL.md:L52]
  • Step 2: Verify Legitimate BGP Routing [Source statement; provisional, not tested. Evidence: skills/exploiting-bgp-hijacking-vulnerabilities/SKILL.md:L131]
  • Step 3: Simulate Prefix Hijack (More-Specific Route) [Source statement; provisional, not tested. Evidence: skills/exploiting-bgp-hijacking-vulnerabilities/SKILL.md:L146]
  • Step 4: Simulate AS Path Prepend and Origin Hijack [Source statement; provisional, not tested. Evidence: skills/exploiting-bgp-hijacking-vulnerabilities/SKILL.md:L175]
  • Step 5: Test RPKI Route Origin Validation [Source statement; provisional, not tested. Evidence: skills/exploiting-bgp-hijacking-vulnerabilities/SKILL.md:L200]
  • Step 6: Monitor and Detect BGP Anomalies [Source statement; provisional, not tested. Evidence: skills/exploiting-bgp-hijacking-vulnerabilities/SKILL.md:L238]

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/exploiting-bgp-hijacking-vulnerabilities/SKILL.md:L1-L29]

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
30.2 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/exploiting-bgp-hijacking-vulnerabilities/LICENSEOther11 KB
skills/exploiting-bgp-hijacking-vulnerabilities/references/api-reference.mdReference1.6 KB
skills/exploiting-bgp-hijacking-vulnerabilities/scripts/agent.pyScript5.3 KB
skills/exploiting-bgp-hijacking-vulnerabilities/SKILL.mdInstruction12.3 KB

SKILL.md frontmatter

{
  "name": "exploiting-bgp-hijacking-vulnerabilities",
  "description": "Analyzes and simulates BGP hijacking scenarios in authorized lab environments to assess route origin validation, RPKI deployment, and BGP monitoring defenses against prefix hijacking and route leak attacks on internet routing infrastructure.\n",
  "domain": "cybersecurity",
  "subdomain": "network-security",
  "tags": [
    "network-security",
    "bgp",
    "routing-security",
    "rpki",
    "route-hijacking"
  ],
  "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: Build an Isolated BGP Lab Environment

    Source-described action candidate under “Step 1: Build an Isolated BGP Lab Environment”; not verified execution.

  4. 04
    Action

    Step 2: Verify Legitimate BGP Routing

    Source-described action candidate under “Step 2: Verify Legitimate BGP Routing”; not verified execution.

  5. 05
    Action

    Step 3: Simulate Prefix Hijack (More-Specific Route)

    Source-described action candidate under “Step 3: Simulate Prefix Hijack (More-Specific Route)”; not verified execution.

  6. 06
    Action

    Step 4: Simulate AS Path Prepend and Origin Hijack

    Source-described action candidate under “Step 4: Simulate AS Path Prepend and Origin Hijack”; not verified execution.

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

    Step 5: Test RPKI Route Origin Validation

    Source-described action candidate under “Step 5: Test RPKI Route Origin Validation”; not verified execution.

  2. 08
    Action

    Step 6: Monitor and Detect BGP Anomalies

    Source-described action candidate under “Step 6: Monitor and Detect BGP Anomalies”; 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

    Build a Containerlab topology replicating the organization's BGP peering with two upstream ISPs

    Source-described action candidate under “Scenario: Assessing an Organization's BGP Hijacking Resilience”; not verified execution.

  7. 13
    Action

    Verify that ROA records are correctly published for all the organization's prefixes using RIPEstat

    Source-described action candidate under “Scenario: Assessing an Organization's BGP Hijacking Resilience”; not verified execution.

  8. 14
    Action

    Simulate a more-specific prefix hijack (/25) from a rogue AS and verify that upstream ISPs with RPKI validation drop the invalid routes

    Source-described action candidate under “Scenario: Assessing an Organization's BGP Hijacking Resilience”; not verified execution.

  9. 15
    Action

    Simulate an exact-match origin hijack and verify that RPKI ROV marks the route as invalid

    Source-described action candidate under “Scenario: Assessing an Organization's BGP Hijacking Resilience”; not verified execution.

  10. 16
    Action

    Test route leak scenarios where a customer AS re-announces the provider's prefix

    Source-described action candidate under “Scenario: Assessing an Organization's BGP Hijacking Resilience”; not verified execution.

  11. 17
    Action

    Deploy BGPalerter in production to continuously monitor for unauthorized announcements

    Source-described action candidate under “Scenario: Assessing an Organization's BGP Hijacking Resilience”; not verified execution.

  12. 18
    Action

    Verify that the organization's ISPs have proper prefix filtering (IRR-based and RPKI) configured

    Source-described action candidate under “Scenario: Assessing an Organization's BGP Hijacking Resilience”; 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

36 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

10 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 10 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

23 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 23 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

2 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 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Downloaded content may be executed

This line combines retrieval and execution. Such patterns can run mutable remote code. Review pinning, integrity checks, and isolation; the analyzer performed no download or execution. This rule matched 1 location(s) in the collected text; 1 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/exploiting-bgp-hijacking-vulnerabilities/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/exploiting-bgp-hijacking-vulnerabilities/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/exploiting-bgp-hijacking-vulnerabilities
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.