Skip to content

Glossary

Key terminology and concepts in Malbox

A configuration set that defines how analysis tasks should be performed, including which plugins to use, VM configurations, network settings, and timeout values.

A unit of work in Malbox that represents the analysis of a specific sample with a defined profile and configuration.

An automation tool used by Malbox to configure virtual machines with necessary analysis tools and settings.

The CPU architecture targeted by a virtual machine or plugin. Malbox supports x86 and x64 architectures.

A component in Malbox that creates customized virtual machine images using Packer.

The command-line tool for interacting with Malbox, providing access to all system functionality.

An abstraction for message passing between components in Malbox, implemented using iceoryx2 for efficient IPC.

A Malbox component that manages downloading and verifying source files like operating system ISOs.

Analysis performed by executing a sample in a controlled environment and observing its behavior.

A deployment context in Malbox (development, staging, production) that affects logging, debugging, and other behaviors.

Defines where a plugin executes - on the host system, in a guest VM, or in a hybrid configuration.

Rules that define how a plugin can execute in relation to other plugins: Exclusive, Sequential, Parallel, or Unrestricted.

A virtual machine running an analysis task.

A plugin that runs inside a virtual machine, typically used for dynamic analysis.

The machine running the Malbox core system.

A plugin that runs on the host system, typically used for static analysis.

A plugin with components that run on both the host system and in guest VMs.

The virtual machines, networks, and storage resources managed by Malbox.

The mechanism through which Malbox components communicate. Malbox uses iceoryx2 for efficient zero-copy IPC.

A shared memory communication library used by Malbox for efficient, zero-copy inter-process communication.

A virtual machine managed by Malbox for running dynamic analysis.

A hypervisor or virtualization platform (KVM, VMware, VirtualBox) used to run virtual machines.

Malicious software that is the target of analysis in Malbox.

An infrastructure automation tool used by Malbox to create customized virtual machine images.

The operating system type (Windows, Linux) of a virtual machine or analysis environment.

An extension module that provides specific analysis capabilities to Malbox.

A running instance of a plugin, managed by the Plugin Manager.

A component that manages the lifecycle of plugins, including loading, initialization, and communication.

A catalog of all available plugins and their capabilities.

The current lifecycle status of a plugin: Created, Starting, Running, Stopping, Stopped, or Failed.

A component that allocates and manages virtual machines and other resources needed for analysis tasks.

A server component that receives analysis results from guest VMs.

A file submitted for analysis.

A component that manages the execution of analysis tasks, including prioritization and resource allocation.

A catalog of available operating system images and other source files that can be downloaded.

The type of a downloadable source file: ISO, VM Image, Container Image, Archive.

Analysis performed by examining a file without executing it.

See “Analysis Task”.

A component that orchestrates the execution of analysis tasks.

A prioritized list of pending analysis tasks.

The current status of an analysis task: Pending, Initializing, PreparingResources, Running, Stopping, Completed, Failed, Canceled.

An infrastructure automation tool used by Malbox to provision and configure virtual machines.

An isolated environment used for dynamic analysis of malware.

A disk image containing an operating system and analysis tools, used to create VMs.

A process responsible for executing analysis tasks.

A collection of worker processes managed by the task coordinator.