A South Korean remote support vendor's update server sent the 9002 remote access trojan to chosen victims from 18 to 31 July 2018.
Trend Micro named the campaign Operation Red Signature. No public source names the vendor.
What happened
Attackers took over the vendor's update server and sent a malicious update to chosen victims.
- The server sent
update.ziponly to victims in target IP ranges. - The file carried a valid code-signing certificate stolen from the vendor, so Windows showed no warning.
- The payload was the 9002 RAT.
- The attackers then downloaded SharpHound, a custom Mimikatz (
m.exe), a SQL password dumper (ssms.exe), and a PlugX variant (printdat.dll). - They also used an IIS 6 WebDAV exploit tool (
w.exe) for CVE-2017-7269.
The update began at about 13:35 on 18 July 2018. Korean media reported the attacks on 6 August 2018.
Affected versions
- A malicious update of a South Korean remote support product, served from 18 to 31 July 2018.
- The sources name no vendor and no version.
Indicators of compromise
- Servers:
207.148.94.157(distribution) and66.42.37.101(command, for the 9002 RAT and the PlugX variant). - URLs:
hxxp://207.148.94.157/update/rcv50/update.zip,.../file000.zip,.../file001.zip, and/aio.exe,/smb.exe,/m.ex_,/w,/Web.ex_. - SHA-256 of ShiftDoor:
0703a917aaa0630ae1860fb5fb1f64f3cfb4ea8c57eac71c2b0a407b738c4e19. - SHA-256 of
printdat.dll:9415ca80c51b2409a88e26a9eb3464db636c2e27f9c61e247d15254e6fbb31eb. - SHA-256 of
rcview40u.dll:bcfacc1ad5686aee3a9d8940e46d32af62f8e1cd1631653795778736b67b6d6e. - SHA-256 of
m.exe:a3a1b1cf29a8f38d05b4292524c3496cb28f78d995dfb0a9aef7b2f949ac278b. - Other file names:
aio.exe,sharphound.exe,ssms.exe,w.exe,Web.exe,smb.exe,rcview.log.
See the Trend Micro report for the full hash table.
How to check
Search proxy and firewall logs for the two addresses listed above. Then search disks for the tool names.
Get-ChildItem C:\ -Recurse -Include printdat.dll,rcview40u.dll,rcview.log,ssms.exe,sharphound.exe -ErrorAction SilentlyContinue | Get-FileHash -Algorithm SHA256
Compare each hash with the list above.
What to do now
- Find out if any machine took a remote support update between 18 and 31 July 2018.
- If you find an indicator, isolate the host and review the whole network.
- Reset passwords and keys used on those hosts and on servers they can reach.
- Block the two addresses.
Frequently asked questions
Which vendor was hit?
The sources never name the vendor. They say only that it was a South Korean remote support provider.
How did the update pass security warnings?
Attackers signed it with a valid certificate stolen from the vendor.
Sources
Send this page to the person who looks after AI at your company.