As of this writing, 25 of 43 virus engines identify this sample as malware.
The file is packed, but we can’t unpack it at this time.
This question can’t be answered without unpacking the file.
This question can’t be answered without unpacking the file.
For the file Lab01-03.exe, VirusTotal.com reports a variety of different signatures with vague-sounding names. The most common signature is that of a file packed with the FSG packer.
When we open the file in PEview, we see several indications that the file is packed. The first
is that the file sections have no names. Next, we see that the first section has a virtual size of
0x3000, but a raw data size of 0. We run PEiD to confirm, and it identifies the packer as FSG 1.0 -> dulek/xt.
To confirm that the file is packed, we search for the imports, but there doesn’t seem to be an import table. An executable file without an import table is extremely rare, and its absence tells us that we should try another tool, because PEview is having trouble processing this file.
We open the file with Dependency Walker, and see that it does have an import table, but it
imports only two functions: LoadLibrary and GetProcAddress. Packed files often import only these two functions, which
further indicate that this file is packed. We can try to unpack the file using UPX, but we know that
the file is packed with FSG, rather than UPX. We’ll return to this file in Chapter 18, once we have covered the skills to unpack it.