> For the complete documentation index, see [llms.txt](https://lance-kenji.gitbook.io/me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lance-kenji.gitbook.io/me/swimmer-osint-ctf-2026-writeups/tgt_dabeyohiru/dabeyohiru_05_hidden1.md).
# dabeyohiru\_05\_hidden1
#### Challenge Overview
The task is to determine the **legal name** of the user `debeyohiru/furaigo5`. We are given access to their public profile page and are instructed to identify the real name in Latin alphabet, ignoring Kanji or Hiragana.
***
#### Initial Assumptions
1. **Public Source Only**: We cannot contact the user directly or access private accounts. Only lawful OSINT methods are allowed.
2. **Metadata Clues**: Usernames, profiles, and website scripts often contain author or creator metadata.
3. **File References**: JavaScript or HTML source files are potential sources of author information.
***
#### Investigation Process
**Step 1: Inspect the Profile Source**
* Visited `https://furaigo5.github.io/profile/index.html`.
* Explored the page structure and located the linked JavaScript file: `/js/script.js`.
**Step 2: Examine the JavaScript File**
* Opened `/js/script.js` and checked the **header comments**.
* Found the **author** **metadata** clearly stated:
```
/**
* @fileoverview furaigo5 Workspace - メインスクリプト
* ナビゲーションのスムーズスクロールとモバイルメニューの制御を担当
* @author Gotanno Tsubasa
*/
```
* The `@author` tag reveals the user’s real name.
* 
***
#### Key Findings
* **Source**: /js/script.js linked from profile
* **Author / Real Name**: Gotanno Tsubasa
***
#### Final Flag / Answer
```
SWIMMER{Gotanno Tsubasa}
```
***
#### Notes & Takeaways
* **Check Source Files**: Even when profiles appear anonymous, author metadata in scripts, HTML, or CSS can reveal real names.
* **OSINT Principle**: Always start with publicly available sources and inspect client-side files before attempting deeper investigation.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://lance-kenji.gitbook.io/me/swimmer-osint-ctf-2026-writeups/tgt_dabeyohiru/dabeyohiru_05_hidden1.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.