Case Library / Agentic AI Attacks (AI-Powered Social Engineering) / ScopeCreep: malware built with ChatGPT and hidden in a fake gaming tool (2025)

ScopeCreep: malware built with ChatGPT and hidden in a fake gaming tool (2025)

OpenAI says a Russian-speaking actor used throwaway ChatGPT accounts to build Windows malware, spread as a fake Crosshair-X gaming tool. How it worked.

Share:

Social Engineering Examples·5 sources

ScopeCreep is a case of malware built with ChatGPT and hidden inside a fake gaming tool. In June 2025, OpenAI said it had banned a cluster of ChatGPT accounts run by what it assessed was a Russian-speaking actor. The actor used throwaway accounts, one conversation each, to write and debug Windows malware in Go and the server that controlled it. The malware went out on a public code site, dressed up as "Crosshair-X", a popular crosshair overlay for PC gamers. OpenAI says it caught the operation early. Status: Disrupted by OpenAI; no victims named.

Key takeaways

  • The lure wasn't an email. It was a free gaming tool that looked like the real thing.
  • Each ChatGPT account was used once, for one small code change, then dropped. That was the actor's attempt to avoid notice.
  • OpenAI's own abuse detection caught it, not a victim or a security vendor.
  • OpenAI called the malware's abilities "not particularly novel". The AI sped up the work rather than inventing anything.

How ChatGPT was used

Think of it as a pair programmer that never asked why. The actor pasted in code, error messages and crash output, and asked for one feature or fix at a time. Each account was opened with a temporary email address, used for a single conversation, then abandoned. OpenAI noted the actor already "demonstrated knowledge of Windows internals". ChatGPT helped them move faster, including writing PowerShell to hide the malware from Windows Defender and moving their control server from a Flask test setup to a production Gunicorn deployment.

Tip: only download game tools, overlays and "cheats" from the official site or store. A copy on a random repository is a different program.

What the malware did

Stage Technique, per OpenAI
Lure A version of Crosshair-X uploaded to a public code repository
Load Running it started a loader that pulled down more malicious parts
Hide A trusted pythonw.exe loaded a malicious python310.dll. The code was packed with Themida
Escalate Relaunched itself with higher rights via ShellExecuteW
Evade PowerShell added it to Windows Defender's exclusion list, hid console windows and added delays
Talk HTTPS over port 80 with self-signed certificates, random user agents, and payloads padded with random bytes
Steal Browser credentials, tokens and cookies
Alert A Telegram bot told the operator every time a new victim was hit
Mask SOCKS5 proxies to hide the attacker's location

None of that needed a phishing email. The trust being exploited was general trust in code repositories and free gaming add-ons. OpenAI reported no fake website or lookalike domain.

How it ended

OpenAI spotted the cluster through its "scaled cyber abuse detection process", despite the account cycling. It banned every linked account and worked with the code-hosting site, which it didn't name, to remove the fake repository. Some samples had shown up on VirusTotal, so the malware was likely live. But OpenAI says it saw no sign of wide distribution. No financial figure was given, and that shouldn't be read as proof nobody lost anything.

OpenAI didn't name the actor. "Russian-speaking" is based on language in the conversations, not confirmed nationality or state backing.

What stops it

  • Get utilities from official, signed sources. Treat unsigned overlay or cheat tools as high-risk.
  • Flag DLL side-loading, like pythonw.exe loading a DLL it shouldn't.
  • Alert on PowerShell changing Defender exclusions.
  • Watch for Telegram Bot API traffic from ordinary PCs, and HTTPS on port 80 with bad certificates.

See also AI-generated malware, supply chain social engineering and LAMEHUG.

Common questions

What is ScopeCreep?

OpenAI's name for a Russian-speaking actor who used throwaway ChatGPT accounts to build Windows malware, spread as a fake version of the Crosshair-X gaming tool.

Did ChatGPT write the malware?

It helped. The actor used it to write, debug and refine code step by step. OpenAI said the resulting capabilities weren't particularly novel.

How was it stopped?

OpenAI's abuse detection flagged the accounts. It banned them and had the fake repository taken down.

Who was targeted?

PC gamers who downloaded the fake Crosshair-X tool. No specific victims were named.

Sources
Cite this case

Social Engineering Examples. “ScopeCreep: malware built with ChatGPT and hidden in a fake gaming tool (2025)”. Accessed 3 November 2026. https://socialengineeringexamples.com/openai-scopecreep-crosshair-x-trojan-2025

Attack Chain & Defense
1Target-Tool Reconnaissance
What happened

The threat actor identified a popular, trusted gaming utility, the "Crosshair-X" crosshair/aim-overlay tool, to impersonate, consistent with a supply-chain-style approach that trades a targeted pretext for broad, trust-based reach into the existing user base of a real tool.

The control that would have stopped it

Which existing, trusted tool an attacker chooses to impersonate is effectively unpredictable and outside any single defender's control; the realistic countermeasures sit downstream at distribution and execution (Stages 6 and 7), where unsigned-binary and code-provenance controls can actually intercept the trojanized package.

2AI-Account Operational Security Setup
What happened

Per OpenAI, the actor signed up for ChatGPT using temporary/disposable email addresses, limiting each account to a single conversation covering one incremental code change before abandoning it and creating a new one, apparently to limit any single account's visibility into the overall project and evade abuse detection.

The control that would have stopped it

