CTIPilot

CL-CRI-1163

actor · actor:cl-cri-1163

Unit 42's designation for a cluster targeting the Brazilian financial sector via job-themed phishing, deploying an iteratively-versioned Go-based SOCKS5 tunneler (SockTz) with AI-generated exploit scripts (Unit 42, 2026-09-03).

Coverage timeline
1
first 2026-09-04 → last 2026-09-04
Peak priority
high
1 high
Sources cited
3
3 hosts
Sections touched
1
active-threats
Co-occurring entities
2
see Co-occurring entities below
ATT&CK techniques
7
pinned v19.2 · see below

ATT&CK techniques

7 techniques observed across 1 entry, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v19.2 · compare on the matrix · Navigator layer (JSON)

Initial Access TA0001

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-09-04/cl-cri-1131-1163-breeze-comet-latam-ai-augmented-intrusions · ATT&CK page ↗

T1566Phishing×1

Adversaries may send phishing messages to gain access to victim systems. All forms of phishing are electronically delivered social engineering. Phishing can be targeted, known as spearphishing. In spearphishing, a specific individual, company, or industry will be targeted by the adversary. More generally, adversaries can conduct non-targeted phishing, such as in mass malware spam campaigns.

Evidence: 2026-09-04/cl-cri-1131-1163-breeze-comet-latam-ai-augmented-intrusions · ATT&CK page ↗

Credential Access TA0006

T1003.002OS Credential Dumping: Security Account Manager×1

Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored. The SAM is a database file that contains local accounts for the host, typically those found with the <code>net user</code> command. Enumerating the SAM database requires SYSTEM level access.

Evidence: 2026-09-04/cl-cri-1131-1163-breeze-comet-latam-ai-augmented-intrusions · ATT&CK page ↗

T1003.003OS Credential Dumping: NTDS×1

Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights. By default, the NTDS file (NTDS.dit) is located in <code>%SystemRoot%\NTDS\Ntds.dit</code> of a domain controller.

Evidence: 2026-09-04/cl-cri-1131-1163-breeze-comet-latam-ai-augmented-intrusions · ATT&CK page ↗

Command and Control TA0011

T1071.004Application Layer Protocol: DNS×1

Adversaries may communicate using the Domain Name System (DNS) application layer protocol to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.

Evidence: 2026-09-04/cl-cri-1131-1163-breeze-comet-latam-ai-augmented-intrusions · ATT&CK page ↗

T1090Proxy×1

Adversaries may use a connection proxy to direct network traffic between systems or act as an intermediary for network communications to a command and control server to avoid direct connections to their infrastructure. Many tools exist that enable traffic redirection through proxies or port redirection, including HTRAN, ZXProxy, and ZXPortMap. Adversaries use these types of proxies to manage command and control communications, reduce the number of simultaneous outbound network connections, provide resiliency in the face of connection loss, or to ride over existing trusted communications paths between victims to avoid suspicion. Adversaries may chain together multiple proxies to further disguise the source of malicious traffic.

Evidence: 2026-09-04/cl-cri-1131-1163-breeze-comet-latam-ai-augmented-intrusions · ATT&CK page ↗

T1572Protocol Tunneling×1

Adversaries may tunnel network communications to and from a victim system within a separate protocol to avoid detection/network filtering and/or enable access to otherwise unreachable systems. Tunneling involves explicitly encapsulating a protocol within another. This behavior may conceal malicious traffic by blending in with existing traffic and/or provide an outer layer of encryption (similar to a VPN). Tunneling could also enable routing of network packets that would otherwise not reach their intended destination, such as SMB, RDP, or other traffic that would be filtered by network appliances or not routed over the Internet.

Evidence: 2026-09-04/cl-cri-1131-1163-breeze-comet-latam-ai-augmented-intrusions · ATT&CK page ↗

Story timeline

  1. 2026-09-04Unit 42 exposes two Latin American intrusion clusters after their own AI-agent staging infrastructure was left open, one hit Mexican federal ministries and water utilities, the other Brazilian finance
    active-threatsAn exposed self-hosted AI chat interface handed researchers the operators' playbook for a campaign against Mexican and Ecuadorian government infrastructure

Where this entity is cited

  • active-threats1

Source distribution

  • cloud.google.com1 (33%)
  • darkreading.com1 (33%)
  • unit42.paloaltonetworks.com1 (33%)

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Entries about CL-CRI-1163 (1)

2026-09-04 · view entry permalink →

HIGHNATOB2

