Loaders

Dyana offers a set of loaders for different file types, with each loader having its own set of arguments. By default, each loader runs in an isolated, offline container.

To view the available loaders and their scriptions, run dyana loaders. To show the help menu for a specific loader, run dyana help <loader>.

​

AutoModel

AutoModel is the default loader for machine learning models. It automatically detects and loads machine learning models in various formats, such as TensorFlow, PyTorch, and others, without requiring you to manually specify the type of model or its format. It loads any model that is compatible with AutoModel and AutoTokenizer.

The AutoModel loader is responsible for:

• Automatic detection: The AutoModel loader inspects the file provided and determines the type of machine learning model.
• Loading and execution: Once the model type is identified, the loader then loads the model into the sandboxed environment, allowing it to be run and profiled.

In essence, the AutoModel loader simplifies the process of handling different machine learning model formats by automatically recognizing the model type and loading it appropriately, all within a secure and isolated environment.

Optional Build Arguments: --extra-requirements

​

Arguments

​

Examples

Load a model and run it with an example input:

dyana trace --loader automodel --model /path/to/model --input "This is an example sentence."

automodel is the default loader, so this is equivalent to:

dyana trace --model /path/to/model --input "This is an example sentence."

In case the model requires extra dependencies, you can pass them as:

dyana trace --model tohoku-nlp/bert-base-japanese --input "This is an example sentence." --extra-requirements "protobuf fugashi ipadic"

To perform tokenizer and model initialization without loading weights:

dyana trace --model /path/to/model --low-memory

To increase the execution timeout of the trace in seconds. [default: 60]

This is a common fix for errors related to * timeout: timeout reached, killing container for larger models.

dyana trace --model /path/to/model --timeout 120

​

ollama

Loads and profiles models via an Ollama server. Local models on the host machine are mounted and shared with the container.

• Requires Network: no

​

Arguments

​

Examples

Pull a model on your host machine and profile it:

ollama pull deepseek-r1:1.5b && dyana trace --loader ollama --model deepseek-r1:1.5b

​

LoRA

Loads LoRA adapters via PEFT.

Optional Build Arguments: --extra-requirements

​

Arguments

​

Examples

Load a LoRA adapter and run it with an example input:

dyana trace --loader lora --adapter /path/to/adapter

​

ELF

The ELF loader specifically handles ELF (Executable and Linkable Format) files. ELF is a standard file format commonly used for executables, object code, shared libraries, and core dumps on Unix-like systems (including Linux).

The ELF loader is responsible for:

• Loading ELF files into the sandbox environment.
• Executing the ELF binary in a controlled and isolated manner.
• Profiling the execution or inspecting the contents of the ELF file for further analysis, such as detecting system calls, memory usage, or other behaviors.

This loader allows you to safely run and analyze ELF executables without exposing the underlying system to potential risks, making it especially useful for security research, debugging, or testing ELF binaries in a secure environment.

​

Arguments

​

Examples

Load an ELF file:

dyana trace --loader elf --elf /path/to/linux_executable

Depending on the ELF file and the host computer, you might need to specify a different platform:

dyana trace --loader elf --elf /path/to/linux_executable --platform linux/amd64

Networking is disabled by default, if you need to allow it, you can pass the —allow-network flag:

dyana trace --loader elf --elf /path/to/linux_executable --allow-network

​

pickle

The Pickle loader is designed to handle Pickle serialized files. Pickle is a module specific to Python that’s used to serialize (or “pickle”) Python objects. Meaning, it converts Python objects into a byte stream that can be stored on disk and later deserialized (or “unpickled”) back into the original Python objects.

The Pickle loader is responsible for:

• Loading Pickle files into Dyana.
• Deserializing the serialized Python objects contained in the Pickle file, so they can be analyzed or executed.
• Profiling the deserialized objects or inspecting their behavior to identify any potential security risks or performance issues.

Since Pickle files can sometimes contain malicious code, loading them into Dyana ensures that the deserialization process is safe and doesn’t compromise the host system.

​

Arguments

