News & Notices: Why GambleJoe was unavailable for half a day on 10.04.2025

This post has been translated automatically

roccoammo11 wrote on 10.04.2025 at 23:42: Thanks for the info. Seems to be a real trend such attacks. You should think about a WhatsApp channel for such extreme cases

This post has been translated automatically

frapi07 wrote on April 10, 2025 at 11:48 pm:
DDOS attacks have been around for years - it's not a trend ^^. I played a massively multiplayer online role-playing game (MMORPG) and there was something like that. It was around 2015.

Can come from anyone. A hater, a competitor. But would rather guess a competitor.

This post has been translated automatically

• On the website haveibeenpwned.com , simply enter your e-mail address in the window provided and click on " pwned?". If you receive a reply with a red background saying "Oh no - pwned!", your e-mail account has unfortunately been hacked.


• The Hasso Plattner Institute's website https://sec.hpi.de/ilc/ also offers you the opportunity to check your e-mail address. This site will send you an e-mail to the address you have provided, informing you of any hack and the approximate time of the data theft.

This post has been translated automatically

btssultan wrote on 11.04.2025 00:41:

Yes and even punishable

Matthias wrote on 11.04.2025 at 00:56: In addition to the first post, I would like to add the following:
We have now made sure that the website and the forum are up and running again, but we still need to fine-tune a few things.
For example, we have deactivated the video upload for the time being and the mail server will not be reactivated until tomorrow.

Note on the security of your accounts on GambleJoe:

In fact, the "hacker" who launched the attack contacted us via email and claimed to have found a vulnerability in our system. He then sent us a list of various account details and wanted to extort a five-figure "ransom" in cryptocurrency from us.

Our initial technical analysis shows:
Important: The data that the person sent to us did not originate directly from our system.

Some of the usernames are outdated, some of the members have not existed for years, some of the usernames were changed by the users a long time ago. The list also contained usernames that do not even exist on GambleJoe. Of course, there are also correct usernames in the list, but this is clear as they are publicly visible everywhere on our website.

The inconsistency of the submitted list confirms to us that the "hacker" was bluffing and could not read any current data from our system.

Passwords, e-mail addresses and also e.g. the communicator messages are never stored in plain text on our , but strongly encrypted - this also speaks against a real "hack".

For the nerds among you: Every password is hashed in encrypted form before it is saved - this means that it is converted into a form that cannot be easily recalculated. We also use additional security features for each account so that even identical passwords are not recognizable as such. The process is protected by an internal project key that is not stored in the database.
This means that it would not be possible to read passwords directly - even in the event of an attack on the database - without additional, in-depth access to our system.

What we have noticed, however, is that all e-mail addresses that we have received have been published by various providers in recent years as part of data breaches and the corresponding data records are now circulating on the Internet.
Anyone can and should enter their e-mail address here and see which Provider has lost control of their personal data: https://haveibeenpwned.com/. You can also check here whether your password has already been leaked somewhere: https://www.gdata.de/passwort-check

As a precautionary measure, we recommend that you
- Never use the same password on different websites.
- Choose a strong and unique password for your GambleJoe account only.

And once again, we would like to emphasize that there is currently no concrete indication or even evidence of direct data theft on our platform. However, we are continuing to investigate the incident thoroughly and remain vigilant.

With this in mind, we go to bed with a clear conscience. Good night, everyone!

This post has been translated automatically

frapi07 wrote on 04/11/2025 01:10:

Okay sounds kind of like the typical scam attempts ala "I have +18 pictures of you, if you don't want them to get circulated, then pay 1000€ in BTC" or something like that.

1. It's a competitor who wants to weaken the other company.


2. The attack serves as a distraction to take over the system unnoticed (all eyes are on the obvious attack).


3. It is an attempt at blackmail - the aim is to stop the attacks only in return for payment. The variant with "Hey, I've taken over your system by the way" seems almost creative.

This post has been translated automatically

This post has been translated automatically

1. Affected services:
   
   
   
   • deezer.com (September 2019) and luminpdf.com (April 2019) are the platforms where your data appears in data leaks.
   
   
   • Both are classified as verified leaks, which means that the information comes reliably from the databases of these services.
   
   
   
   


2. Affected information:
   
   
   
   • In both cases, the address of your data is affected. This indicates that your address from the services' databases is included in the leak. Fortunately, no passwords, credit cards or bank details are affected.
   
   
   • Other sensitive information such as social security numbers are also not affected.
   
   
   
   


3. Number of users:
   
   
   
   • The Deezer leak had a huge number of over 228 million affected users.
   
   
   • The LuminPDF leak had almost 15 million affected users.
   
   
   
   

• Change your password for the affected services (if you use the same email address and password), even if the report says passwords are not affected.


• Be wary of phishing attempts, as your address could potentially be used for targeted attacks.


• Consider taking other steps, such as setting up two-factor authentication.

This post has been translated automatically

This post has been translated automatically

This post has been translated automatically

This post has been translated automatically

This post has been translated automatically

This post has been translated automatically