Lazarus UpdateAgent profiles 3CX macOS victims
Objective-See analyzed UpdateAgent, the second-stage macOS payload in the Lazarus Group's 3CX supply-chain attack, which exfiltrates victim data to a hard-coded C2 endpoint.
Sourceobjective-see.org — open the original
What to check
- Applies to
- Whether this concerns you is not assessed; the names the report mentions are listed below.
This post continues Objective-See's analysis of the macOS component of the 3CX supply-chain compromise, attributed to North Korea's Lazarus Group. Having previously analyzed the first-stage payload (libffmpeg.dylib), the author obtained and reverse-engineered the second-stage payload, UpdateAgent, an adhoc-signed x86_64 Mach-O binary that was downloaded and executed by the first stage.
UpdateAgent employs basic anti-analysis techniques including forking and self-deletion via unlink to evade file-based AV detection. It reads a legitimate 3CX configuration file (config.json) to extract the provisioning URL and account name, then reads a victim-unique UUID from a locally-stored .main_storage file (XOR-encoded with key 0x7a, written by the first-stage payload). This data is encrypted and combined into a parameterized cookie string, then exfiltrated via HTTP POST to the hard-coded endpoint sbmsa.wiki/blog/_insert using a spoofed Chrome/Windows user-agent.
At analysis time the attacker's C2 infrastructure was offline, preventing observation of any response-handling logic; static analysis showed the malware simply exits after the POST, suggesting UpdateAgent's sole purpose is victim profiling/reconnaissance for a mass supply-chain campaign, allowing Lazarus to later selectively deploy more capable implants to targets of interest. The author provides file and network IOCs and demonstrates detection/protection via Objective-See's free tools (BlockBlock, DNSMonitor, LuLu).
Mentioned in this report
Detection guidance
1 detection for this report is in the app — an indicator rule with Sigma, Splunk SPL, Elastic, Microsoft Defender XDR KQL, and YARA. Free account, no card.
Source reporting: https://objective-see.org/blog/blog_0x74.html
Free public brief. The indicators and the detections with Splunk SPL already written (plus Elastic and KQL where they apply) are in the app with a free account, no card. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), and live profiles of the actors, malware, and campaigns it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,436 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs