> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/add-ons/malware/overview.md).

# Overview

The Malware Analysis add-on gives IDA Pro features for malware analysts. You install the add-on with HCLI, and it adds the **Extensions → Malware Analysis** menu to IDA.

The add-on uses IDA's own UI and API, so there is no new interface to learn. Its results show in the disassembly and pseudocode views, and IDA keeps them in your database.

## Purpose

Before you can read the code that matters, malware analysis has many slow manual steps. You must find the packer, unpack the sample, set up a safe debugger, match sandbox output to the code, and more. The add-on does these steps for you, or makes them easier. With the add-on, you can:

* Remove repetitive unpacking work on commodity malware.
* Step through confusing code safely, with no VM to set up.
* Turn sandbox output into context on the code that caused it.

Many teams keep their own scripts for these tasks, and the scripts stop working when their maintainer leaves. Hex-Rays maintains this add-on, so you get regular updates, and you can report bugs to <support@hex-rays.com>.

## Who it is for

The add-on is for malware analysts, often on a team that triages many samples:

* SOC analysts get a high volume of alerts. The multi-service checker and the unpacker help them find the samples that need manual analysis.
* Incident responders must recover the inner payload fast and connect it to the wider investigation. The unpacker recovers the payload, and sandbox integration shows what it did on the system.
* Threat intelligence analysts study code and data structures to write signatures and attribute samples. The add-on gives them unpacked code and run-time context to start from.
* AV and product teams write detections for the inner payload. The add-on can write the unpacked code to a PE or ELF file, which YARA and other scanners can read.

For a team, the add-on gives a common baseline. All analysts can unpack common samples and emulate code in the same way. This makes the analysis more consistent, and junior analysts can recover payloads that otherwise need manual unpacking skills.

## Key features

* [Multi-service checker](#multi-service-checker): find out what external services know about the sample.
* [Automated unpacking](#automated-unpacking): remove the packer and show the inner payload.
* [Isolated system emulation](#isolated-system-emulation): step through code with no risk to your system.
* [Sandbox integration](#sandbox-integration): connect sandbox behavior to the code that caused it.
* [CyberChef](#cyberchef): decode data from the sample in IDA.

### Multi-service checker

Find out what external services already know about the sample before you start your own analysis.

The checker shows one row for each service, with a summary of its result. From VirusTotal, you get the number of engines that detect the sample, the names that the sample is known by, and the sandboxes that have memory dumps of it. From VMRay, you get the verdict and the score. From MalwareBazaar, you get the malware family, the date when the service first saw the sample, and its tags. Select a row to see the details, or open the full report in your browser. The checker searches by the SHA-256 hash of the input file, so you get results before auto-analysis completes.

Open the checker with **Extensions → Malware Analysis → Triage → Services Checker** (<kbd>Shift</kbd> + <kbd>U</kbd>). Each service needs an API key. If a service does not know the sample, you can upload it. By default, the checker asks for confirmation before each upload.

See [Multi-service Checker](https://docs.hex-rays.com/add-ons/malware/concepts/multi-service-checker.md).

### Automated unpacking

Get to the inner payload of a packed sample without manual unpacking work.

The unpacker runs the sample, by default in an emulator, and writes the unpacked code over the packed data in your database. Then it analyzes the code again, rebuilds the import address table (IAT) so that calls to the Windows API show their names, and finds the original entry point. You do not have to set up a debugger, dump memory, or repair imports by hand. For samples that the unpacker cannot handle, you can unpack manually with the isolated system emulator.

When you open a packed PE file, the add-on asks if it should unpack the sample. You can also start the unpacker at any time with **Malware Analysis → Unpacking → Unpack now\...** (<kbd>Shift</kbd> + <kbd>P</kbd>).

![The rebuilt import address table after unpacking](https://492083732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFP6ibt8r6WPBHTqekG9u%2Fuploads%2Fgit-blob-bcb085f55fd6f3a0a1d950eeb136244d10d007f2%2Fiat-after-unpacking.png?alt=media)

See [Automated Unpacking](https://docs.hex-rays.com/add-ons/malware/concepts/automated-unpacking.md), and the how-to [Unpack a Malware Sample](https://docs.hex-rays.com/add-ons/malware/how-tos/unpack-a-malware-sample.md).

### Isolated system emulation

Step through suspicious code safely: the sample runs in an emulator, never on your system.

An emulation session works like a debug session in IDA. Step, set breakpoints, and stop or restart with IDA's debugger controls. The sample cannot change your files, run code on your host, or connect to your network, so you do not need a VM or a remote debugger. When you rename an item during emulation, IDA keeps the new name in your database. Interactive emulation uses [Speakeasy](https://docs.hex-rays.com/add-ons/malware/concepts/emulators/speakeasy.md) or [Sogen](https://docs.hex-rays.com/add-ons/malware/concepts/emulators/sogen.md) and works on PE files.

Start a session with one click on the toolbar button (the "magic wand"), or with **Malware Analysis → Emulation → Start interactive emulation → with Speakeasy** or **with Sogen**.

See [Isolated System Emulation](https://docs.hex-rays.com/add-ons/malware/concepts/isolated-system-emulation.md) and [Isolation](https://docs.hex-rays.com/add-ons/malware/concepts/isolated-system-emulation.md#isolation).

### Sandbox integration

See which code caused the behavior that a sandbox reports.

IDA highlights the instructions that executed in the sandbox run, which shows you the code coverage. The trace view shows the API calls and their arguments, and lets you jump directly to the code that made each call. You can also import memory regions from the run, such as shellcode and injected payloads.

The **Malware Analysis → Sandbox** menu runs the Speakeasy sandbox, loads a Speakeasy report, or fetches or imports VMRay results.

See [Sandbox Integration](https://docs.hex-rays.com/add-ons/malware/concepts/sandbox-integration.md).

### CyberChef

Decode data from the sample, such as a configuration block, without leaving IDA.

CyberChef, the "Cyber Swiss Army Knife", runs in a panel in IDA. Develop and run transformation recipes against data in the IDB, and write the results back into your database.

Open it with **Malware Analysis → Data Transformation → Open CyberChef**. CyberChef is a separate plugin that HCLI installs together with the add-on.

![CyberChef side panel next to the disassembly](https://492083732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFP6ibt8r6WPBHTqekG9u%2Fuploads%2Fgit-blob-9815c62b46a58edf8559d509b4b8c26174acd820%2Fcyberchef-side-panel.png?alt=media\&token=2d74a406-6255-4bd0-a260-9be42813d6f9)

See [CyberChef](https://docs.hex-rays.com/add-ons/malware/concepts/cyberchef.md).

## Getting started

To install the add-on and open your first sample, see [Getting Started](https://docs.hex-rays.com/add-ons/malware/getting-started.md).

For the features in each release, see [Release Notes](https://docs.hex-rays.com/add-ons/malware/release-notes.md).

If you have a question, an idea, or a problem, email <support@hex-rays.com>. The Malware Analysis team reads every message and replies quickly.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hex-rays.com/add-ons/malware/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
