Roblox game creators are losing entire digital assets to a malware campaign that exploits social engineering on Discord and steals authenticated session tokens, bypassing 2FA. The phenomenon, documented on June 17, 2026 by Help Net Security and Malwarebytes based on 404 Media reporting, marks a qualitative leap in so-called "beaming": from theft of virtual items to outright confiscation of productive games with direct revenue streams.
- Attackers contact developers on Discord with fake job offers, often impersonating legitimate studios like Cheesy Studios.
- The malware is distributed as a Python package named 'robase', presented as a database development tool.
- It steals session tokens, not credentials: this bypasses 2FA by reusing already-authenticated sessions.
- Roblox support took over 30 days to resolve cases, with actual recovery only after media intervention.
How the Attack Mechanism Works
Entry occurs through Discord. Attackers pose as "project managers" with enticing collaboration offers, sometimes impersonating studios with established credibility like Cheesy Studios — the Matziaris brothers' company. The payload is a Python package called 'robase', presented as a database utility.
Once executed, the malware operates as a specialized infostealer. It does not target passwords: it steals session tokens from already-authenticated browsers. As Malwarebytes explains, citing 404 Media, "this is a case of session-token theft, rather than credential theft". The distinction is crucial: with a valid session token, attackers reuse an already-verified session, rendering measures like 2FA ineffective.
With access acquired, attackers modify security settings, change passkeys, force logout from all devices, and transfer ownership of games and groups. The creator is dispossessed of the asset in short order, with direct economic impact.
Documented Victims: From 10,000 Robux Daily to Zero
Jovan Rai, 15, managed a game peaking at 1,100 concurrent users and earning roughly 10,000 Robux daily — equivalent to about $38. The game was stolen; he spent over 30 days contacting Roblox support without result. The breakthrough came only after a 404 Media reporter intervened.
Equally significant is the case of the Matziaris brothers, who had "The Shadow Network" stolen — a game they had worked on for five years. The family's son executed the malware after being contacted with a job offer in April 2026. Attackers then impersonated Cheesy Studios themselves to lend credibility to further offers, expanding their contact network.
"Account theft usually ends with someone losing a password. This one ends with hackers walking off with the entire game."
Roblox's Response and Its Limits
Roblox responded to comment requests citing features like "Enhanced Protection" and "Account Session Protection". The company statement, reported by Help Net Security, however includes a significant clause: "no security measure can completely eliminate the risk of account theft when users are persuaded to run malicious software or execute untrusted code".
The case documents a recurring pattern: game restoration occurred only after media contact, not through ordinary support channels. This raises questions about the platform's ability to independently protect creators, particularly younger ones or those with less visibility.
What to Do Now
For Roblox developers active on Discord, verifying the identity of contacts proposing collaborations is the first filter. Requesting confirmation through official studio or personal channels — not just via the Discord profile that initiated the conversation — reduces the risk of interacting with impersonated accounts.
The nature of the 'robase' package as a Python tool requires specific caution: any unverified package from untrusted repositories or unsolicited from known sources deserves cross-checking. Developers should isolate installation of third-party tools in environments separate from the main development system, when possible.
The session-token theft mechanism makes 2FA insufficient as a sole barrier. Monitoring active Roblox account sessions and disconnecting unrecognized ones is a concrete action, though forced logout by attackers may render this check reactive rather than preventive.
For creators with valuable assets, documenting game ownership through external records — screenshots of control panels, development histories, support communications — provides useful material in case of dispute with Roblox support. Documented cases show media visibility accelerated recovery: having structured documentation ready reduces reaction time if ordinary channels fail.
Why This Matters
The shift from virtual item theft to seizure of entire productive games represents an escalation striking the economic heart of UGC platforms. For indie developers, many of them minors, the risk is no longer loss of a cosmetic accessory but loss of a revenue-generating asset.
The dossier does not specify the total number of developers affected by this specific campaign, nor does it document malware variants beyond the 'robase' package. It also does not clarify whether the package is distributed on public repositories or exclusively via direct sharing. The source does not clarify whether stolen sessions are monetized through game sales or only through Robux extraction.
The absence of structured primary advisories — no CVE identified for this campaign, no official vendor communication with technical details — leaves this campaign in a gray zone of documentation. Available sources are security editorials and journalistic reporting, not independently verifiable technical advisories. For the industry, the central question remains platform responsibility in protecting user-created assets and support timeliness.
Information is based on cited sources and current as of publication.
Sources
Information is based on cited sources and current as of publication.
Sources
- https://securelist.com/dozens-of-malicious-wallpapers-found-on-steam-workshop/120186/
- https://unit42.paloaltonetworks.com/flutterbridge-new-fluttershell-backdoor/
- https://nvd.nist.gov/vuln
- https://nvd.nist.gov/vuln/search
- https://nvd.nist.gov/vuln/categories
- https://nvd.nist.gov/vuln/data-feeds
- https://nvd.nist.gov/vuln/vendor-comments
- https://nvd.nist.gov/vuln/cvmap