AutoHotkey VS CyberChef

AutoHotkey is what made me fall love programming after disliking it after getting my degree. After switching to a macbook, AutoHotkey is probably what I miss most from being on Windows. It really has it all.

My old suite had:

- Universal VIM movement w/ CapsLock

- App launch hotkeys

- App-specific hotkeys

- Easy text-expansion

Hasn't been updated in years, but here is the repo for those interested: https://github.com/denolfe/autohotkey

Or a nice boilerplate to start from: https://github.com/denolfe/AutoHotkeyBoilerplate

I used to be a very heavy AHK user and developer a rather extensive config. Here is my config along with a boilerplate to help you start one that is similar:

- https://github.com/denolfe/AutoHotkey

Then we take the encrypted text and use CyberChef to decrypt it.

Let's go to CyberChef and insert our pieces of evidence.

A parameter was changed from '2AMBCgIQBg' to 'CgIIAdgDAQ%3D%3D' which is just the correct base64 encoding they should have been using the entire time.

I don't think this was a hostile action by Google, I think someone just added better input validation for security reasons and it accidently broke the bad requests they were sending.

https://gchq.github.io/CyberChef/#recipe=URL_Decode()From_Ba...

❗This is indeed the flag, but the text is encrypted with Base64. Usually, the presence of padding character "=" indicates that's Base64 type of encoding (but that's only one of the hints). To decrypt it, we can use CyberChef. Copy-paste the text and we either:

It uses a combination of magic bytes (like the `file` command), entropy analysis and character frequency detection to determine whether an output is likely to be of interest to the user.

The file type mechanism is written here[0]. There's a list of all signatures we detect here[1].

[0] https://github.com/gchq/CyberChef/blob/master/src/core/lib/F...

I think this can be deciphered using CyberChef...