Malware analysis basics in Cybersecurity - Step-by-Step Execution

Concept Flow - Malware analysis basics

Receive Suspicious File

↓

Static Analysis

↓

Dynamic Analysis

↓

Behavior Observation

↓

Report Findings

↓

Mitigation

Malware analysis starts by getting the suspicious file, then checking it without running it (static), then running it safely (dynamic), watching what it does, and finally reporting and stopping it.

Execution Sample

Cybersecurity

1. Get suspicious file
2. Check file info (size, type)
3. Scan file with antivirus
4. Run file in safe environment
5. Watch file actions
6. Write report

This sequence shows the basic steps to analyze malware from receiving to reporting.

Analysis Table

Step	Action	What Happens	Result
1	Receive Suspicious File	File is obtained for analysis	File ready for checking
2	Static Analysis	Check file properties without running	Identify file type, hashes, strings
3	Scan with Antivirus	Run antivirus scan on file	Detect known malware signatures or none
4	Dynamic Analysis	Run file in isolated environment	Observe real-time behavior safely
5	Behavior Observation	Monitor file actions (network, files)	Record suspicious activities
6	Report Findings	Summarize analysis results	Create report for response team
7	Mitigation	Apply fixes or blocks based on report	Prevent malware spread or damage

💡 Analysis ends after reporting and mitigation steps to protect systems.

State Tracker

Variable	Start	After Step 2	After Step 4	After Step 6	Final
File Status	Suspicious	Analyzed statically	Analyzed dynamically	Behavior recorded	Mitigated or flagged
Threat Level	Unknown	Potential risk	Confirmed behavior	Assessed risk	Resolved or monitored

Key Insights - 3 Insights

Why do we do static analysis before running the file?

Static analysis (Step 2) helps understand the file safely without risk. It shows file info and possible threats before running it in Step 4.

What is the purpose of running the file in a safe environment?

Dynamic analysis (Step 4) lets us see what the file actually does without risking the real system, as shown in the execution table.

How does behavior observation help in malware analysis?

Observing behavior (Step 5) reveals actions like network calls or file changes, which static checks might miss, helping assess threat level.

Visual Quiz - 3 Questions

Look at the execution table, what is the result after Step 3?

A Known malware signatures detected or none

B File is run in a safe environment

C File type and hashes identified

D Report created for response team

💡 Hint

Check the 'Result' column for Step 3 in the execution table.

At which step does the file behavior get recorded?

A Step 2 - Static Analysis

B Step 5 - Behavior Observation

C Step 4 - Dynamic Analysis

D Step 6 - Report Findings

💡 Hint

Look at the 'Action' and 'What Happens' columns in the execution table.

If the file is found safe during static analysis, what happens next?

A Immediately apply mitigation

B Skip dynamic analysis and report safe

C Proceed to dynamic analysis to confirm behavior

D Delete the file without further checks

💡 Hint

Refer to the logical flow in concept_flow and the execution steps.

Concept Snapshot

Malware analysis basics:
1. Receive suspicious file
2. Static analysis: check file info safely
3. Dynamic analysis: run in isolated environment
4. Observe behavior: monitor actions
5. Report findings
6. Apply mitigation to protect systems

Full Transcript

Malware analysis starts by receiving a suspicious file. First, static analysis checks the file's properties without running it to avoid risk. Then, dynamic analysis runs the file in a safe, isolated environment to observe its real behavior. Behavior observation records actions like network connections or file changes. Finally, analysts write a report and apply mitigation steps to protect systems from harm. This step-by-step process helps safely understand and stop malware threats.