Trojan found targeting Digitain iGaming infrastructure and crash games, JFrog says

JFrog researchers say they found malware built to attack Digitain’s iGaming platform and interfere with the backend of one of its crash games. For PSPs and operators, the useful part is not the drama around the trojan itself, but the reminder that game-integrity incidents can come from inside knowledge of the stack, not just from generic fraud tooling.

1. According to JFrog, the malicious package was distributed as if it were a popular .NET development library, which made it look normal to most users. Once it landed inside Digitain’s infrastructure, it activated and вмешался in the server-side logic of one crash game.
2. JFrog says the code could alter the results of individual crash-game rounds and let attackers predict outcomes in advance. In practice, that would let fraudsters use the information to gain an advantage while playing, and the trojan also sent data back to the attackers to confirm the scheme was still working.
3. The researchers said the attack required deep knowledge of Digitain’s internal software architecture, which is why they suspect a current or former employee, or a contractor with access to internal information, may have been behind it. That is the part operators and vendors should care about: this is not just commodity malware sprayed around at random.
4. JFrog notified Digitain on 7 July. Two days later, Digitain told the researchers that the issue had already been passed to the relevant team and fixed. The attackers have not been identified.

Digitain is a platform supplier used by iGaming brands, so any compromise in its backend logic has a direct downstream effect on operators that rely on it. For high-risk businesses, the takeaway is straightforward: access controls, vendor separation, and monitoring for supply-chain tampering are not optional extras when your game economy depends on third-party infrastructure.