Windows Analysis Report KHAWATMI CO.IMPORT & EXPORT.exe

Signatures

Creates a process in suspended mode (likely to inject code)

May try to detect the Windows Explorer process (often used for injection)

Spawns processes

Signatures

Hides threads from debuggers

Tries to detect Any.run

Found potential dummy code loops (likely to delay analysis)

Checks if the current process is being debugged

Sample might executed code dummy loops to delay execution, try to increase analysis time

Signatures

Uses code obfuscation techniques (call, push, ret)

Signatures

Contains functionality to retrieve information about pressed keystrokes

Sample has functionality to log and monitor keystrokes, analyze it with the 'Simulates keyboard and window changes' cookbook

Signatures

Contains functionality to detect hardware virtualization (CPUID execution measurement)

Detected RDTSC dummy instruction sequence (likely for instruction hammering)

Hides threads from debuggers

Tries to detect Any.run

Tries to detect sandboxes and other dynamic analysis tools (process name or module or function)

Found potential dummy code loops (likely to delay analysis)

Tries to detect virtualization through RDTSC time measurements

Checks if the current process is being debugged

Contains functionality for execution timing, often used to detect debuggers

May try to detect the virtual machine to hinder analysis (VM artifact strings found in memory)

Signatures

May try to detect the Windows Explorer process (often used for injection)

Signatures

Reads ini files

Signatures

Contains functionality to detect hardware virtualization (CPUID execution measurement)

Detected RDTSC dummy instruction sequence (likely for instruction hammering)

Tries to detect virtualization through RDTSC time measurements

Reads software policies

Queries a list of all running drivers

Signatures

Detected potential crypto function

Signatures

Detected potential crypto function

Signatures

C2 URLs / IPs found in malware configuration

Execution Graphs are highly condensed control flow graphs which give the user a synthetic view of the code detected during Hybrid Code Analysis. They include additional runtime information such as the execution status which is highlighted with different colors and shapes.

Entrypoint

Program entry point, most likely the entry point of the PE file.

Key Decision

A code location where a decision has been made to avoid execution of potentially malicious behavior.

Dynamic / Decrypted

Code which has been generated at runtime, often referred to as unpacked or self-modifying code.

Unpacker / Decrypter

Code section which is responsible for unpacking or decrypting a portion of dynamic code.

Executed

Code which has been executed at runtime.

Not Executed

Code which has not been executed at runtime.

Unknown

Code for which it is unknown if it has been executed or not at runtime.

Signature Matched

Code which matches a behavioral signature.

Rich Path

Path through the execution graph which shows a lot of behavior (e.g. with respect to called API functions).

Thread / callback entry

Code corresponding to a thread or callback entry point.

Thread / callback creation

Edges denoting either a thread creation (e.g. using CreateThread) or a callback registration (e.g. EnumWindows).

Entrypoint

VBA program entry point such as Document_Open.

Decryption Function

Function likely responsible for string decryption.

Executed

This line was executed during analysis.

Not Executed

This line was likely not executed during analysis.