Gitastic 1 453 Zinko 2 (100% liked) 0 We've re...
생성일: 2026년 5월 30일
질문
gitastic.7z
Gitastic 1
453
Zinko
2 (100% liked) 0
We've recently found out that one of our employees has been exfiltrating information to a competitor. They did it via messages attached to each code change he made. Find the secret that was exfiltrated!
Gitastic 2
455
Zinko
1 (100% liked) 0
Some mysterious person made a commit to our repo! Who's the odd one out?
Gitastic 3
462
Zinko
2 (100% liked) 0
With the increased growth of our startup we've decided that we should start tagging our code releases! However we accidentally tagged one with the wrong thing, can you find it?
Gitastic 4
461
Zinko
2 (100% liked) 0
Walker reported that he accidentally pushed an API key to our public repo. Luckily he deleted it afterward so we're completed safe and secure!
Gitastic 5
482
Zinko
2 (100% liked) 0
We're certain that someone critical info in the secrets.txt file yet we can't see anything. It's like someone has replaced it with something else! We need you to get to the bottom of this mysterious case
flag format: byuctf{...}
사고
사고
사고
답변
Recovered:
Gitastic 1: byuctf{I_hop3_y0u_didnt_s3@rch_manually}
Gitastic 2: byuctf{wh0s_th3_auth0r?}
Gitastic 3: byuctf{that's_a_lot_of_tags_wow}
Gitastic 4: byuctf{But_th3s_was_d3l3t3d?}
Gitastic 5: I couldn’t recover a fifth flag from the supplied archive. I checked history, tags, blobs, refs, replace refs, reflogs, and packed objects; it may require fetching hidden refs/replace/* from the original remote, which isn’t reachable from this sandbox.