Incident Responder

85MB
Open

Since we know the final attack chain was lambda function that encrypts stuff, lets try from the last step.

Grepping for encrypt, we can see that it encrypts the s3://hexnovadatabreach-databreach-content-dolphin/ImportantInformation.txt as well as the dynamodb/HevNovaDataBreachDynamoDB-databreach.

We are also given the API gateway URL for the lambda function

Trying to POST the the prod stage give us a 404 not found error

Playing around with the route, we managed to get a response out of the API Gateway.

It returns the encrypted important information.txt Doign a quick google, the gAAAA encryption is fernet encryption.

Looking at the CloudWatch log, we managed to find the encryption key.

Wrtiting a quick solve script we are able to get part1 of the flag.

For Part2, the flag is in the dynamodb.

I used LLM to write another solve script to parse the output and get the flag.


During the CTF, I tried to submit FLAG{R35p0nd_N0w_D1sc0v3r_F0r3ns1cs} as the flag but it failed. So I thought that there were another part and wasted alot of time trying the parse the logs to find something different.

It is only until after the CTF ends then I realized I had formatted the flag wrongly 🤦‍♂️

The flag format is FLAG-{R35p0nd_N0w_D1sc0v3r_F0r3ns1cs}

Last updated

Was this helpful?