​

Examples

Load a Pickle file:

dyana trace --loader pickle --pickle /path/to/file.pickle

Networking is disabled by default, if you need to allow it, you can pass the —allow-network flag:

dyana trace --loader pickle --pickle /path/to/file.pickle --allow-network

​

python

The Python loader is specifically designed to handle and execute files related to Python. This includes Python scripts and other Python objects like modules or libraries.

The Python loader is responsible for:

• Loading Python scripts: It allows you to load and execute Python scripts in Dyana.
• Isolated execution: The loader ensures that the Python code runs in a secure, isolated environment, preventing any unintended effects on the host system.
• Profiling: It can also monitor and profile the Python script’s behavior, tracking things like system calls, resource usage, and potential security issues.
• Package and module handling: The loader may also handle Python packages or modules, making sure that dependencies required by the script are available within the sandboxed environment.

By using a Python loader, Dyana enables secure execution and analysis of Python scripts or applications, even if they are untrusted or potentially harmful, by containing them within a controlled environment.

• Requires Network: no
• Optional Build Arguments: --extra-requirements

​

Arguments

​

Examples

Load a Python script:

dyana trace --loader python --script /path/to/file.py

Networking is disabled by default, if you need to allow it, you can pass the —allow-network flag:

dyana trace --loader python --script /path/to/file.py --allow-network

​

PIP

Loads and profiles Python packages installation via PIP.

• Requires Network: yes
• Optional Build Arguments: --extra-dependencies

​

Arguments

​

Examples

Load and profile a Python package via PIP:

dyana trace --loader pip --package requests

You can install a specific version of a package:

dyana trace --loader pip --package requests==2.28.2

You can also pass extra dependencies to be installed:

dyana trace --loader pip --package foobar --extra-dependencies "gcc"

​

JS

The JS loader is designed to handle and execute JavaScript (JS) files in Dyana. JavaScript files are commonly used for web applications and scripts, but they can also pose security risks if they contain malicious code.

The JS loader is responsible for:

• Loading and executing JavaScript: The JS loader is responsible for safely loading and running JavaScript code, such as .js files, in a controlled, isolated environment.
• Isolation from host system: Like other loaders in Dyana, the JS loader ensures that the code is executed without affecting or interacting with the host system directly. This prevents malicious or buggy scripts from causing harm.
• Profiling JavaScript execution: It can monitor the behavior of the JavaScript code during execution, capturing key metrics like memory usage, network calls, and potential security threats.
• Security monitoring: Given that JavaScript is often used in web contexts, it can be a vector for cross-site scripting (XSS) attacks or other vulnerabilities. The JS loader protects the system from these risks by running the code in a sandbox, limiting its scope and access.

By using the JS loader, Dyana ensures that potentially dangerous JavaScript code is executed in a secure, isolated manner, making it safer to work with in research, testing, or debugging scenarios.

• Requires Network: no
• Optional Build Arguments: --extra-requirements

​

Arguments

​

Examples

Load and profile a JS script:

dyana trace --loader js --script /path/to/file.js

Networking is disabled by default, if you need to allow it, you can pass the —allow-network flag:

dyana trace --loader js --script /path/to/file.js --allow-network

​

NPM

Loads and profiles NodeJS packages installation via NPM.

• Requires Network: yes
• Optional Build Arguments: --extra-dependencies

​

Arguments

​

Examples

Load and profile a NodeJS package via NPM:

dyana trace --loader npm --package express

You can install a specific version of a package:

dyana trace --loader npm --package [email protected]

You can also pass extra dependencies to be installed:

dyana trace --loader npm --package express --extra-dependencies "axios"

​

Website

Opens a website in a headless browser and profiles its performance.

• Requires Network: yes

​

Arguments

​

Examples

Load and profile a website:

dyana trace --loader website --url https://www.google.com

You can also save a screenshot of the page:

dyana trace --loader website --url https://www.google.com --screenshot

You can also wait for a specific element to load:

dyana trace --loader website --url https://www.google.com --wait-for "body"