-
Marco_KO, today at 07:23 pm CEST
-
upola, yesterday at 06:06 pm CEST
-
cislok, on 14th Apr. 2025 at 02:07 pm CEST
-
Langhans_innen, today at 07:34 pm CEST
-
Ariana, today at 07:26 pm CEST
-
frapi07, today at 06:33 pm CEST
-
Leemoni, today at 05:57 pm CEST
-
Max_Bet, today at 05:56 pm CEST
-
kenne32, today at 05:12 pm CEST
-
Pat1991, today at 05:08 pm CEST
-
roccoammo11, today at 04:27 pm CEST
-
tapsi, today at 11:29 am CEST
-
olum29, today at 12:31 am CEST
-
gagapapamama, yesterday at 08:47 pm CEST
-
roccoammo11, yesterday at 03:34 pm CEST
-
TonioKroeger, on 14th Apr. 2025 at 11:31 pm CEST
-
Langhans_innen, on 14th Apr. 2025 at 06:31 pm CEST
-
taylor3733, on 14th Apr. 2025 at 04:41 pm CEST
-
streetworksusi, on 14th Apr. 2025 at 07:46 am CEST
-
Memoak447, on 13th Apr. 2025 at 02:10 am CEST
-
Babatyp, on 13th Apr. 2025 at 01:11 am CEST
-
frapi07, on 12th Apr. 2025 at 10:06 pm CEST
-
roccoammo11, on 12th Apr. 2025 at 04:09 pm CEST
-
Zockerbernd, on 11th Apr. 2025 at 11:32 pm CEST
-
Leemoni, on 11th Apr. 2025 at 10:56 pm CEST
Hacker attack on Merkur Bets
Liked this post:
bigbig,
Danny0815,
Donnie,
gamble1,
Max_Bet
Yes, that's also the next problem. Of course you can't guarantee anything. But the stalls claim that no one else had access to it. They couldn't possibly know that. You can also find statements (or emails) here where they write false facts. I don't want to imply whether this is done deliberately, but it has already happened to some people here. Example: GGL would have discovered this security gap, the hacker did not want to misuse the data (although the misuse had already taken place).
I'm not an IT expert, but I'm interested in how the hacker did it. We read that a GraphQL of an API was the cause of this vulnerability. This GraphQL had inadequate authorization, which allowed the data to be retrieved. So it wasn't an infiltrated virus, a Trojan or a phishing email, no - it simply wasn't secured well enough.
Maybe I'm a noob, but I think that every computer scientist has worked with GraphQL or has already dealt with it. I've read that many companies use it, precisely because GraphQL is very efficient at querying data. I don't want to put my hand on the fire, but I think quite a few could have abused this loophole.
This post has been translated automatically
Hacker attack on Merkur Bets
Liked this post:
frapi07
Hello,
I come from the IT industry and yes, with expert knowledge, anyone could have done this. It was not a direct hack. The data was visible to anyone with some experience due to the gap in the interface. But it's really not easy to exploit this error.
And there really are these "hackers" who point this out positively without any ulterior motives or blackmail etc.
This post has been translated automatically
Hacker attack on Merkur Bets
Liked this post:
Danny0815
Thank you for the answer. I know that there are good and bad hackers.
I just wasn't 100% sure whether GraphQL can be used by just about any computer scientist, or whether advanced training or the like is required. I assume it's part of the basic knowledge (just because it's supposed to be very good). However, as I have neither trained nor studied in this field, I could only guess.
I wondered about this for one simple reason: you want to give the impression that this vulnerability is extremely difficult and that hardly anyone could discover it. But your answer told me that it's not what they want to make it look like.
This post has been translated automatically
Hacker attack on Merkur Bets
Nobody has liked this post so far
I don't know if there is a connection. Does anyone know if this has been planned for some time?
A merger like this usually involves cost savings.
The "war chest" needs to be filled.
This post has been translated automatically
Hacker attack on Merkur Bets
Nobody has liked this post so far
It was probably planned for some time. Could be a coincidence, but in 2023 the sponsor for the GJ Advent calendar was still Crazybuzzer. In 2024 it was then Slotmagie.
This post has been translated automatically