AI Tool Use in Latin American Cyberattacks Exposed

AI-Powered Cyberattacks Target Financial and Government Sectors in Latin America

HIGH
September 3, 2026
8m read
Threat ActorMalwareThreat Intelligence

Related Entities

Threat Actors

CL-CRI-1131CL-CRI-1163

Organizations

Products & Tech

ClaudeGPT-4.1NextChatSOCKS5

Other

Let's Encryptduckdns.org

Full Report

Executive Summary

This report details two ongoing, multi-stage cyber campaigns targeting organizations in Latin America, primarily in Mexico and Brazil. Researchers at Unit 42 have identified two activity clusters, CL-CRI-1131 and CL-CRI-1163, which demonstrate a significant evolution in the regional threat landscape: the integration of Artificial Intelligence (AI) and Large Language Models (LLMs) into their operational toolchain. The attackers use commercial LLMs like Claude and GPT-4.1 to generate scripts, troubleshoot technical obstacles, and orchestrate data exfiltration. The campaigns share overlapping SOCKS5 proxy infrastructure and target sensitive sectors, including government, transportation, and finance. Poor operational security by the attackers, including exposed infrastructure, has provided critical insights into their methods and increasing reliance on AI to streamline attacks.

Threat Overview

Two distinct but related threat clusters are actively targeting entities in Latin America. CL-CRI-1131 focuses on Mexican federal government and transportation organizations, while CL-CRI-1163 targets the Brazilian financial sector. Despite their different geographic targets and methods—CL-CRI-1131 uses living-off-the-land techniques while CL-CRI-1163 deploys custom malware—both campaigns share critical TTPs that signal a broader trend.

The core of this trend is the operational use of AI. The attackers leverage an open-source tool called NextChat, hosted on their own infrastructure, to interact with multiple LLMs. This allows them to generate and refine malicious scripts in real-time. During an observed intrusion by CL-CRI-1131 in April 2026, the attacker demonstrated a trial-and-error approach consistent with LLM usage, struggling to dump credentials from the SAM hive and NTDS.dit file before successfully using shadow copies.

Initial access for the CL-CRI-1163 campaign is believed to be through job-themed phishing attacks. Both groups make extensive use of a shared SOCKS5 proxy network for anonymity and dynamic DNS services like duckdns.org for resilient command-and-control (C2) infrastructure.

Technical Analysis

The technical execution of these campaigns reveals a blend of common and advanced techniques, augmented by AI.

CL-CRI-1131: Living-off-the-Land with AI Assistance

This cluster relies heavily on built-in Windows tools, with LLMs providing the logic. Key observed actions include:

  1. Credential Access (T1003): The attacker made repeated, unsuccessful attempts to directly access and copy the Security Account Manager (SAM) registry hive and the Active Directory database (NTDS.dit).
  2. Script Generation (T1059.003): After initial failures, the attacker used a series of numbered batch scripts, likely generated by an LLM, to automate data collection. The scripts included permission checks, indicating iterative refinement.
  3. Defense Evasion (T1565.002): The attacker successfully used Volume Shadow Copies (VSS) to create a snapshot of the system, allowing them to copy the locked SAM and NTDS.dit files without interruption.
  4. C2 Infrastructure: The attackers used the IP 62.171.185[.]97 for data exfiltration, linked to the dynamic DNS domain m-doxa-apodo.duckdns[.]org. Analysis of TLS certificates revealed a multi-SAN certificate exposing other subdomains, indicating intended targets within the Mexican government.

CL-CRI-1163: Custom Malware and Phishing

This cluster, targeting Brazil's financial sector, uses a more sophisticated approach but with the same AI-driven backend.

  1. Initial Access (T1566): Initial access was likely gained via a job-themed phishing campaign.
  2. Custom Implants: Unlike CL-CRI-1131, this group uses custom-built malware. However, exposed staging infrastructure revealed operational scripts with filenames suggesting they were dynamically generated by an LLM.

Shared Infrastructure and AI Tooling

Both clusters leverage a shared SOCKS5 proxy network and an instance of NextChat hosted on 178.128.87[.]160:3000. NextChat provides a web interface for the attackers to query various LLMs, compare their outputs, and generate code, all while keeping the prompts on attacker-controlled infrastructure. This setup indicates a deliberate strategy to integrate AI into the attack lifecycle for increased efficiency and adaptability.

Impact Assessment

The targeting of government, transportation, and financial sectors poses a significant risk to national security and economic stability in the affected Latin American countries. Successful exfiltration of NTDS.dit files could lead to a full domain compromise, giving attackers access to all user accounts, passwords, and sensitive data within the organization's network. For the Brazilian financial institutions, a breach could result in financial theft, customer data loss, and erosion of trust in the banking system. The use of AI suggests that these threat actors can adapt and overcome defensive measures more quickly than traditional attackers, potentially reducing the time from initial compromise to significant impact.


IOCs — Directly from Articles

The following indicators of compromise were explicitly mentioned in the source report.

Type
IP Address
Value
62.171.185[.]97
Description
C2 infrastructure used for data exfiltration in CL-CRI-1131 activity.
Type
Domain
Value
m-doxa-apodo.duckdns[.]org
Description
Dynamic DNS domain associated with C2 IP 62.171.185[.]97.
Type
IP Address
Value
178.128.87[.]160
Description
Hosted an instance of the NextChat open-source tool on TCP port 3000.

Cyber Observables — Hunting Hints

Security teams may want to hunt for the following patterns, which could indicate related activity:

Type
Network Traffic
Value
Outbound connections to *.duckdns.org
Description & Context
Monitor DNS logs and proxy logs for connections to this dynamic DNS provider, which is uncommon for legitimate corporate traffic.
Type
Process Creation
Value
vssadmin.exe create shadow
Description & Context
Monitor command-line logs (Event ID 4688) for the creation of volume shadow copies, especially when initiated by non-standard accounts or scripts.
Type
Network Traffic
Value
Outbound connections on TCP port 3000
Description & Context
Monitor firewall and NetFlow data for traffic to non-standard ports like 3000, which was used to host the NextChat interface.
Type
File Creation
Value
*.bat or *.ps1 in temp directories
Description & Context
Hunt for newly created, numerically sequenced script files (e.g., 1.bat, 2.bat) in user profiles or temporary folders, which may indicate LLM-generated code.

Detection & Response

Detecting these AI-assisted attacks requires a focus on behavioral anomalies and infrastructure patterns.

  1. Monitor Command-Line and Scripting: Implement enhanced logging for PowerShell (T1059.001) and Windows Command Shell (T1059.003). Use EDR solutions to alert on suspicious command chains, especially the use of vssadmin.exe followed by file copy operations from the shadow copy path (\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy*).
  2. Network Traffic Analysis: Per D3FEND technique Network Traffic Analysis (D3-NTA), filter and alert on outbound traffic to dynamic DNS providers like duckdns.org. Profile normal network behavior and flag connections to unusual ports or IP ranges associated with proxies.
  3. Behavioral Analytics: Employ User and Entity Behavior Analytics (UEBA) to detect anomalous account activity, such as a user account suddenly running numerous reconnaissance scripts or attempting to access sensitive files like NTDS.dit.
  4. Endpoint Detection and Response (EDR): An EDR tool is critical for identifying the living-off-the-land techniques used. EDR can correlate the sequence of events, from script execution to shadow copy creation and network connections, to identify the attack chain.

Mitigation

Defenders can take several steps to mitigate the risk from these and similar threats.

  • Restrict Dynamic DNS: Implement D3FEND's DNS Denylisting (D3-DNSDL). If your organization does not have a business need for dynamic DNS services, create firewall or proxy rules to block outbound connections to known dynamic DNS providers.
  • Application Control: Use application control solutions like AppLocker to restrict the execution of unauthorized scripts. This aligns with MITRE ATT&CK Mitigation M1038 - Execution Prevention.
  • Protect Credentials: Harden systems to prevent credential dumping. Ensure that access to domain controllers is heavily restricted. Implement Privileged Access Management (PAM) solutions (M1026) to control and monitor access to administrative accounts.
  • User Training: Since one cluster used phishing for initial access, ongoing user security training (M1017) is essential to reduce the likelihood of compromise.
  • Endpoint Hardening: Reduce the attack surface by hardening endpoints. This includes disabling unnecessary services and applying the principle of least privilege, aligning with D3FEND's Platform Hardening (D3-PH).

