chaos-coder
chaos-coder copied to clipboard
Infinite coins
I think it's how they process the information. Several requests are sent to supabase to check how many coins they have, and then when the coins are spent, a request is made to supabase to tell it how many are left. Well, if all those requests and responses are captured and the number of coins is modified, the result is that you can have infinite coins. It's actually very complicated to find this bug, and I don't think it can be fixed unless you change how requests are handled. Since technically you don't have a backend, you have to send all the data through the frontend.
This is the application where the user's credits are verified. If any changes are made, they are only reflected in the interface.
This is the application where the user's credits are verified. If changes are made, they are only reflected in the interface.
This is the dangerous request, because it tells supabase how many credits I have, and that's what I can move and everything I put in will be put into the database.
This is the one that confirms to me that the change was made in the database.
And so I permanently have the coins I want.
Thank you for reporting this @LeoValdi64 !