Erick Cisneros
ContactResume
Directory
Overview
Experience
Investigations & Tooling
The Trophy Case
Education
Contact Me
Direct Inquiries
Back to Security Investigations & Tooling
INC-2025-AZ01

Azuki Import/Export Compromise

STATUS: CONTAINED

ANALYST: Erick Cisneros Ruballos

DATETIME: Nov 23, 2025

A highly targeted corporate espionage intrusion resulting in external RDP access, Microsoft Defender tampering, active credential dumping via Mimikatz, and bulk data exfiltration leveraging Discord C2 channels.

Incident ResponseKQLDigital ForensicsMITRE ATT&CKLSASS Dumping
See Full Report on GitHub
Case Brief

Executive Summary

Azuki Import/Export Trading Co. recently experienced a targeted intrusion likely stemming from corporate espionage, wherein a competitor successfully undercut a primary shipping contract by exactly 3%.

Initial forensic assessment indicates an external attacker compromised the IT administrator workstation (AZUKI-SL) via a brute-forced Remote Desktop Protocol (RDP) connection. The attacker established deep registry persistence, harvested local administrator credentials, and actively exfiltrated internal pricing data utilizing a Discord webhook tunnel.

IMPACT LEVELHIGH SEVERITY
TARGET HOSTazuki-sl
BREACH VECTORRDP (External)
COMPROMISED ADkenji.sato
Intrusion Killchain

Investigation Timeline

PHASE 1

Initial Access (TA0001)

Brute-force login via external RDP targeting kenji.sato from attacking IP 88.97.178.12.

PHASE 2

Internal Discovery (TA0007)

Immediate execution of 'ARP.EXE -a' post-compromise to map out internal LAN subnet topography.

PHASE 3

Defense Evasion (TA0005)

Attacker staged 'C:\ProgramData\WindowsCache', wiped the Security Event Logs using 'wevtutil', and injected 3 explicit exclusions into Windows Defender.

PHASE 4

System Persistence (TA0003)

Created backdoor local admin account named 'support'. Registered malicious scheduled task mimicking 'Windows Update Check' pointing to payload.

PHASE 5

Credential Access (TA0006)

Transferred a disguised binary 'mm.exe'. Executed 'sekurlsa::logonpasswords' dumping LSASS memory hashes via Mimikatz.

PHASE 6

C2 & Exfiltration (TA0011)

Archived pricing sheets into 'export-data.zip'. Opened an HTTPS tunnel to 78.141.196.6 and exfiltrated the archive via Discord API webhooks.

Threat Intelligence

Indicators of Compromise (IOCs)

Network Infrastructure
IPv4 (Attacker)88.97.178.12
IPv4 (C2)78.141.196.6:443
Filesystem & Payloads
File Payloadexport-data.zip
Binarymm.exe (Mimikatz)
Directory StageC:\ProgramData\WindowsCache
Scriptwupdate.ps1
Telemetry Reconstruction

KQL Threat Hunt Validation

Flag 12 & 13: Mimikatz Execution
KQL Query
DeviceProcessEvents
| where Timestamp between (datetime(2025-11-19) .. datetime(2025-11-20))
| where ProcessCommandLine contains "::"
| where FileName has "mm.exe"
| project Timestamp, DeviceName, FileName, ProcessCommandLine
| where DeviceName has "azuki"
Flag 14 & 15: Discord Exfiltration
KQL Query
// Detecting the zip compression
DeviceProcessEvents
| where Timestamp between (datetime(2025-11-19) .. datetime(2025-11-20))
| where ProcessCommandLine contains "zip"
| where DeviceName has "azuki-sl"

// Finding the upload mechanism via curl to Discord webhooks
DeviceNetworkEvents
| where Timestamp between (datetime(2025-11-19) .. datetime(2025-11-20))
| where DeviceName has "azuki-sl"
| where InitiatingProcessFileName == "curl.exe"
Flag 5: Defender Tampering
KQL Query
DeviceRegistryEvents
| where RegistryKey has @"Windows Defender\Exclusions\Extensions"
| project Timestamp, DeviceName, RegistryKey, RegistryValueName, RegistryValueData
| summarize UniqueExtensions = dcount(RegistryValueName)

Strategic Recommendations

  • 1Reset all Active Directory credentials for compromised accounts (kenji.sato, support).
  • 2Disable external RDP access from public WAN and enforce strict MFA boundaries.
  • 3Wipe the scheduled task 'Windows Update Check' via administrative shell.
  • 4Forensically isolate and delete the staging directory 'C:\ProgramData\WindowsCache'.
  • 5Null-route outbound network connections destined for '78.141.196.6' inside the edge firewall.
© 2026 Erick Cisneros Ruballos
LinkedIn•GitHub•Direct Email