Yeah that’s also what I found while searching for more information.
1 Like
it got cracked and someone spammed ur json log this is why you dont mess with exploiters
2 Likes
These united databases is really awful idea. Like let’s remind oofd. It got hacked. This database? It got cracked too, token got leaked. That’s why it’s really bad idea. Better just implement your own methods than using united databases. Really ;-;
3 Likes
The guy who leaked the token made a bruteforcer a bit ago too
1 Like
Actually it’s not the token, but we are going to take down the database for a bit
1 Like
Then why you name this cookie as token
1 Like
you know, you have to wipe all your database since some IDs was banned by exploiters
(screen from exploiter forum)
1 Like
Thanks for letting me know. I got a backup list anyway
1 Like
Are you sure your backup list don’t have any false banned ids?
1 Like
your backup list has innocent people and users who were terminated 1-2 years ago after doing some checking. I also joined one of the “exploiters” and talked with them for a little bit and they were being honest with me and saying that they don’t even know how to exploit + You had a video star creator on the ban list
6 Likes
Another proof why these united databases useless
4 Likes
It seems that the system is down, did you take it down for maintenance or something?
1 Like
He didn’t, the person who hosted the server for him. for free did
1 Like
The token was leaked and the website’s banlist json was flooded
We just shut down the system while we fix the issues
We didn’t notice any important damage
What? Your database was flooded with a lot of innocents accounts and you say no important damage?
1 Like
asking exploiters if they cheated is like asking a murderer if he killed somebody
11 Likes
It’s now 22mb? Lol. Can I have this JSON file if you saved it?