Ravindra BagaleCourses & study guides मराठी Track your progress

39. Malware Threats

By Last updated:

Chala mitrano, Chapter 38 madhe Active Directory identity attacks baghitla – aata malware (दुर्भावनापूर्ण सॉफ्टवेअर). Virus, worm, trojan, ransomware, spyware, rootkit, botnet, fileless, wiper – naave ahe, pan Blue job ekach: spread rokna, detect karna, contain karna, recover karna. Ghabru naka – aapan real ransomware download nahi karnaar. Lab madhe EICAR / pseudo-malware / snapshots. He khup important aahe, lakshat theva!

What you will learn in this chapter

  • Malware types: virus, worm, trojan, ransomware, spyware, adware, rootkit, botnet, fileless, wiper – clear defs for defenders
  • How malware spreads: phishing, drive-by, USB, supply chain, cracked software, Office macros
  • Ransomware deep dive: encryptor vs locker, double extortion, backups + immutable / offline copies (Raja-Rani Traders)
  • Static vs dynamic analysis mindset – hashes, VirusTotal (lab samples only), sandbox ideas; never run unknown malware on host OS
  • Indicators of compromise (IOC): hashes, C2 domains, weird processes, autoruns, DNS spikes
  • Defence stack: AV/EDR, allowlisting, least privilege, patching, email filtering, awareness
  • Safe malware lab: isolated VM + snapshot, no shared folders with host secrets, revert
  • Incident response for malware + CERT-In awareness
  • Project: Build a weak lab VM, simulate safely, fix, re-verify

Lab scope

Study and practice only on your own isolated VMs (VirtualBox/VMware host-only / no shared folders with host secrets). Never download real ransomware, never encrypt personal or office files, never email malware samples. IT Act sections such as 43 and 66 apply if you damage others' systems (verify current text). Use EICAR test file and benign marker scripts only. Lab = learn. Production = defend only.

Concepts in this chapter

  1. 39.1What Is Malware – Types for Defenders
  2. 39.2How Malware Spreads
  3. 39.3Ransomware Deep Dive – Raja-Rani Traders
  4. 39.4Static vs Dynamic Analysis Mindset
  5. 39.5Indicators of Compromise (IOC)
  6. 39.6Defence Stack – Practical Controls
  7. 39.7Safe Malware Lab Setup
  8. 39.8Incident Response for Malware + CERT-In Awareness
  9. 39.9Putting It Together – Purple Team Mindset
  10. 39.10Detecting Data Theft (DLP)

The chapter recap is at the end of the last concept page.

Chapter 39: Malware threats — practice tasks

Open chapter lessons · Full guided lab: check suspicious file hash eicar virustotal (not repeated here)

39.1 Detect EICAR safely

EasyIT

Why: EICAR is a standard harmless test string.

What: Create and scan the EICAR file.

How:

  1. Create eicar.com with the official EICAR test string.
  2. clamscan eicar.com

Expected output: FOUND / Eicar-Test-Signature.

Hint

Do not upload real malware; EICAR is allowed.

Answer / how to check
  1. ClamAV flags it.

39.2 Hash and look up on VirusTotal

MediumRetail

Why: Hash lookup beats running unknown files.

What: Hash a clean file and search VirusTotal by hash only.

How:

  1. sha256sum /bin/ls
  2. Paste hash on virustotal.com (hash only).

Expected output: Known clean Linux binary results.

Hint

Never upload secret documents.

Answer / how to check
  1. VT shows many vendors, clean.

39.3 Phishing attachment rules

EasyBanking

Why: Macros and double extensions trick users.

What: Mark each attachment Risky or OK.

Data file: attach.csv

File name
invoice.pdf.exe
Q3-report.pdf
payroll.xlsm from unknown sender

About this file: Made-up attachments. Each row is one file name to judge.

How:

  1. Read the data file.

Expected output: invoice.pdf.exe Risky; report.pdf OK; unexpected xlsm Risky.

Hint

When unsure, open in a sandbox VM.

Answer / how to check
  1. Two Risky items.

Extended teaching notes

Why this lesson matters

Malware analysis in this course is defensive: recognise indicators, isolate hosts, preserve evidence. Never run unknown malware on your main OS or on someone else's network.

  1. Isolate the host from the network.
  2. Capture volatile data if trained to do so.
  3. Hash samples; search only in licensed/safe tools.
  4. Rebuild from a known-good image when unsure.
  5. Share IOCs with your SOC, not on random chats.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.