JASKEERAT SINGH a.k.a. paino5
All writeups
Writeup 02 — OSINT UK Flags — 4 / 4 captured

Operation Cord

Discord Platform Forensic & Application Auditing

Challenge Summary

This challenge focused on platform-specific digital forensics targeting Discord infrastructure, including account metadata identification, cryptographic snowflake tracking, hidden web data extraction, and community intelligence analysis. All discovered intelligence vectors have been cross-referenced with the operational tracking dossier Op_Cord.md.


1. Discord Profile Account Enumeration

  • Methodology: Turned on "Developer Mode" in Discord settings. Located the user profile for "Nathaniel" and right-clicked the name to copy the unique user ID.
  • Verification Reference:

    Discord profile card for the user “Not Nathaniel” with the account context menu open and the “Copy User ID” option highlighted.
    Discord profile with the “Copy User ID” context-menu option visible.
  • Flag Data:

    Click to reveal flag
    osintuk{1191511485365616671}

2. Snowflake Cryptographic Timeline Analysis

  • Methodology: Took the Discord user ID from the first step and plugged it into an online Discord Snowflake converter tool. This revealed the exact account creation time, allowing the collection of the Unix timestamp in milliseconds.
  • Verification Reference:

    Output of a Discord Snowflake to Timestamp converter, showing the snowflake 1191511485365616671 resolved to 1704148875324 Unix milliseconds.
    Snowflake converter output for the user ID recovered in step 1.
  • Flag Data:

    Click to reveal flag
    osintuk{1704148875324}

3. Hidden Application Layer Data Extraction

  • Methodology: Inspected the challenge page and zoomed into the text elements. Found a hidden hyperlink written in tiny font, which contained a Base64 string (data:text/plain;base64,bXV0aW55bW9ja291dHNpbg==). Decoded this text to reveal the hidden flag.
  • Verification Reference:

    Zoomed-in challenge page text showing the answer format, including the instruction to use the osintuk{answer} format and that numbers only are accepted.
    Zoomed text elements on the challenge page.
  • Flag Data:

    Click to reveal flag
    osintuk{mutinymockoutsin}

4. Community Signature Discovery

  • Methodology: Looked at the core focus of the entire challenge, which centered on the specific community and its founders, making the final answer clear based on the hosting group.
  • Verification Sources: Core challenge architecture metrics
  • Flag Data:

    Click to reveal flag
    osintuk{ukosintcommunity}