Matching executable copies appear at two paths with Run entries

A Windows executable left matching copies of itself in both the user profile and Windows directory, with registry launch settings pointing to each location. In a sandbox report for the same sample, requests to two remote IP addresses received HTTP 404 responses. That combination raises a consequential question: does an unsuccessful request for remote content mean the executable failed to establish a foothold? The records examined by CTX Threat Intelligence support a more specific answer.