awesome-selfhosted VS CyberChef

And of course, look at the subreddit sidebar, find the awesome-selfhosted list and work your way through that. There is also a big fat sticky "Please read this first" thread that you ignored.

You could start off by taking a look at this list from the subreddit sidebar: https://github.com/Kickball/awesome-selfhosted

The list from the subreddit sidebar has a lot of options for you to look at and try out: https://github.com/Kickball/awesome-selfhosted

Interesting, never heard of this before. You may want to make a "product announcement" post about it here in the sub to make more people aware of it. And maybe get it added to the list that is in the sub sidebar.

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...