Unit 42 exposes two Latin American intrusion clusters after their own AI-agent staging infrastructure was left open, one hit Mexican federal ministries and water utilities, the other Brazilian finance

Unit 42 published two distinct, ongoing intrusion clusters against Latin American targets on 2026-09-03, both showing operators using commercial LLMs to drive parts of the attack chain. CL-CRI-1131 hit a Mexican transportation organization plus federal government ministries and municipal water utilities in Mexico and Ecuador: operators relied on living-off-the-land batch scripts, and (after repeated failed attempts to dump the SAM registry hive and NTDS.dit) pivoted to shadow-copy-based collection instead (Unit 42, 2026-09-03). A self-hosted instance of NextChat, an open-source multi-model LLM chat interface, exposed on the operators' own infrastructure is what let Unit 42 reconstruct the operators' targeting logic: given the initial collection failures and the exposed AI interface on the same backend, Unit 42 assesses the operators relied on the LLM to generate the working-around scripts. Certificate-transparency pivoting on the associated infrastructure showed a single-domain certificate in February 2026 rotating to a five-subdomain certificate by April/June 2026, with subdomain names indicating Mexican federal-government targeting categories. Unit 42 ties this activity to the campaign CloudSEK separately tracks as "Operation Escaneo."

CL-CRI-1163 is a separate cluster reached via job-themed phishing against the Brazilian financial sector, deploying homebrewed malware rather than living-off-the-land tooling: within a two-hour window, attackers attempted installation of versions 1 through 8 of a Go-based reverse SOCKS5 tunneling tool named SockTz from a compromised WordPress site, then, after that install path failed, retrieved a ninth version from separate attacker-controlled infrastructure, with exploit-script filenames appended with descriptive adjectives (exploit_creative.py, exploit_careful.py, rce_focused.py) that Unit 42 reads as evidence of iterative, language-model-driven script generation rather than human authorship. Unit 42's central finding across both clusters is that the operators' own AI-staging infrastructure (an open NextChat directory, an open directory of numbered SockTz builds) is what let researchers reconstruct the operators' playbooks: attacker OpSec failures around their own AI tooling, not the AI use itself, are the exploitable defender advantage.

Separately, on 2026-09-01, Google Threat Intelligence Group/Mandiant documented BREEZE COMET (formerly UNC5669), a financially-motivated actor active against Brazilian financial services, retail and eCommerce since 2024, which GTIG states overlaps with activity publicly reported by others as "Plump Spider" and "SHADOW-AETHER-064" (Google Threat Intelligence Group / Mandiant, 2026-09-01). Trend Micro has reported that the group also exploits vulnerabilities in JBoss AS servers for initial access (Google Threat Intelligence Group / Mandiant, 2026-09-01, citing Trend Micro), alongside password spraying and voice-phishing calls impersonating IT support to talk targets into installing remote-monitoring tools. BREEZE COMET manipulates Brazil's Pix, STR and Boleto payment rails via a custom malware suite and stages through compromised small-government websites across Brazil, Nigeria, Paraguay, Ghana and Venezuela; one component, MILDFROST, is a passive Java backdoor that uses a class named DnsCommandBeacon to run a slow, covert DNS tunnel as a fallback command channel, dynamically querying delegated subdomains for instructions and fresh payloads (Google Threat Intelligence Group / Mandiant, 2026-09-01). GTIG independently confirms LLM-generated reconnaissance, credential-validation and deployment scripts in this cluster too, identified by a verbose AI-generated commenting style rather than any hardcoded signature. Within 24 to 48 hours of gaining access to core financial applications, GTIG reports the actor executed two waves of hundreds of fraudulent transactions.

we observed the attacker struggling to gather sensitive data. After repeated attempts to dump the Security Account Manager (SAM) registry hive and the domain controller NTDS.dit file, the attacker created shadow copies across multiple drives

Exposing an open NextChat directory to the public internet reveals a fundamental lack of operational maturity. The AI provided the necessary tactical workaround to extract the Active Directory database, but the human operators failed to secure the staging server.

attackers appended exploit filenames with descriptive adjectives. This suggests that the attackers employed iterative, language model-driven development: exploit_creative.py, exploit_careful.py and rce_focused.py.

Unit 42

Within 24-48 hours of establishing this access, the threat actor executed two waves of hundreds of fraudulent transactions, based on reporting by a client and third party forensic analysis.

Google Threat Intelligence Group / Mandiant 2026-09-01
threat04 Sep 05:50Zmulti-sourceOpen finding ↗