Ursnif VS Italy: Il PDF del Destino By Kostas Published: 2023-07-31 · Archived: 2026-04-06 00:07:26 UTC 9 min read Jul 18, 2023 This is the second blog of this series which displays the actions that threat actors are taking upon post-exploitation efforts. Just a reminder, these short blog posts come with sanitized artifacts of the intrusion I observed. This is so people can use it for training materials or recreate the investigation steps I followed in their own lab. You can find the artifacts in the repo below. Intrusion_data: https://github.com/tsale/Intrusion_data Summary In the first week of July, I observed post-exploitation activity from an Ursnif malware initial infection. Post-exploitation activities were very rapid, with threat actors enabling the VNC feature of the malware to interact with the infected host. Through VNC’s graphical interface, they quickly searched for important documents on mapped share drives. They later used the command prompt to run enumeration commands before using process injection to spawn a Cobalt Strike beacon. Several hours after the initial infection, the Cobalt Strike beacon came to life and threat actors started enumerating the environment. They used their existing beacon session and attempted to elevate their access using a zerologon exploit. After about 10 hours, I witnessed them spawning a new Cobalt Strike beacon using a PowerShell loader. This second beacon communicated with a different C2 IP. This was the last activity I observed through my analysis, it is possible that the threat actors left the infected environment or that the gap of inactivity allowed for response and remediation of the infected host. Further Intelligence Gathering During the ursnif VNC sessions, I was able to extract interesting data from the unencrypted network communication. Specifically, I managed to obtain the threat actors’ clipboard as well as screenshots. This information provides valuable insight into the attackers’ tactics, techniques, and procedures (TTPs). It allows us to see the attack from their eyes. Their respective sections below will cover the relevant details regarding the intrusion. https://kostas-ts.medium.com/ursnif-vs-italy-il-pdf-del-destino-5c83d6281072 Page 1 of 12 The Hands-On-Keyboard (HOK) activity began 30 minutes after the initial execution of the Ursnif malware. This emphasizes the importance of promptly addressing initial access broker malware. During the intrusion, it seemed like the infected host was shared among multiple groups. This is due to the long periods of inactivity observed, the different C2 channels as well as the repetitive enumeration commands on every newly established connection to a different C2 infrastracture. Trustworthy threat intelligence sources reveal how criminals divide responsibilities during an intrusion after the initial infection. Establishing initial access themselves is no longer really required for threat actors, there’s a good chance someone else has already done it and is happy to sell it on. ~ source by @BushidoToken It is also possible for different threat actors to often specialize in different aspects of an attack. In this case, the job of threat actors that responded to the initial infection could have been to profile the victim host and organization. There was no activity from the beacon loaded in memory for five hours after the initial infection. Press enter or click to view image in full size Due to the sensitivity of the enclosed data, the VNC communication was not included in the network traffic artifacts. However, information on how to extract this data as well as sanitized screenshots will be shared down below. Initial Access The phishing campaign that resulted in this intrusion targeted Italian organizations. The phishing email contained a PDF attachment that started the malicious execution chain, as reported by @JAMESWT_MHT in this thread. Press enter or click to view image in full size https://kostas-ts.medium.com/ursnif-vs-italy-il-pdf-del-destino-5c83d6281072 Page 2 of 12 This blog will focus on the malicious Ursnif DLL loader and the post-exploitation activity after the malware was installed on the infected host. Execution After the Ursnif DLL was loaded in memory, a series of automated activities took place in a very short timeframe. Here’s a visualization of the execution flow: Press enter or click to view image in full size https://kostas-ts.medium.com/ursnif-vs-italy-il-pdf-del-destino-5c83d6281072 Page 3 of 12 The malware used mshta.exe to run an encoded script from Registry Key via the Explorer.exe parent process as part of the initial automated tasks. C:\Windows\System32\mshta.exe” “about: Here is a breakdown of the script: ‘about:’: This starting element creates an executable HTML Application loaded as a data URL. ‘