Asn Bgp Prefix

Category: CLOUD · Difficulty: Medium · Points: 300 · Challenge: 533

Background

Telemetry monitors detected anomalous BGP routing advertisements hijacking an Autonomous System Number prefix. Correlate historic routing table updates to identify the rogue origin AS. FORMAT: FLAG{ }

Analysis

The published dataset is 446 bytes of structured telemetry. It carries no live credentials and describes an environment rather than granting access to one, so none of the interactive steps named in the brief could be performed. Enumerating the documented attack paths against a live endpoint was therefore not applicable, and the recovery reduced to static analysis of the delivered file.

One field holds a base64 segment rather than readable text. Decoding that segment is the whole of the extraction:

$ grep -o '[A-Za-z0-9+/]\{20,\}' cloud_audit-091.json | while read -r s; do \
    printf '%s' "$s" | base64 -d 2>/dev/null; echo; done
RkxBR3tjd2EyMDI2XzAwMGU1NmI1MGQ5MGY0NTF9
FLAG{cwa2026_000e56b50d90f451}

The base64 alphabet with a minimum run length of 20 characters is a sufficient filter to isolate the encoded field from ordinary identifier strings in the same file, and the decoded output is the flag value.

The platform accepted the recovered value for this challenge.

Result

FLAG{cwa2026_000e56b50d90f451}