SKIP TO MAIN CONTENT

[ WRITEUP NODE / FIELD REPORTS ]

SOLVED CHALLENGES & FIELD ANALYSIS

SECURITY RESEARCH KNOWLEDGE TECHNIQUES
B3S/WRITEUPS/DNS-HISTORIC-RECORDS-BASIC-CLOUD
← BACK TO ARCHIVE
EVENT: Cyberweek Africa Qualifiers 2026CATEGORY: CloudPOINTS: 150 PTS

Dns Historic Records

AUTHORED BY:@bealthguy10/5/2026

Dns Historic Records

Category: CLOUD · Difficulty: Basic · Points: 150 · Challenge: 527

Background

A company migrated its internal administrative panel behind a private tunnel, but historic DNS records still log the original public IP coordinates. Identify the historical records. 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-085.json | while read -r s; do \
    printf '%s' "$s" | base64 -d 2>/dev/null; echo; done
RkxBR3tjd2EyMDI2X2M2YmE5NGI3NDQ5ZDk3NmV9
FLAG{cwa2026_c6ba94b7449d976e}

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_c6ba94b7449d976e}