Skip to content

Commit f71e702

Browse files
Update scoreboard.md
1 parent ea849d2 commit f71e702

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed
Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# Finding the scoreboard
2+
3+
## Expected result / verification
4+
Access to the scoreboard/hint page or discovery of a hidden resource; evidence: page content, new UI elements, or a flag string.
5+
6+
## Hints
7+
- Use the Pretty Print ({}) function in Sources to make minified JS readable.
8+
- Search entire sources for keywords rather than scanning files manually.
9+
10+
## Steps (exact DevTools actions)
11+
- View Page Source (right-click → View Page Source) and search for keywords like "score", "admin", or "hidden".
12+
Elements: inspect the DOM for hidden links or HTML comments that contain route hints.
13+
Sources: open bundled JS files and search (Ctrl+F) for strings like "/scoreboard", "/admin" or "flag".
14+
Console: construct the discovered path (e.g., `/scoreboard`) and navigate `window.location="/scoreboard"` or fetch it via `fetch("/scoreboard")` to view content.
15+
If the route is guarded by client checks, inspect the guard logic in Sources and try modifying client state (localStorage/cookie) accordingly.
16+

0 commit comments

Comments
 (0)