Emulator-Based Malware Detection via Execution Profile Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing malware detection methods face challenges in identifying obfuscated malware without executing the malicious code, which can lead to system infection and requires resource-intensive hardened environments.

Innovation Solution

An emulator system that simulates the execution of suspected executable programs, providing emulated APIs and deobfuscating code without actual execution, allowing for malware detection without exposing the system to risk.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If malware is executed for detection, then detection accuracy is improved, but system security is compromised and resource consumption increases

Engineering Contradiction:
Improvedetection accuracyVSAvoidsystem infection risk
Core Design Contradiction:
Measurement precisionVSObject-affected harmful factors

Solution Approach 1:

The patent creates a virtual machine (VM) that copies and replicates the execution environment of the host system. The VM emulates hardware components, operating system, and application environment, allowing malware to be executed within this isolated copy rather than on the actual system. This enables accurate detection of malware behavior while preventing any harmful effects from impacting the real system, thus resolving the contradiction between detection accuracy and system security.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The virtual machine acts as an intermediary layer between the malware and the host system. It provides a controlled environment where malware can execute its operations, but all actions are monitored and contained within the VM boundaries. The VM's isolation mechanisms (memory isolation, CPU virtualization, system call interception) serve as intermediaries that prevent direct access between malware and the host system, enabling safe detection without compromising security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If hardened environments are used for malware execution, then system security is improved, but device complexity and resource requirements increase

Engineering Contradiction:
Improvesystem infection riskVSAvoidenvironment complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

Instead of creating complex hardened environments through multiple security layers and isolation mechanisms, the patent uses a virtual machine that copies the essential execution environment. The VM captures the necessary hardware abstraction, operating system interface, and application context in a simplified manner. This copying approach provides adequate security isolation without requiring complex hardware modifications or multiple nested security layers, thus reducing overall system complexity while maintaining security.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The virtual machine platform provides universal functionality for malware analysis across different malware types and execution environments. A single VM infrastructure can handle various malware families, operating systems, and architectural requirements through configuration rather than physical customization. This multi-functional capability eliminates the need for separate specialized detection systems for different malware categories, reducing device complexity while maintaining comprehensive security.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Object-affected harmful factors

If emulation is used instead of execution, then system security is improved, but detection capability may be compromised

Engineering Contradiction:
Improvesystem infection riskVSAvoiddetection accuracy
Core Design Contradiction:
Object-affected harmful factorsVSMeasurement precision

Solution Approach 1:

The virtual machine serves as an intermediary that faithfully reproduces the execution behavior of native code while maintaining security isolation. It intercepts and emulates CPU instructions, system calls, and hardware operations, providing a accurate representation of malware behavior without actual execution on the host. This intermediary emulation approach preserves detection accuracy by capturing genuine malware operations while preventing any harmful effects from reaching the host system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces direct mechanical execution of malware instructions with an emulated execution model. Instead of allowing malware to directly manipulate host hardware and memory, the VM translates and emulates these operations in a controlled virtual environment. This substitution maintains the essential execution semantics needed for accurate detection while eliminating the direct harmful interactions between malware and the host system, thus preserving detection capability without compromising security.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12333008B2Emulation-based malware detection
Publication Date: 2025.06.17 CROWDSTRIKE
  • US12333008B2 patent drawing
  • US12333008B2 patent drawing
  • US12333008B2 patent drawing

AI summary

An executable program compiled for a first execution environment is obtained. The executable program is processed by an emulation function of a second execution environment to create an execution profile for the executable program. The emulation function of the second execution environment is configured to emulate an execution of the executable program and to replace an application programming interface (API) function call within the executable program with a call to an emulated API function call within the second execution environment. A malware classification is determined for the executable program based on the execution profile.