
Two Windows samples tied to the same QLOG output path
Sandbox records identify each executable as the producer of a text file at the same temporary path, making the repeated output more than a coincidental file listing. Similar build characteristics and Restart Manager DLL loads strengthen the comparison, but the records do not establish what the logs contain or show an attack sequence.
Two different Windows executables left a text file at the same temporary path, AppData\Local\Temp\QLOG\ThreadId(1).LOG, and the sandbox records identify each sample process as the producer of its own file. That is a stronger connection than two suspicious files merely appearing in the same report. It raises a specific question: does the repeated output reflect a common executable pattern, and how much of the surrounding activity belongs to that pattern?
Members-only article
This story is members-only. Sign in to read the full body, indicators of compromise, and VirusTotal context.
Sign in to read