This is the one stage where the defender (OpenAI) had direct visibility: its own scaled cyber-abuse detection process identified the cluster's activity despite the one-conversation-per-disposable-account tradecraft, leading to a ban of every account tied to it.

3AI-Assisted Malware Development
What happened

The actor used ChatGPT as an iterative pair-programmer, pasting Go code, stack traces, and crash output for the model to debug, and building out the Windows implant's capabilities (privilege escalation, persistence, credential theft) one requested feature at a time.

The control that would have stopped it

The same AI-vendor abuse-detection telemetry is the operative control here too, since no outside organization can see another vendor's chat logs; once the resulting binary reaches a network, standard EDR/behavioral detection on the implant itself becomes the backstop.

4AI-Assisted C2 Infrastructure Build-Out
What happened

ChatGPT was used to help build and later migrate the command-and-control backend from a Flask development server to a production Gunicorn/WSGI deployment, troubleshoot TLS certificate handling (cert.pem/key.pem) for HTTPS-over-port-80 delivery, and design a base64-encoded, randomly-padded payload-delivery scheme via a /auth POST endpoint intended to defeat signature-based detection.

The control that would have stopped it

Network-side monitoring for HTTPS traffic on non-standard port 80 with self-signed or invalid TLS certificates, and for outbound connections to unfamiliar C2-style /auth endpoints, can flag this infrastructure pattern even without knowing the payload's exact contents.

5AI-Assisted Evasion Engineering
What happened

The actor used ChatGPT to write PowerShell logic (invoked from Go) that programmatically added Windows Defender AV exclusions, suppressed console windows, and inserted timing delays, and to compile python310.dll so its code executed whenever python.exe ran; Themida commercial packing was another technique intended to defeat static and dynamic analysis.

The control that would have stopped it

EDR/AV tuning to flag DLL side-loading through legitimate interpreters (e.g., pythonw.exe loading unexpected DLLs), scripted or PowerShell-driven changes to Windows Defender's exclusion list, and the presence of commercial packers like Themida on unsigned binaries directly targets this stage's techniques.

6Trojanized-Tool Distribution
What happened

The finished malware was uploaded to a public code-hosting repository disguised as the legitimate "Crosshair-X" tool, relying on gamers discovering and downloading it organically rather than any direct outreach or phishing message.

The control that would have stopped it

Sourcing gaming utilities and overlays only from official, signed distribution channels, and treating unsigned "cheat"/overlay tools hosted on public code repositories as high-risk regardless of how legitimate their branding looks, removes the trust the impersonation depends on.

7Victim Execution and Initial Access
What happened

A user who downloaded and ran the fake "Crosshair-X" package triggered a loader that reached out to attacker infrastructure and pulled down the additional malicious components.

The control that would have stopped it

Application allow-listing and code-signing enforcement that blocks unsigned executables from running, paired with user-facing awareness that free gaming utilities from public repos are a common malware vector, would stop the loader before it can call out to attacker infrastructure.

8Privilege Escalation, Persistence, and On-Host Evasion
What happened

The malware relaunched itself via ShellExecuteW to escalate privileges, added itself to the Windows Defender exclusion list, and routed traffic through SOCKS5 proxies to mask the attacker's source IP and mimic the victim's apparent location.

The control that would have stopped it

EDR monitoring for anomalous ShellExecuteW-based relaunches, unexpected Windows Defender exclusion changes, and SOCKS5-proxied outbound connections from consumer endpoints can catch the malware after execution but before objective completion.

9Data Theft, Attacker Notification, and Objective Completion
What happened

The malware harvested browser-stored credentials, session tokens, and cookies and exfiltrated them over the covert HTTPS/port-80 channel, while a Telegram bot integration alerted the operator whenever a new victim was compromised, completing the attacker's goal of ongoing remote access and credential harvesting.

The control that would have stopped it

Browser/OS credential-store hardening and monitoring for bulk credential or cookie access, plus flagging outbound Telegram Bot API traffic from consumer endpoints as an indicator of compromise, per OpenAI's own stated defenses, can catch exfiltration and attacker notification even after the host is compromised.

Quick Facts
Victim
No named corporate, government, or individual victim was disclosed.
The apparent targets were gamers/PC users who downloaded a public-repository tool impersonating the legitimate "Crosshair-X" crosshair/overlay utility; OpenAI treats this as a supply-chain-style malware distribution campaign rather than a targeted attack on a specific organization.
Location
Threat actor: OpenAI describes only a "Russian-speaking" cluster of ChatGPT accounts; nationality, citizenship, and precise geography are not established, only language/behavioral indicators.
Victims: unspecified, presumed global population of PC gamers who could access the public repository hosting the trojanized tool.
Date
Disclosed by OpenAI on 2025-06-05 (blog) / report PDF dated 2025-06 (metadata 2025-06-01), as part of the quarterly "Disrupting malicious uses of AI" report.
The underlying ScopeCreep malware-development and C2 activity predates the disclosure; OpenAI does not give exact intrusion or campaign-start dates, only that it appeared to be caught in an early stage.
Impact
The ScopeCreep impact discussion from OpenAI's June 2025 report gives no financial figure
BasisunquantifiedNo financial figure appears in the ScopeCreep impact discussion
; this record does not infer that no losses occurred.
Status
Corroborated research/advisory
Case Type
Research / Advisory
Sector
Consumer / General Public, Technology & Software
Threat Actor
unknown
Explore more

Related Cases

Browse by what this case has in common with others in the library.