Executive Summary
In September 2026, threat actors launched a sophisticated ClickFix campaign exploiting OpenAI's Custom GPT feature to deliver remote access Trojans (RATs). Attackers created malicious Custom GPTs mimicking legitimate ChatGPT releases, leveraging trusted domains from OpenAI and Google to deceive victims. The attack chain began when users interacted with fake Custom GPTs named "Plus 5.6" through the official ChatGPT domain, then redirected to a Google Sites page with fake CAPTCHA prompts. Victims were tricked into executing PowerShell commands that downloaded MSI files, which used legitimate Canon-signed applications to sideload malicious DLLs and deploy RATs capable of data theft, surveillance, and network infiltration. Huntress security researchers documented at least 40 confirmed incidents from this campaign. This attack represents an evolution in social engineering tactics, exploiting trust in AI platforms and legitimate cloud infrastructure to bypass traditional security awareness training focused on domain verification.
Why This Matters Now
This incident highlights the emerging threat of AI platform abuse as Custom GPTs and similar AI tools proliferate in enterprise environments. The exploitation of trusted AI domains undermines traditional security awareness training and demonstrates how attackers are adapting to leverage users' growing dependence on AI assistants.
Attack Path Analysis
Attackers leveraged malicious Custom GPTs on legitimate ChatGPT infrastructure to redirect victims to Google Sites hosting fake Cloudflare pages with ClickFix prompts. Victims executed PowerShell commands downloading MSI files that sideloaded Canon-signed applications with malicious DLLs. The DLLs extracted encrypted loaders from WAV files to deploy RATs capable of remote desktop sessions, camera/microphone access, file searching, user account creation, and serving as a network foothold for additional payloads and data theft.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
Malicious Custom GPTs named 'Plus 5.6' hosted on legitimate chatgpt.com domain redirect users to Google Sites with fake Cloudflare CAPTCHA pages containing ClickFix prompts that trick victims into executing PowerShell commands
MITRE ATT&CK® Techniques
Phishing: Spearphishing Link
User Execution: Malicious Link
Command and Scripting Interpreter: PowerShell
Hijack Execution Flow: DLL Side-Loading
Process Injection: Portable Executable Injection
Ingress Tool Transfer
Input Capture: Keylogging
Screen Capture
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
CISA Zero Trust Maturity Model 2.0 – Identity Verification and Authentication
Control ID: IA-2
PCI DSS 4.0 – Security Awareness Program
Control ID: 12.6.1
NYDFS 23 NYCRR 500 – Training and Monitoring
Control ID: 500.14(a)
Digital Operational Resilience Act (DORA) – ICT Risk Management Framework
Control ID: Article 13
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21(2)(a)
ISO 27001:2022 – Information Security in Project Management
Control ID: A.6.8
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
Custom GPTs exploit trusted ChatGPT domains for RAT delivery, compromising software development environments through ClickFix social engineering targeting technical personnel.
Information Technology/IT
RAT infections enable lateral movement and command-control activities across IT infrastructure, bypassing traditional security controls through legitimate domain abuse.
Financial Services
Remote access trojans pose severe data exfiltration risks to financial institutions, violating PCI compliance requirements and enabling unauthorized system access.
Health Care / Life Sciences
Healthcare organizations face HIPAA violations and patient data theft through RAT-based surveillance capabilities and encrypted traffic exfiltration methods.
Sources
- Malicious Custom GPTs Turn ChatGPT Into RAT Delivery Lurehttps://www.darkreading.com/cyberattacks-data-breaches/malicious-custom-gpts-chatgpt-rat-delivery-lureVerified
- Huntress Labs Threat Intelligence Report on Custom GPT Abusehttps://www.huntress.com/blog/custom-gpt-clickfix-campaignVerified
- CISA Alert on ClickFix Social Engineering Campaignshttps://www.cisa.gov/news-events/cybersecurity-advisories/aa24-270aVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF would likely reduce the blast radius of this Custom GPT-initiated attack by constraining lateral movement between network segments and limiting the scope of RAT communications through segmented access controls.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Cloud-native visibility and policy enforcement would likely limit the initial foothold establishment by constraining which network resources the compromised endpoint could access immediately after PowerShell execution.
Control: Zero Trust Segmentation
Mitigation: Zero Trust segmentation would likely constrain the privileged process's network reachability, limiting which systems and services the sideloaded DLL could communicate with despite achieving code execution on the compromised host.
Control: East-West Traffic Security
Mitigation: East-west traffic controls would likely limit the RAT's ability to discover and access adjacent systems, constraining network reconnaissance and reducing the attacker's capability to establish footholds on additional organizational endpoints.
Control: Multicloud Visibility & Control
Mitigation: Multicloud visibility controls would likely limit the RAT's command channel establishment by constraining which external destinations the compromised workload could reach for persistent communication and payload retrieval activities.
Control: Egress Security & Policy Enforcement
Mitigation: Egress security policies would likely constrain the RAT's data transmission capabilities by limiting outbound network paths and restricting which external destinations could receive stolen file contents and captured surveillance data.
The overall impact scope would likely be reduced to the initially compromised network segment, with constrained ability to affect critical business systems or establish widespread organizational presence for sustained espionage operations.
Impact at a Glance
Affected Business Functions
- Information Technology Operations
- Data Security and Privacy Controls
- Employee Productivity Systems
- Network Security Infrastructure
Estimated downtime: 3 days
Estimated loss: $75,000
Browser credentials, session tokens, endpoint configuration data, and potential network reconnaissance information. The RAT enables remote desktop access, camera and microphone surveillance, file system access, and creation of unauthorized user accounts for persistent access.
Recommended Actions
Key Takeaways & Next Steps
- • Deploy Cloud Native Security Fabric (CNSF) with real-time inspection to detect and block malicious Custom GPT interactions and shadow AI usage through behavioral analysis and prompt injection detection
- • Implement Egress Security & Policy Enforcement with FQDN filtering to prevent unauthorized outbound connections to malicious Google Sites domains and block PowerShell-initiated downloads of suspicious MSI files
- • Enable Threat Detection & Anomaly Response capabilities to identify covert tools like remote access applications and detect baseline deviations from normal user behavior patterns during ClickFix exploitation attempts
- • Configure Zero Trust Segmentation with identity-based policies and least privilege access to limit RAT lateral movement capabilities and prevent creation of unauthorized user accounts across network segments
- • Establish Multicloud Visibility & Control with centralized policy enforcement to detect anomalous automation patterns, repeated malformed requests to legitimate domains, and suspicious cross-domain redirections from trusted infrastructure



