Crowdsourced TIA frontend client binary reverse engineering effort
The Challenge is over.
Running assets is always difficult, however this year has been excruciating for t2. We lost one of our most prized and well placed deep cover operatives in a foreign three letter agency. Shortly after the CFP, communications stopped and we have to assume his/her new assignment is a permanent placement at a black site somewhere in Eastern Europe.
Luckily for us, the person was able to exfiltrate a key piece of an intelligence analysis system before disappearing. In order to turn the tables and go for the pride-and-ego down, our intention is to burn this capability once and for all.
Y-LOCKPOINT is designed for searching and analyzing compromised computer systems. Despite the OPSEC failures, which allowed us to gain access to front-end application, the binary is well-protected – preliminary analysis indicates emphasis on multi-layer protection and resistance to analysis.
Your mission, should you choose to accept it, is to participate in the crowdsourced reverse engineering effort of the acquired front-end binary.
The Challenge will be released on 2014-09-13 10:00 EEST.
The first person to enter all correct SHA1s will win a free ticket to t2’14 conference. In addition to this, the creators of the Challenge will select another winner among the next ten correct answers. The criteria for the other selection is the elegance of the answer. In short, you can win with both speed and style. Either way the solution must include a detailed description of methods and tools used.
If you don’t know what is the definition of elegance – please check out the winning write-ups from previous years.
Rules of the Challenge
- Anybody can participate, excluding the organizers and employees of the companies that made the challenge.
- The answer must have a detailed description of the methods and tools used.
- It is not allowed to publish the solution on public forums before the challenge is over.
- It is not allowed to modify or redistribute the challenge files.
- All rights are reserved.
Filesize: 19 343 984 bytes
Ideas and implementation: Timo Teräs, Tomi Tuominen