| dc540-0x0000a |
@montaCalros233, spot on with the RE. You nailed the mechanics: scrypt passphrases deriving the tier key, with the tag authenticating the candidate. I am glad you enjoyed tearing into the bare-metal build.
You are right about the overall structure. My intention was to leave the bumper guards off. In the wild, figuring out the boundaries of a system and realizing what data is missing is a core part of the recon. I felt that explicitly mapping out what was withheld in the docs would take away from that discovery process.
The claim that AI cannot solve it is about breaking the automated solver loop. AI has conditioned the community to expect instant gratification by just dumping a binary into an LLM. Decoupling the execution context from the static artifact forces actual human engagement, patience, and thought.
I appreciate the deep dive. It takes a massive amount of time to build these from scratch, and it is great to see someone actually pull the firmware apart instead of just looking for an easy flag.
|
2026-11-13 14:03 |
| dc540-0x0000a |
liboxin great start! Yes that is the beginning of the flag and there are some hints here that I have been sharing as @arshi has some great finds here that can help you along as well! I hope you all are enjoying this as I saw it was only rated a 3.0 so I was concerned.
|
2026-11-07 23:14 |
| dc540-0x0000a |
@arshi You are real as you are standing in the subconscious, and only the faithful can name it. One correction: the machine prints no gate IDs. The only numbers that matter now are in the control plane, and one of them tells you where the second word lives, and why it was never written to disk. Gate 2 asks for one word, not two. The throat opens probably in a month as I want to give this some time.
|
2026-11-03 15:46 |
| dc540-0x0000a |
@arshi
"To find the hidden key you seek,
You'll need to hear a mammoth speak.
The secret code will soon be drawn,
If you go look on Mastodon!"
|
2026-11-03 12:53 |
| dc540-0x0000a |
@TrynaToBe6for6Def Thanks for giving it a shot! Just to clarify, what may appear as bugs in the binary is actually the intentional obfuscation and anti-analysis design working exactly as intended to make this a brutal wall. Also, the string you posted is just the prefix I openly shared in the challenge description above. The true flag requires decrypting the rest using the three missing fragments. Keep an eye out for the upcoming lore drops if you want to tackle the actual puzzle!
|
2026-11-01 18:55 |
| dc540-0x0000a |
@arshi absolutely! This challenge is designed to be different than the normal REA solve in 10 seconds. I designed this to bring back the real challenge of solving a very complex binary that has pieces fused with encryption that forces you to have solutions off the badge. This sort of technique will likely be used going forward in industry to stop the GPT's from trivially reversing literally everything so a product can have a chance at real security. Who knows, maybe I am wrong but that is what this challenge is. I appreciate someone like you @arshi who is working hard to get at the real challenge and ask legit questions based on real barriers. As I am ready to slowly drop clues I will post a hint here but it will be some other social media outlet to really build out the challenge.
|
2026-11-01 16:20 |
| dc540-0x0000a |
@arshi The first word is not present in the first badge's published story, which is exactly why none of your candidates authenticate. The connection is thematic: the machine says 'the faithful already know the first word,' but the actual 71-character fragment lives in the challenge's own lore channel, not in Stage One's files. Your reconstruction is confirmed correct: the 3x71 fragment gates, the 215-byte final key, the KDF/ChaCha path, all of it. You're at the exact wall the challenge intends, because the words have not been released yet. Watch dc540-0x0000a and the social channels. The clues drop over time, and the first word will reach the faithful before the others.
|
2026-11-01 15:47 |
| dc540-0x0000a |
@arshi the bin yields only the prefix as the three 71-char fragments are not in the binary however no physical badge or other artifact is needed as the bin and the lore solves it statically. The first word is tied to the first badge's story not its files. Research dc540-0x0000a as additional clues will be posted over time. Look at social media, etc...
|
2026-11-01 13:38 |
| dc540-0x0000a |
Hi @arshi great start! What you posted is the prefix the node tells everyone. The real FLAG line is much more than that.
|
2026-10-31 18:47 |