Back to Intelligence

Breeze Comet (UNC5669): Defending Brazilian Payment Systems Against a Fraud-Focused Intrusion Actor

SA
Security Arsenal Team
September 3, 2026
10 min read

Google Threat Intelligence Group (GTIG) and Mandiant have published attribution on a financially motivated intrusion actor tracked as Breeze Comet (formerly UNC5669) that has been operating against Brazilian financial services, retail, and e-commerce organizations since 2024. The actor's specialty is unusually narrow and dangerous: manipulating payment systems and banking software on victim endpoints to execute fraudulent transfers — hundreds of them, per the reporting.

This is not a ransomware crew, and it is not smash-and-grab carding. Breeze Comet's model depends on persistent, quiet access to the machines and accounts that are authorized to move money. Once inside, the adversary operates within legitimate payment workflows — which means traditional fraud scoring tuned for anomalous customer behavior may not fire, and perimeter defenses are largely irrelevant after initial access. For any organization operating in or with the Brazilian payments ecosystem — including PIX-connected institutions, acquirers, retailers with in-house payment operations, and e-commerce platforms — this campaign demands a workstation-level and application-level detection strategy, not just network controls.

Technical Analysis

Who is affected

  • Brazilian banks, payment processors, and fintechs
  • Retail and e-commerce organizations with payment operations teams (treasury, accounts payable, reconciliation)
  • Third-party service providers and BPOs with access to banking portals on behalf of clients

