-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LabyREnth threat4 (yara1) #1
Comments
Lucky — yes. But still, it solved the problem… that is not what I call horribly wrong… maybe unintended :-) Problems were two sets should be separated (I’m guessing they used yara in the background on the server) can be solved by a sufficient number of random queries, so guessing is a strong method. |
So it means they didn't even check how these sets were created by your rule cause the intended one and yours produce completely different output in the meaning of match/not match. |
Yeah... anyways, thanks for providing your solution. I will make a reference in the write-up. |
Lool, really really lucky.
The intended solution was that you again have appended data in each file, 3 different in 6 files. After messing with it a bit you get XOR key 0x26 and decrypted texts:
Next, it looks like base64 but decrypts to nonsense. There is
ROTXOR
in end of each text, after a waaay long thinking and trying you get that you actually need to rotate base64 alphabet by XOR key (also need to replace+
with-
). Code:gets you this text:
So after filling the rule like this:
you get the answer.
After all, your solution is horribly wrong and still you got the answer, very lucky :) And the challenge itself is broken very hard, my rule didn't work when I swapped two strings in it.
The text was updated successfully, but these errors were encountered: