Attackers Expose Ongoing AI Tool Use Targeting Organizations in Latin America
Unit 42 analyzed two ongoing intrusion campaigns in Latin America (CL-CRI-1131 and CL-CRI-1163) where attackers leveraged commercial LLMs via self-hosted NextChat instances to generate scripts and troubleshoot execution failures. CL-CRI-1131 targeted Mexican transportation and government entities using living-off-the-land techniques, while CL-CRI-1163 targeted the Brazilian financial sector with custom RATs and a Go-based SOCKS5 proxy tool called SockTz. Both campaigns exhibited operational security failures, including exposed staging directories and multi-SAN certificates that revealed their infrastructure and intended targets.
Detection / Hunteropenrouter
What Happened
Attackers targeting organizations in Latin America are using artificial intelligence tools to help them break into systems and steal data. In two separate campaigns, one targeting Mexican transportation and government groups and another targeting Brazilian financial institutions, attackers used AI to write scripts and fix problems they encountered during the intrusions. The attackers made operational security mistakes, such as leaving their tool directories and AI interfaces exposed on the internet, which allowed security researchers to track their activities and intended targets. Organizations in the region should review their security posture, be on the lookout for phishing emails, and hunt for the specific tools and infrastructure used by these attackers.
Key Takeaways
- Attackers are using commercial LLMs like Claude and GPT-4.1 via self-hosted NextChat instances to generate scripts and troubleshoot operational failures during intrusions.
- Two distinct campaigns, CL-CRI-1131 and CL-CRI-1163, targeted Latin American organizations using living-off-the-land techniques and custom RATs respectively.
- Attackers deployed a Go-based reverse SOCKS5 tunneling tool named SockTz with iterative versioning (v1-v9) indicating AI-assisted development.
- Operational security failures by the attackers, such as exposed open directories and unsecured NextChat interfaces, allowed researchers to map their infrastructure and targets.
- Infrastructure overlaps include shared SOCKS5 relay infrastructure and multi-SAN TLS certificates revealing intended targets like Mexican federal government ministries.
Affected Systems
- Windows endpoints
- Domain controllers
- Web servers (JBoss)
- WordPress sites
Vulnerabilities (CVEs)
None identified.
Attack Chain
- Initial Access: CL-CRI-1163 used resume-themed phishing emails; CL-CRI-1131 initial access vector not explicitly detailed but involved host-based operations.
- Execution & AI Integration: Attackers used self-hosted NextChat instances with commercial LLMs (Claude, GPT-4.1) to generate scripts and troubleshoot execution failures.
- Credential Access: In CL-CRI-1131, attackers created volume shadow copies to dump the SAM registry hive and NTDS.dit file after repeated failed attempts.
- Persistence & Defense Evasion: CL-CRI-1163 deployed multiple versions (v1-v9) of a Go-based reverse SOCKS5 tunneling tool named SockTz to establish proxy connections.
- Exfiltration: CL-CRI-1131 exfiltrated data to 62.171.185.97 using the domain m-doxa-apodo.duckdns.org; CL-CRI-1163 staged scripts and tools on an open directory at 167.148.195.53.
Detection Availability
- YARA Rules: No
- Sigma Rules: No
- Snort/Suricata Rules: No
- KQL Queries: No
- Splunk SPL Queries: No
- EQL Queries: No
- Other Detection Logic: No
No specific detection rules (YARA, Sigma, Snort/Suricata, KQL, SPL, EQL) are provided in the article. Palo Alto Networks products (Advanced WildFire, Cortex XDR, XSIAM, Advanced URL Filtering, Advanced DNS Security) are mentioned as providing protections.
Detection Engineering Assessment
| Dimension | Rating | Rationale |
|---|---|---|
| EDR Visibility | Medium | EDR can detect the execution of batch scripts, vssadmin usage for shadow copy creation, and the execution of SockTz binaries. However, the use of living-off-the-land techniques may blend in with legitimate administrative activity. |
| Network Visibility | High | The article provides specific IP addresses, domains, and a URL for staging and exfiltration. Network monitoring can detect connections to these known-bad infrastructures and the use of dynamic DNS domains. |
| Detection Difficulty | Moderate | Detection is moderate because while specific IOCs are provided, the use of LotL techniques and AI-generated scripts may require behavioral analysis to distinguish from legitimate activity. The iterative naming conventions and descriptive adjectives in filenames are strong indicators if observed. |
Required Log Sources
- EDR process execution logs
- DNS logs
- Web proxy logs
- TLS certificate logs (for SAN matching)
- Firewall logs
Hunting Hypotheses
| Hypothesis | Telemetry | ATT&CK Stage | FP Risk |
|---|---|---|---|
| Hunt for volume shadow copy creation followed by file copying from the shadow copy path, which may indicate credential database extraction attempts. | EDR process execution logs, file access logs | Credential Access | Medium - System administrators may legitimately create shadow copies for backups, but copying NTDS.dit or SAM hives from them is highly suspicious. |
| Hunt for outbound connections to dynamic DNS domains with the 'm-doxa-' prefix or to the specific IPs 178.128.87.160, 62.171.185.97, and 167.148.195.53. | DNS logs, firewall logs, web proxy logs | Command and Control | Low - These are specific IOCs associated with malicious activity. |
| Hunt for the execution of binaries with iterative version naming conventions (e.g., socktz_v1.exe through socktz_v9.exe) or descriptive adjectives in filenames (e.g., exploit_creative.py). | EDR process execution logs, file creation logs | Execution | Low - Legitimate software rarely uses this naming pattern for execution. |
| Hunt for the presence of or connections to a NextChat instance on TCP port 3000 on attacker-controlled infrastructure. | Network connection logs, web proxy logs | Command and Control | Medium - NextChat is a legitimate open-source tool, but its presence on non-corporate infrastructure or accessed from a server is suspicious. |
Control Gaps
- Standard signature-based AV may miss custom RATs and AI-generated scripts with unique filenames.
- DNS filtering may not block dynamic DNS domains if they are newly registered or not yet categorized as malicious.
Key Behavioral Indicators
- Execution of vssadmin.exe followed by copy commands accessing shadow copy paths
- Process execution of files with iterative version naming (e.g., socktz_v1.exe to socktz_v9.exe)
- Network connections to *.duckdns.org domains with 'm-doxa-' prefix
- Execution of Python scripts with descriptive adjectives in filenames (e.g., exploit_careful.py)
- Outbound connections to TCP port 3000 on known malicious IPs
False Positive Assessment
Low
Recommendations
Immediate Mitigation
- Verify against your organization's incident response runbook and team escalation paths before acting. Block the identified IP addresses (178.128.87.160, 62.171.185.97, 167.148.195.53, 165.22.184.26) and domains (m-doxa-*.duckdns.org) at the firewall and web proxy.
- Hunt for the provided SHA-256 hashes (a38b2cf8beff32a276eed8783723ecf8cc53d7dc88669e1b998dddc4db6fe996, 87bf8bc8b4a2cf34f0af1afe161f123a3d200e77f6c6f41b81bf6ae66ee172ec) across endpoint telemetry.
- If your EDR supports it, consider isolating hosts that have communicated with the identified infrastructure or executed the SockTz binaries.
Infrastructure Hardening
- Evaluate restricting outbound traffic to dynamic DNS domains (*.duckdns.org) where not required for business operations.
- Consider implementing TLS inspection to detect multi-SAN certificates that may reveal attacker infrastructure targeting patterns.
- Review and restrict access to TCP port 3000 and other non-standard ports to prevent communication with unapproved NextChat instances.
User Protection
- Consider deploying email filtering rules to block resume-themed phishing attachments, particularly in Latin American regions or financial sector organizations.
- Ensure endpoint protection is updated with the latest signatures and behavioral detection capabilities for custom RATs and tunneling tools.
Security Awareness
- Consider incorporating warnings about resume-themed phishing emails into existing security awareness programs, especially for financial sector employees.
- Reinforce the importance of reporting suspicious emails and unexpected system behavior, as attackers are using AI to make their lures and scripts more convincing.
MITRE ATT&CK Mapping
Initial Access
Stealth
Credential Access
Command and Control
Impact
Additional IOCs
- Ips:
165[.]22[.]184[.]26- Host associated with a single-SAN Let's Encrypt certificate used in February 2026 for the CL-CRI-1131 campaign.
- Domains:
m-doxa-geo[.]duckdns[.]org- Subdomain indicating geolocation operational function, revealed via multi-SAN certificate in CL-CRI-1131.m-doxa-intel[.]duckdns[.]org- Subdomain indicating intelligence operational function, revealed via multi-SAN certificate in CL-CRI-1131.m-doxa-repuve[.]duckdns[.]org- Subdomain indicating targeting of REPUVE (Mexican vehicle registry), revealed via multi-SAN certificate in CL-CRI-1131.m-doxa-sre[.]duckdns[.]org- Subdomain indicating targeting of SRE (Mexican Secretary of Foreign Affairs), revealed via multi-SAN certificate in CL-CRI-1131.m-doxa-vacunas[.]duckdns[.]org- Subdomain indicating targeting of vaccines (likely health ministry), revealed via multi-SAN certificate in CL-CRI-1131.
- File Hashes:
46ac289ce0c13666de616446f5d5a68da8bd150f4f065c3bec02f63776d3899c(SHA256) - Let's Encrypt TLS certificate SHA-256 hash from June 19, 2026, associated with host 178.128.87.160 in CL-CRI-1131.4e218e70afdbb116209ec0ebe8fc556e296e69648aa4e0425b83c0e863a8fee5(SHA256) - Let's Encrypt TLS certificate SHA-256 hash from April 20, 2026, associated with host 178.128.87.160 in CL-CRI-1131.7d766942ef34542cee39c852286599958c4c2e23187010c4d38dbf88fcb40bf8(SHA256) - Let's Encrypt TLS certificate SHA-256 hash from Feb. 27, 2026, associated with host 165.22.184.26 in CL-CRI-1131.
- File Paths:
socktz_v8.exe- Filename of version 8 of the SockTz SOCKS5 proxy tool attempted to be executed in the CL-CRI-1163 campaign.socktz_v9- Filename of version 9 of the SockTz SOCKS5 proxy tool retrieved from attacker-controlled infrastructure in the CL-CRI-1163 campaign.
- Command Lines:
- Purpose: Volume shadow copy creation for extracting sensitive files like NTDS.dit | Tools:
vssadmin,cmd.exe| Stage: Credential Access |vssadmin create shadow /for=<volume> - Purpose: Copying files from shadow copy to a collection directory | Tools:
cmd.exe,copy| Stage: Exfiltration |cmd.exe /c copy <source> <dest>
- Purpose: Volume shadow copy creation for extracting sensitive files like NTDS.dit | Tools:
- Other:
exploit_creative.py- Filename of an exploit script with a descriptive adjective, suggesting LLM-driven iterative development in CL-CRI-1163.exploit_careful.py- Filename of an exploit script with a descriptive adjective, suggesting LLM-driven iterative development in CL-CRI-1163.rce_focused.py- Filename of an exploit script with a descriptive adjective, suggesting LLM-driven iterative development in CL-CRI-1163.
- domainm-doxa-apodo[.]duckdns[.]orgPrimary dynamic DNS domain used for data exfiltration in the CL-CRI-1131 campaign, tied to a Let's Encrypt TLS certificate.
- domainm-doxa-geo[.]duckdns[.]orgSubdomain indicating geolocation operational function, revealed via multi-SAN certificate in CL-CRI-1131.
- domainm-doxa-intel[.]duckdns[.]orgSubdomain indicating intelligence operational function, revealed via multi-SAN certificate in CL-CRI-1131.
- domainm-doxa-repuve[.]duckdns[.]orgSubdomain indicating targeting of REPUVE (Mexican vehicle registry), revealed via multi-SAN certificate in CL-CRI-1131.
- domainm-doxa-sre[.]duckdns[.]orgSubdomain indicating targeting of SRE (Mexican Secretary of Foreign Affairs), revealed via multi-SAN certificate in CL-CRI-1131.
- domainm-doxa-vacunas[.]duckdns[.]orgSubdomain indicating targeting of vaccines (likely health ministry), revealed via multi-SAN certificate in CL-CRI-1131.
- filenamesocktz_v8.exeFilename of version 8 of the SockTz SOCKS5 proxy tool attempted to be executed in the CL-CRI-1163 campaign.
- ip165[.]22[.]184[.]26Host associated with a single-SAN Let's Encrypt certificate used in February 2026 for the CL-CRI-1131 campaign.
- ip167[.]148[.]195[.]53Hosted an open directory containing hundreds of campaign scripts and multiple versions of the SockTz SOCKS5 proxy tool in the CL-CRI-1163 campaign.
- ip178[.]128[.]87[.]160Hosted an exposed NextChat instance on TCP port 3000 used by attackers for LLM-assisted script generation and troubleshooting in the CL-CRI-1131 campaign.
- ip62[.]171[.]185[.]97Used for data exfiltration and connectivity troubleshooting in the CL-CRI-1131 campaign.
- sha25646ac289ce0c13666de616446f5d5a68da8bd150f4f065c3bec02f63776d3899cLet's Encrypt TLS certificate SHA-256 hash from June 19, 2026, associated with host 178.128.87.160 in CL-CRI-1131.
- sha2564e218e70afdbb116209ec0ebe8fc556e296e69648aa4e0425b83c0e863a8fee5Let's Encrypt TLS certificate SHA-256 hash from April 20, 2026, associated with host 178.128.87.160 in CL-CRI-1131.
- sha2567d766942ef34542cee39c852286599958c4c2e23187010c4d38dbf88fcb40bf8Let's Encrypt TLS certificate SHA-256 hash from Feb. 27, 2026, associated with host 165.22.184.26 in CL-CRI-1131.
- sha25687bf8bc8b4a2cf34f0af1afe161f123a3d200e77f6c6f41b81bf6ae66ee172ecSHA-256 hash associated with the Brazilian financial campaign (CL-CRI-1163).
- sha256a38b2cf8beff32a276eed8783723ecf8cc53d7dc88669e1b998dddc4db6fe996SHA-256 hash associated with the Brazilian financial campaign (CL-CRI-1163).
- urlhxxp://167[.]148[.]195[.]53:8888/socktz_v9[.]exeURL used to download version 9 of the SockTz SOCKS5 proxy tool after versions 1-8 failed to install in the CL-CRI-1163 campaign.