Open Side Menu Go to the Top
Register
Superuser Caught on GGPoker - "MoneyTaker69" Thread Superuser Caught on GGPoker - "MoneyTaker69" Thread

12-30-2023 , 12:15 PM
Imagine what's going on in RnC games since they aren't tracked...
Players who ch/f every time you flop a set and call every river bluff, anyone?

Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 12:16 PM
there have been many speculating moneytaker was white hat and didnt care about money, just trying to expose gg's lax security. why do we think that?

the two arguments i'm aware of are
a) their sn is the name of a hacker group
b) they played so bad they must've wanted to get caught

to a): has that hacking group ever whitehatted anything or even done something "just to show" security exploits? briefly reading about them it sounds like they operated silently and undetected for a period of years before their sophisticated financial crimes were detected and attribtued to them

to b): robbie jade. also, the atrocious play is entirely consistent with someone who's not sophisticated at poker but is sophisticated at pushing known allin equities to grow bankroll fastest

the theory's also inconsistent with moneytaker cashing out some of their winnings so GG couldn't confiscate it all, no?
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 12:22 PM
Quote:
Sorry the book merchant is a moderator/admin and you are not allowed to ignore him or her.
That's unfortunate.

Quote:
Originally Posted by Gavron
Omaha games seem the same. 50/15-ish people that do very well, also same pattern of donking 1bb in a spot that makes absolutely no sense to do it even for rec's.
I've seen a guy that is putting insane volume on R&C 100 and 200 (he playes 8 tables rush simultaneously and almost always wins the LB) min3bet with kjt7 single suit(very reg-like behaviour) then a "fish" 4bets we get it all in with aces and he is good , because the "fish" also has aces. All in all very very suspicious and dodgy pool tendencies in games that look extremely soft. I saw EddieKing mention 22 cheating accounts, I am willing to bet he had only holdem in mind, there are just as much in the Omaha Pool.
It does make sense, minbetting gives you more points than checking. These "fishes" are rb pros abusing the rush leaderboards.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 12:25 PM
Quote:
Originally Posted by GGcare
So many security flaws in the GG design:
  1. Calculating all-in equity prior to all-in state;
  2. Communicating all-in equity to client prior to all-in state;
  3. Communicating all-in equity in unencrypted format;
  4. Failing to force security updates to client before allowing further play;
  5. Concealing a known vulnerability from users even after it was apparent that it was known and exploited;
  6. Failing to conduct regular audits of accounts with extreme variance
Nailed it.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 12:32 PM
Quote:
Originally Posted by GGcare
Tried to summarize it all, cause #GGcare
MoneyTaker69 exploited a vulnerability in the software, which made it possible for him to see the equity in real-time. He wouldn’t see the hole cards of the other players, but he’d always know his chance of winning the hand. Simply put, the server would know what cards the other players were holding, it’d calculate the equity based on this, regardless of whether there was an all-in situation, and MoneyTaker69 would tap into this info, always knowing whether he was ahead or behind. It’s possible the client-side hack by MoneyTaker69 would trigger additional equity calculations – that server side normally wouldn’t do it, unless there’s an all-in – but that’s equally bad, as it means GG never bothered putting an all-in condition in place for equity calculation.
MoneyTaker69 chose to make use of this exploit in such a moronic fashion that there’re only two possible explanations:
  1. He didn’t have the faintest idea about poker.
  2. He wanted to get caught and/or expose the GG security, or rather lack thereof.
