MOVEit Zero Day – Detection Opportunities

Several potential indicators of compromise were noted by the community:

  • Look for a file named human2.aspx in the wwwroot folder of the MOVEit install directory; this is potentially a web shell utilized by the attackers. The web shell code looks for an inbound request containing a header named X-siLock-Comment and will return a 404 “Not Found” error if the header was not populated with a specific password-like value. Other HTTP headers include X-siLock-Step[1-3].
  • Other locations for artifacts of compromise may be present in the C:\Windows\Temp and \microsoft.net\Framework64\ folders: “A new DLL file starting with App_web_randomchars.dll. If you have two, the one from around the last week or so would be the ‘bad’ one under c:\windows\microsoft.net\framework64\v…\temporary asp.net files/root/RANDOMCHARS/RANDOMCHARS/ then a library. IF YOU HAVE TWO App_Web_randomchars.dll YOU’VE PROBABLY BEEN COMPROMISED. There should only be one.”
  • The presence of action=m2 in IIS logs; a post to aspx suggests that the m2 command activates human2.aspx. Investigators should verify that data is posted to human2.aspx and not human.aspx, which is a legitimate component of MOVEit.
  • Search within the MOVEit database for user Health Check Service, as well as any active sessions for this user.

Indicators of Compromise

The following are the available indicators of compromise DeepSeas has observed in relation to this incident, from both public and internal sources:

  • 89.39.105.108
  • 5.252.190.197
  • 195.128.248.40
  • 84.234.96.104

Explore the DeepSeas cyber defense solutions

https://community.progress.com/s/article/MOVEit-Transfer-Critical-Vulnerability-31May2023

https://www.rapid7.com/blog/post/2023/06/01/rapid7-observed-exploitation-of-critical-moveit-transfer-vulnerability/

 

https://www.trustedsec.com/blog/critical-vulnerability-in-progress-moveit-transfer-technical-analysis-and-recommendations/