I think it's by design. You're overriding the "query" key in the JSON object. When GraphQL (assuming JS impl.) retrieves the value for the "query" key, the value of the last declared key will be returned only. I'm not sure if other languages behave differently.

Looks like the recalculation is already being done after the first 10 bounties are rewarded, according to their docs: docs.hackerone.com/hackers/r…. Definitely prefer the way it works now. Reputation based on the set severity level wouldn't work out.

The title of this book.

Most effective PR of the year? 👌🏽😅

#1337up1119 was amazing. Met a lot of cool people, and learnt a lot. It was amazingly well organized as well, so props to the @intigriti team for that! It's an honour to receive an award for my PoC, thank you!

Simple example in PHP. It happens ¯\_(ツ)_/¯

hi

I've become lazy to test endpoints for JSONP functionality, so I decided to create a Burp extension. It attempts to find JSONP functionality behind every request responding with content-type application/json, on the fly. Check it out at github.com/kapytein/jsonp!

late to the party, but this happened on Monday 😢

Good luck man!