While the case is great for shedding light on the dire state of GG security, it’s really about the bigger picture here. How was this made possible in the first place? How widespread is cheating on GG?
Firstly, GG’s use of Adobe AIR is a concern on its own. As they said in their statement: “since part of our desktop client leverages the Adobe Air framework, which has attack vectors that other frameworks do not”. Adobe AIR is part of the problem here, but it’s a symptom of a more severe issue: GG are prioritizing getting new features and games out, over the integrity and security of their games. There’s no good reason for using Adobe AIR, other than it enables them to release stuff faster than would have otherwise been possible, but it's at the cost of additional “attack vendors”/vulnerabilities. This is something they’re obviously aware of, and they’ve simply made the decision that game integrity can’t take priority.
It's not just about Adobe AIR though. There’re more concerns related to what seems to be a general trend of prioritizing time to market over everything else. As a another member wrote earlier:
So many security flaws in the GG design:
  1. Calculating all-in equity prior to all-in state;
  2. Communicating all-in equity to client prior to all-in state;
  3. Communicating all-in equity in unencrypted format;
  4. Failing to force security updates to client before allowing further play;
  5. Concealing a known vulnerability from users even after it was apparent that it was known and exploited;
  6. Failing to conduct regular audits of accounts with extreme variance
Lastly, the way GG has handled this case is anything but confidence inspiring:
  1. According to their statement, they became aware of the issue on the 16th of December but never announced it. Only after public outcry, 13 DAYS LATER, they issued a statement. GG were aware their game integrity could be compromised but did not deem it necessary to let the players know. Or, almost worse: they had no idea how the vulnerability could be exploited.
  2. Once they issued a statement, they made sure to only do it on their .com blog, making the content unavailable to the majority of players, due to a redirect being in place.
  3. MoneyTaker69 was allegedly reported already on the 25th, but the report was dismissed. Only after it became a thing on 2+2 and X did GG act.
  4. They’ve proudly announced they’ll double the size of their “technical security team”. Great, but that means they’ve either had way too small a team (despite claiming to take security extremely seriously) or they’ve already got a big team but realize there’ve been operating with a fundamentally flawed model for the past year and foresee bigger challenges in the future, i.e. state of security is terrible. Regardless of the size of their security team, they must change their way of working. A bigger team will help, sure, but if time to market continues to be priority number one, it won’t be a fix.

Is it likely that MoneyTaker69 just doesn’t have the faintest idea about poker, that he simply didn’t want to become rich and that there’s no one else that took advantage of the issue? Millions could have been made – and perhaps have been made? – with this exploit. It must be considered unlikely that an individual who had the technical know-how to hack the all-in equity was such a dumbass when it comes to taking financial advantage of it. There’s at least a real possibility of this being significantly bigger than the one account.
This is what matters. The issue is GG's whole approach to security and how they prioritize speed of release over security, not the isolated incident (which may not be so isolated).

Trying to investigate chipdumping cases/cases with unnaturally high winrates, that doesn't make all that much sense, in the context of this specific issue. If multiple players took advantage of the exploit, it's unlikely they'll have done it as blatantly as MoneyTaker69. If it's been used in a smart way, there'll be no way for you to identify the perpetrators. GG might not even be able to do so, based on their blog post, as they likely don't have any server side logs that'd make it easy to identify. And if they do, there's no way they'll ever disclose it, if there's more than this one case.

If you live in a country where GG holds a local license, it could be worth flagging this to the local regulator, but it's unlikely they'll understand the severity of the issue.
The local regulator could demand a formal investigation and data to be shared with them.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 12:39 PM
As a software developer, that the bug happened doesn't surprise me. Business types can't be bothered with the details and want speed and new features above all else. If there's a bug, they know they can just blame the technical people.

It often takes a heroic stand by a programmer to slow down and do things right, which only works if the programmer has been there for a while and has a lot of clout.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 12:41 PM
Don't worry. They are hiring a new security person, thus doubling there security team.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 12:44 PM
Quote:
Originally Posted by suzzer99
As a software developer, that the bug happened doesn't surprise me. Business types can't be bothered with the details and want speed and new features above all else. If there's a bug, they know they can just blame the technical people.