Timeline of Events

1
February 1, 2026
Initial infrastructure for the CL-CRI-1131 campaign was established, including a single-SAN certificate for m-doxa-apodo.duckdns.org.
2
April 1, 2026
An intrusion by CL-CRI-1131 was observed, showing trial-and-error attempts to exfiltrate data. Attackers rotated infrastructure and generated new multi-SAN certificates.
3
June 1, 2026
Campaign infrastructure persisted, and attackers generated another new multi-SAN certificate.
4
September 3, 2026
This article was published

MITRE ATT&CK Mitigations

Enable detailed logging of process creation, command-line arguments, and script execution to detect anomalous use of built-in tools like vssadmin.exe.

Mapped D3FEND Techniques:

Strictly control and monitor access to administrative accounts and domain controllers to prevent credential dumping of SAM and NTDS.dit files.

Mapped D3FEND Techniques:

Block or alert on outbound connections to known dynamic DNS providers and other untrusted domains to disrupt C2 communications.

Mapped D3FEND Techniques:

Conduct regular security awareness training to help users identify and report phishing attempts, which served as an initial access vector.

Use application allowlisting to prevent the execution of unauthorized scripts and executables, limiting the attacker's ability to run their generated code.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

To counter the techniques observed in the CL-CRI-1131 and CL-CRI-1163 campaigns, security teams should implement robust process analysis with a focus on command-line argument monitoring. Specifically, configure EDR and SIEM solutions to generate high-priority alerts for the execution of vssadmin.exe with create shadow arguments, especially when initiated by user accounts or scripts rather than automated system backup processes. Correlate this activity with subsequent file access to the shadow copy path (\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy*) and any follow-on network connections. Establish a baseline of normal script execution (e.g., PowerShell, batch files) in your environment and alert on deviations, such as the rapid creation and execution of numerically sequenced script files in temporary directories, which is a key indicator of the LLM-assisted TTPs described in this threat.

Given the attackers' reliance on duckdns.org for command and control, implementing DNS denylisting is a highly effective countermeasure. At the network perimeter firewall or secure web gateway, create a policy to block all DNS requests and subsequent connections to *.duckdns.org and other known free dynamic DNS providers. For organizations that cannot outright block these services due to a niche business need, switch to a 'log and alert' policy. Ingest DNS query logs into a SIEM and create rules that trigger alerts for any internal host resolving a domain from a high-risk dynamic DNS provider. This directly disrupts the C2 channel for the CL-CRI-1131 campaign and forces attackers to acquire more traditional, and often easier to track, domain infrastructure.

To address the phishing vector used by CL-CRI-1163 and the post-compromise behavior of both clusters, deploy a User Behavior Analysis (UBA) solution. Configure the system to monitor for sequences of anomalous events tied to a single user identity. For example, a user clicking a link in an email, followed by the download of an executable, and then the execution of command-line scripts, should be flagged as a high-risk incident. For credential dumping detection, the UBA platform should alert when a non-administrative account or an administrator account outside of normal working hours attempts to access or copy sensitive system files like the SAM hive or NTDS.dit. This technique moves beyond single indicators to identify the logical progression of an attack, making it effective against adaptable, AI-driven adversaries.

Timeline of Events

1
February 1, 2026

Initial infrastructure for the CL-CRI-1131 campaign was established, including a single-SAN certificate for m-doxa-apodo.duckdns.org.

2
April 1, 2026

An intrusion by CL-CRI-1131 was observed, showing trial-and-error attempts to exfiltrate data. Attackers rotated infrastructure and generated new multi-SAN certificates.

3
June 1, 2026

Campaign infrastructure persisted, and attackers generated another new multi-SAN certificate.

Sources & References

Attackers Expose Ongoing AI Tool Use Targeting Organizations in Latin America
Unit 42 (unit42.paloaltonetworks.com) •September 2, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

AI in cyberattacksLLMLatin AmericaSOCKS5Dynamic DNSData ExfiltrationThreat Actor

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

⚡ Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.