> For the complete documentation index, see [llms.txt](https://reaper.gitbook.io/my-malware-analysis-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://reaper.gitbook.io/my-malware-analysis-guide/welcome-here.md).

# Welcome here!

Welcome to **my malware analysis guide**, this guide is not meant to be perfect, but the main purpose of it is to share what I am learning, and to improve my skills in technical writing and academic presentation.

This project is being continuously improved in terms of structure and materials, and to provide practical and accessible content for learners and professional and of course me :). 

This is built on my knowledge from several certifications and materials so at some point its content will be heavy and long to read (I am trying to make everything easy to understand in few lines).

***

## Before you start

{% hint style="danger" %}
This chapter is very important to **READ AND FOLLOW!!**
{% endhint %}

This type of work is so risky, you may be working sometime with a real malware, so of course you don't want your PC to get infected, right? For this to be done please follow the procedures and make sure you have met the checklist in the Safety Procedures section in **The Guide**.

***

## Who Is This For? <a href="#who-is-this-for" id="who-is-this-for"></a>

This guide is intended for a wide range of users. How you use it depends on your background:

* **Beginners**
  * Learn core concepts in a simplified, beginner-friendly format.
  * Understand malware types, tools, and terminology with clear descriptions.
  * Use it as a structured path to start your malware analysis journey.
* **Cybersecurity Professionals**
  * Use it as a reference during practice or labs.
  * Copy commands, and procedures directly (Of course they are explained).
  * Build custom checklists or test plans based on the documented techniques.

***

## Share Your Feedback <a href="#share-your-feedback" id="share-your-feedback"></a>

* Have suggestions, corrections, or topic requests?
* Reach out via email: [**reaper.gitbook@gmail.com**](mailto:reaper.gitbook@gmail.com)

Your input is appreciated and will help shape future updates.