It often takes a heroic stand by a programmer to slow down and do things right, which only works if the programmer has been there for a while and has a lot of clout.
From what I understand, the client was able to request AIEV from the server at any time during the hand, and the server provided it. I'd say that's a pretty egregious defect as far as its effect, but it's really just a "minor" (i.e. non-architectural) programming error. It doesn't take long to add a check to that procedure call to verify that the client is also in a state where it is allowed to see all non-folded hole cards (i.e. all in or post hand), so I don't think this one can even be blamed on rushing features to market. It's just a bug that wasn't picked up in testing.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 12:48 PM
As long as the code which collects the rake is working fine I’m sure the higher ups dgaf. This is how the real world operates
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 12:52 PM
Quote:
Originally Posted by d2_e4
From what I understand, the client was able to request AIEV from the server at any time during the hand, and the server provided it. I'd say that's a pretty egregious defect as far as its effect, but it's really just a "minor" (i.e. non-architectural) programming error. It doesn't take long to add a check to that procedure call to verify that the client is also in a state where it is allowed to see all non-folded hole cards (i.e. all in or post hand), so I don't think this one can even be blamed on rushing features to market. It's just a bug that wasn't picked up in testing.
That's still a massive design failure. Two seconds of thought should have told you that could be exploited.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:00 PM
If cutting corners, sometimes one too much is cut. It's easier to find out in hindsight and ask: why was that particular corner cut, easily avoided.

You have to have that staff not cutting security corners. GG should maybe quadruple, if doubling means a very small number!

Last edited by plaaynde; 12-30-2023 at 01:10 PM.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:08 PM
Quote:
Originally Posted by d2_e4
From what I understand, the client was able to request AIEV from the server at any time during the hand, and the server provided it. I'd say that's a pretty egregious defect as far as its effect, but it's really just a "minor" (i.e. non-architectural) programming error. It doesn't take long to add a check to that procedure call to verify that the client is also in a state where it is allowed to see all non-folded hole cards (i.e. all in or post hand), so I don't think this one can even be blamed on rushing features to market. It's just a bug that wasn't picked up in testing.
Using Adobe AIR is more relevant here, in regards to rushing things and not having priorities in order. There're also past incidents and cases, but this most recent one is obviously in a league of its own.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:08 PM
Quote:
Originally Posted by jayme87
the thread is cluttered with so much noise that the real questions are getting overlooked .

those results look suspicious too, albeit its micros, another instance of 500nl was shown with some suspicious wr's. how many others have been using this exploit, i think we need to do the work for gg, who wants to ransack their security department? eddie get your coat i will get the balaclavas, or just hack the servers that way its probably so easy still?
Spoiler:

Spoiler:


Above are images of NL10 Leaderboards on GG poker at different timeframes this year. This is really not looking good guys.
so far we have evidence of suspicious accounts on NL10, NL25, NL50, NL500
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:10 PM
Quote:
Originally Posted by suzzer99
That's still a massive design failure. Two seconds of thought should have told you that could be exploited.
Programmers, especially cheap ones, are not always entirely well versed with the business domain in which they operate. Two seconds of thought would tell us, as poker players that, yes. It may not be entirely intuitive to someone who has never played a hand of poker and gets paid to churn out lines of code. "Just" forgot to double-check a condition for a state the code should never reach anyway, and wouldn't, without a hacked client.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:11 PM
Quote:
Originally Posted by GGcare
Using Adobe AIR is more relevant here, in regards to rushing things and not having priorities in order. There're also past incidents and cases, but this most recent one is obviously in a league of its own.
Fair point.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:28 PM
Players didn't care when their recent promotion was funded by reducing players rakeback.

Players didn't care when their "free" buffet and rooms at Atlantis were taken from the "guaranteed" prize pool at WSOP Paradise

Players didn't care when their Spins didn't award the right multipliers

Player don't care about PVI and just take it

Players don't care that their Curacao "licence" provides literally ZERO player protections

Players didn't care when they remained in Russia through a skin, when every other site withdrew from the market according to international sanctions

Players don't care that they operate in markets that require a license illegally by using agents and changing the countries that players are located in

Why would they possibly care now?