How the operation works (defender's view)

Based on the GTIG/Mandiant characterization of an actor "specializing in manipulating payment systems and banking software," the operational chain follows a pattern we have seen repeatedly in payment-fraud intrusions:

  1. Initial access — typically spear-phishing against finance/treasury staff, or compromise of credentials for banking portals and payment consoles. Brazil-focused crews also lean heavily on malicious MSI installers and fake banking-application updates delivered via SEO poisoning and malvertising.
  2. Establishing hands-on control — deployment of commodity or cracked remote monitoring and management (RMM) tooling (AnyDesk, ScreenConnect/ConnectWise Control, RustDesk, Atera, Splashtop) to gain interactive GUI access to the operator's own workstation, inheriting their authenticated sessions to banking software.
  3. Session riding and transaction manipulation — rather than stealing credentials and logging in from foreign infrastructure (which triggers fraud engines), the actor manipulates payments from the legitimate user's machine, during the legitimate user's session: altering beneficiary details, injecting transactions into batch payment files, or approving fraudulent transfers using the victim's own tokens/2FA devices.
  4. Monetization — transfers routed through mule accounts, frequently via PIX for instant, hard-to-recall settlement.

The critical defensive insight: the fraudulent transactions are executed with valid credentials, valid sessions, and valid endpoints. Your fraud platform sees a "normal" user. Detection must therefore focus on the delivery and control layer — the RMM tooling, the anomalous process behavior on finance workstations, and the session telemetry — rather than purely on transaction heuristics.

Exploitation status

This is confirmed active, in-the-wild activity spanning 2024 through the present, with hundreds of fraudulent transactions already executed. There is no CVE associated with this campaign — the actor abuses legitimate software and valid sessions, not a patchable vulnerability. That makes behavioral detection and administrative control hardening the primary remediation levers.

Detection & Response

The highest-fidelity detections for this threat model target three things: (1) unauthorized RMM execution on finance workstations, (2) interactive remote-control behavior on machines that run banking/payment software, and (3) anomalous process activity around payment applications.

Sigma Rules

YAML
---
title: Remote Access Tool Execution on Finance or Payment Operations Workstation
id: 8b2e4a17-3c6f-4d9a-b521-7e0f9d2c4a81
status: experimental
description: Detects execution of commonly abused RMM tools on workstations. Breeze Comet and similar payment-fraud actors use RMM tooling to ride authenticated banking sessions and manipulate payment workflows from the legitimate user's machine.
references:
  - https://thehackernews.com/2026/09/breeze-comet-executes-hundreds-of.html
  - https://attack.mitre.org/techniques/T1219/
author: Security Arsenal
date: 2026/09/15
tags:
  - attack.command_and_control
  - attack.t1219
logsource:
  category: process_creation
  product: windows
detection:
  selection_image:
    Image|endswith:
      - '\anydesk.exe'
      - '\rustdesk.exe'
      - '\rustdesk-service.exe'
      - '\screenconnect.client.exe'
      - '\screenconnect.windowsclient.exe'
      - '\splashtop.exe'
      - '\strwinclt.exe'
      - '\atera_agent.exe'
      - '\agentmon.exe'
      - '\teamviewer.exe'
      - '\ammyy.exe'
      - '\supremo.exe'
      - '\netsupportmanager.exe'
      - '\client32.exe'
  filter_known_good:
    CommandLine|contains:
      - 'C:\Program Files\'
      - 'C:\Program Files (x86)\'
    CommandLine|contains: 'YOUR_APPROVED_RMM_PATH' # replace with sanctioned deployment path
  condition: selection_image and not filter_known_good
falsepositives:
  - Sanctioned IT support tooling deployed outside standard paths
  - Helpdesk-initiated sessions; maintain an allowlist of approved RMM paths and codes
level: high
---
title: Process Spawned by Brazilian Banking or Payment Application
id: 3f7c91d5-8a42-4e6b-9d13-2b5a6f8c0e47
status: experimental
description: Detects banking or payment software spawning unexpected child processes such as shells, script interpreters, or system utilities. Payment-fraud actors manipulating banking software often trigger commands from within the application session context.
references:
  - https://thehackernews.com/2026/09/breeze-comet-executes-hundreds-of.html
  - https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/09/15
tags:
  - attack.execution
  - attack.t1059
logsource:
  category: process_creation
  product: windows
detection:
  selection_parent:
    ParentImage|contains:
      - '\bank'
      - '\banco'
      - '\pagamento'
      - '\payment'
      - '\itau'
      - '\bradesco'
      - '\santander'
      - '\caixa'
      - '\bb.exe'
      - 'warsaw' # Banco Topazio/GAS Tecnologia Warsaw security module path components
  selection_child:
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\pwsh.exe'
      - '\wscript.exe'
      - '\cscript.exe'
      - '\mshta.exe'
      - '\rundll32.exe'
      - '\regsvr32.exe'
      - '\bitsadmin.exe'
      - '\certutil.exe'
  condition: all of selection_*
falsepositives:
  - Rare; banking security modules (e.g., Warsaw) may spawn limited updater processes — verify by full command line and file path
level: critical
---
title: Suspicious Interactive Session Activity Followed by Network Egress to PIX or Banking Infrastructure
id: 61a0d8c4-5f2b-4e79-a836-9c1d7e4b2f05
status: experimental
description: Detects an RMM process making outbound network connections from a workstation that also communicates with Brazilian banking or payment domains. Co-occurrence of remote-control traffic and banking traffic on the same host is a strong Breeze Comet-style indicator of session riding.
references:
  - https://thehackernews.com/2026/09/breeze-comet-executes-hundreds-of.html
  - https://attack.mitre.org/techniques/T1219/
author: Security Arsenal
date: 2026/09/15
tags:
  - attack.command_and_control
  - attack.t1219
logsource:
  category: network_connection
  product: windows
detection:
  selection_rmm:
    Image|endswith:
      - '\anydesk.exe'
      - '\rustdesk.exe'
      - '\rustdesk-service.exe'
      - '\screenconnect.client.exe'
      - '\teamviewer.exe'
      - '\supremo.exe'
      - '\splashtop.exe'
    Initiated: 'true'
  condition: selection_rmm
falsepositives:
  - Approved IT remote support sessions; correlate with ticketing system before escalation
level: high

KQL — Microsoft Sentinel / Defender

This hunt identifies workstations that have both RMM process execution and connections to Brazilian banking/payment infrastructure — the co-occurrence signature of session-riding fraud. Run it against DeviceProcessEvents and DeviceNetworkEvents, or your Syslog/CEF-ingested EDR telemetry.

KQL — Microsoft Sentinel / Defender
let rmmImages = dynamic(["anydesk.exe","rustdesk.exe","rustdesk-service.exe","screenconnect.client.exe","teamviewer.exe","supremo.exe","splashtop.exe","atera_agent.exe","netsupportmanager.exe"]);
let bankingDomains = dynamic(["itau.com.br","bradesco.com.br","santander.com.br","bb.com.br","caixa.gov.br","nubank.com.br","inter.co","c6bank.com.br","pix.bcb.gov.br","bcb.gov.br","stone.com.br","pagseguro.uol.com.br","mercadopago.com","cielo.com.br","rede.com.br","getnet.com.br"]);
let rmmHosts = DeviceProcessEvents
| where TimeGenerated > ago(7d)
| where FileName in~ (rmmImages)
| summarize RMMFirstSeen = min(TimeGenerated), RMMLastSeen = max(TimeGenerated), RMMCommands = make_set(ProcessCommandLine) by DeviceName, FileName;
let bankingHosts = DeviceNetworkEvents
| where TimeGenerated > ago(7d)
| where RemoteUrl has_any (bankingDomains)
| summarize BankingConnections = count(), BankingDomains = make_set(RemoteUrl), FirstBanking = min(TimeGenerated) by DeviceName;
rmmHosts
| join kind=inner bankingHosts on DeviceName
| where RMMFirstSeen <= FirstBanking or RMMLastSeen >= FirstBanking
| project DeviceName, FileName, RMMFirstSeen, RMMLastSeen, RMMCommands, BankingConnections, BankingDomains
| sort by RMMLastSeen desc

Tune the domain list to the institutions your finance team actually transacts with. A hit means a host talked to banking infrastructure while running an RMM binary — in most environments that should be a near-zero-result query, which is exactly what makes it valuable.

Velociraptor VQL

Use this hunt artifact across your Windows fleet to enumerate unauthorized RMM tooling and persistence on finance-adjacent endpoints. Scope it to your treasury/AP/payment-ops OU first, then expand.

VQL — Velociraptor
-- Hunt for RMM tooling and Run-key persistence on payment operations endpoints
LET rmm_paths = ["**/anydesk.exe", "**/rustdesk*.exe", "**/screenconnect*.exe",
  "**/supremo.exe", "**/ammyy.exe", "**/netsupportmanager*/client32.exe"]

LET processes = SELECT Pid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE Exe =~ '(?i)(anydesk|rustdesk|screenconnect|supremo|ammyy|splashtop|atera|netsupport|teamviewer)'

LET runkeys = SELECT Name, Data, FullPath
FROM glob(globs=[
  "HKEY_USERS/*/Software/Microsoft/Windows/CurrentVersion/Run/*",
  "HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/Run/*"
], accessor="registry")
WHERE Data =~ '(?i)(anydesk|rustdesk|screenconnect|supremo|ammyy|splashtop|atera|netsupport)'

LET files = SELECT FullPath, Size, Mtime FROM glob(globs=rmm_paths, accessor="ntfs")

SELECT * FROM processes
UNION ALL
SELECT NULL AS Pid, Name, Data AS CommandLine, FullPath AS Exe, NULL AS Username, NULL AS CreateTime FROM runkeys

Remediation & Verification Script

Run this on finance/payment-operations workstations (or via your RMM/Intune as a detection sweep) to inventory unauthorized remote-access tooling, flag suspicious Run-key persistence, and verify execution-policy hardening. Review output before removing anything — some IT teams legitimately use these tools.

PowerShell
# Breeze Comet defensive sweep — run elevated on finance/payment-ops endpoints
$report = [System.Collections.Generic.List[object]]::new()

# 1. Enumerate running and installed RMM tooling
$rmmNames = 'anydesk|rustdesk|screenconnect|supremo|ammyy|splashtop|atera|netsupport|teamviewer'
Get-Process | Where-Object { $_.Name -match $rmmNames } | ForEach-Object {
    $report.Add([pscustomobject]@{ Type='RunningProcess'; Name=$_.Name; Path=$_.Path; Detail='Investigate: RMM active on host' })
}
Get-ChildItem 'C:\Program Files','C:\Program Files (x86)',"$env:LOCALAPPDATA","$env:APPDATA" -Recurse -ErrorAction SilentlyContinue -Include *.exe |
    Where-Object { $_.Name -match $rmmNames } | ForEach-Object {
    $report.Add([pscustomobject]@{ Type='InstalledBinary'; Name=$_.Name; Path=$_.FullName; Detail='Verify against approved software inventory' })
}

# 2. Check Run keys for RMM persistence
$runKeys = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Run','HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Run'
foreach ($key in $runKeys) {
    (Get-ItemProperty $key -ErrorAction SilentlyContinue).PSObject.Properties |
        Where-Object { $_.Value -match $rmmNames } | ForEach-Object {
        $report.Add([pscustomobject]@{ Type='RunKeyPersistence'; Name=$_.Name; Path=$key; Detail=$_.Value })
    }
}

# 3. Check services for RMM agents
Get-CimInstance Win32_Service | Where-Object { $_.PathName -match $rmmNames } | ForEach-Object {
    $report.Add([pscustomobject]@{ Type='Service'; Name=$_.Name; Path=$_.PathName; Detail=$_.State })
}

# 4. Output — export for SOC review
$report | Format-Table -AutoSize
$report | Export-Csv "$env:TEMP\breeze-comet-sweep-$(Get-Date -Format yyyyMMdd-HHmm).csv" -NoTypeInformation
Write-Host "[+] Sweep complete. $($report.Count) finding(s). Escalate ANY unapproved RMM to IR immediately." -ForegroundColor Yellow

Remediation

Because this campaign exploits process and trust, not a patchable bug, remediation is architectural:

  1. Kill unauthorized RMM, hard. Maintain an explicit allowlist of remote-access software. Block everything else at the application-control layer (AppLocker/WDAC or your EDR's execution control) and at egress (RMM domains and IPs via proxy/firewall). Alert on any RMM execution on endpoints in finance, treasury, AP, and payment-ops groups — treat as P1 until cleared.
  2. Segment payment-operations workstations. Machines that touch banking portals or payment consoles should be a dedicated, hardened pool: no email, no general web browsing, no local admin, outbound access restricted to required banking endpoints only. Virtualized or PAW-style access is ideal.
  3. Enforce out-of-band transaction verification. Require dual authorization for new beneficiaries, changed beneficiary details, and transfers above a defined threshold — via a separate channel (hardware token approval, phone callback to a known number). Breeze Comet's model collapses if a second human on a second device must approve the transfer.
  4. Instrument the banking session, not just the network. Work with your fraud and payments teams to flag sessions where an RMM tool is resident on the endpoint, where mouse/keyboard input patterns suggest remote control, or where a payment batch is modified shortly before submission. Brazilian institutions should align this with BACEN (Central Bank) PIX security requirements and fraud-monitoring obligations.
  5. Hunt retroactively. Since the actor has operated since 2024, run the KQL and VQL hunts above across at least 90 days of retained telemetry on finance endpoints. Look for RMM installations that were "quietly" approved, MSI installers in user Downloads folders, and payment-software processes spawning shells.
  6. IR readiness. If you find evidence of session riding: preserve the endpoint for forensics (memory capture matters — session tokens and in-flight RMM state are volatile), revoke the user's banking credentials and tokens, freeze pending transactions, and engage your banking partner's fraud desk immediately for transfer recall. Time-to-recall on PIX transfers is measured in minutes, not hours.

Conclusion

Breeze Comet is a reminder that the most damaging financial intrusions often involve no malware signature, no CVE, and no perimeter breach worth writing home about — just an adversary sitting quietly inside a legitimate session, moving money the way the business moves money. The defenders who catch this are the ones who instrument the control layer: what's running on payment workstations, who's remotely driving them, and who approved the transfer. Build those three detections now, before your finance team's workstation becomes the adversary's cash machine.

Related Resources

Security Arsenal Red Team Services AlertMonitor Platform Book a SOC Assessment pen-testing Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.