Last edited by JackSpratt; 12-30-2023 at 01:35 PM.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:30 PM
Quote:
Originally Posted by suzzer99
That's still a massive design failure. Two seconds of thought should have told you that could be exploited.
Two seconds of thought during a security review, which is clearly not part of their process. So it's not only a massive design failure, but a massive management failure--they don't have a way to catch massive design failures.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:36 PM
Quote:
Originally Posted by GGcare
Using Adobe AIR is more relevant here, in regards to rushing things and not having priorities in order. There're also past incidents and cases, but this most recent one is obviously in a league of its own.
If you design the server correctly who cares is they hack the client. The server's API from clients should consist of a limited set of operations. Sit at table, fold/bet/raise, leave table, chat. That's pretty much it. Any other operations are initiated server side and encrypt the data so you can't spoof a different client. To allow the client to request hole card information or equities is just terrible design.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:36 PM
Welcome to the world where everything is run and decided by MBAs who know absolute dick about anything except "make numbers go up".
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:42 PM
Quote:
Originally Posted by donkatruck
If you design the server correctly who cares is they hack the client. The server's API from clients should consist of a limited set of operations. Sit at table, fold/bet/raise, leave table, chat. That's pretty much it. Any other operations are initiated server side and encrypt the data so you can't spoof a different client. To allow the client to request hole card information or equities is just terrible design.
Also a very fair point. And as far as equities go, I see no reason to not just calculate them on the client anyway, once the server has sent hole card info. The equities should always be based on visible hole cards and the board, and those alone.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:51 PM
Quote:
Originally Posted by d2_e4
Programmers, especially cheap ones, are not always entirely well versed with the business domain in which they operate. Two seconds of thought would tell us, as poker players that, yes. It may not be entirely intuitive to someone who has never played a hand of poker and gets paid to churn out lines of code. "Just" forgot to double-check a condition for a state the code should never reach anyway, and wouldn't, without a hacked client.
When money is at stake, your programmers need to understand the domain inside and out.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:54 PM
Quote:
Originally Posted by suzzer99
When money is at stake, your programmers need to understand the domain inside and out.
True. But let's be honest, what are the chances that they don't offshore their development to some sweatshop in India?
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 01:59 PM
Their development is done in South Korea.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 02:04 PM
C'mon GG insiders, pls do not wait a year or two from now to tell us what's really going on behind the scenes like it was with pitbull poker back in 2009.

GG was set up to scam players, wasn't it?
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote
12-30-2023 , 02:24 PM
Quote:
Originally Posted by p0ker_n00b
id like a statistician to tell me how many hands need to be played in the next billion years in order for a 50vpip that loses at -50bb/100 to achieve a 90bb winrate over 15,000 hands assuming a stdev of 100

pretty please
I understand what you are getting at, but the exact probability isn’t relevant. The existing tools are sufficient to determine this was likely cheating. Poker dope shows a 100.00% chance of loss over even 5000 hands for a player with far higher than 100 st dev. Cheating occurs more often than 00.00% of the time (we dont even have to define “of the time”) so a player with fish stats winning at any significant amount let alone 90bb/100 over even a 5k hand sample is far more likely to be cheating. A security check should have been triggered after a few thousand hands.

The live guys saying this was a fish on a heater have a scale misunderstanding around how large a sample 15k hands is. If a fish cleaned out their table a full 100% of sessions for 3 months they would all be crying “cheater” too. Poker hands aren’t distinct random events. To get lucky fish need their pattern of play to match what the deck gives. Things like having air when their opponent also has bottom of range or putting in money bad on an early street to improve to the best hand. They don’t randomize in a way that allows them to perfectly dance around raindrops. A “tails never fails” guy running into an outlier string of coins landing on tails looks different than someone guessing perfectly every time. GG’s security team would be able to tell the difference when reviewing hands.
Superuser Caught on GGPoker - "MoneyTaker69" Thread Quote

      
m