Malware Families and Behavior
You will learn to follow a payload's own life: how it spreads, how and at what level its code runs, what keeps the access alive, and what it is finally for. Interviewers test mechanism, not names.
on this pageshowhide
explore
- Spreading and Staging8 questions
- Clearing the Wormability Bar4 questions
- Loaders and Second Stages4 questions
- Getting Code to Run17 questions
- Living Off the Land4 questions
- Fileless Residence4 questions
- Running in Another Process4 questions
- Rootkits and Signed Drivers5 questions
- Staying Resident and Reachable14 questions
- Persistence Triggers6 questions
- Command Channel Choice4 questions
- Rendezvous and Fallback4 questions
- Endgame of Quiet Access25 questions
- Pre-Encryption Leverage4 questions
- Extortion as a Service4 questions
- Wipers and Destruction4 questions
- Renting Out the Victim5 questions
- Commodity Stealers4 questions
- The Exfiltration Tax4 questions
questions
64 · 4 sectionsWhy does malware delivery usually split into a small first-stage loader and a separate second stage?
basics
~10 sThe two halves have different price tags. The first stage is cheap and disposable, built to survive one arrival. The capable second stage is fetched only once the host looks worth spending it on.
What must be true for malware to spread host to host with no user action?
basics
~20 sFour things at once: the next host exposes a service the spreading code can satisfy on its own, no step waits on a person, attempts succeed often enough to keep finding new hosts, and the code can name candidates to try.
Why ship a first stage inside an ISO or a password-protected archive rather than as the file itself?
basics
~20 sContainers buy two different things and candidates name only one. An encrypted archive hides contents from inspection in transit. A mounted disk image historically launders the internet-zone marking, so the file inside runs as if never downloaded.
Fully patched, so nothing is wormable - where does that reviewer's claim break?
basics
~20 sPatch state addresses one route to one precondition. A spreader that logs in with a valid reused credential exploits nothing and is fully wormable on a patched estate, while a critical-rated flaw that needs someone to open a file is not wormable at any severity.
How does an exploit that crashes the service one attempt in five limit a worm's spread?
basics
~20 sEvery failure subtracts a host from the pool that all infected nodes share. A host killed on the first attempt against it is never recruited by anyone, so per-attempt success caps total reach and cuts the number of hosts each infected node can pass the code to.
What does calling malware 'fileless' actually claim about it, and what does it not claim?
basics
~20 sFileless claims only that the code which ran was never a normal executable file launched from disk; it arrived as data and became code in memory. It does not claim that nothing was written to disk.
Why does an operator already running as a user inject into that user's browser instead of opening its own connection?
basics
~20 sThe operator's own process has no business reaching the internet, and its traffic carries no user identity. Running inside the user's browser borrows that person's session, proxy settings and usual destinations, so the outbound traffic looks like their ordinary browsing rather than a strange new program phoning out.
Why does an operator run their payload through a signed Windows system binary rather than dropping an EXE?
basics
~20 sBecause the binary already carries the vendor's trust and is already installed. Nothing attacker-authored arrives as an executable, no install rights are needed, and the run collides with the administration the estate performs every day.
Does installing a rootkit give an adversary the privilege level it hides at?
basics
~20 sNo. A rootkit conceals activity at a level the adversary already controls. Loading a kernel driver or writing firmware needs administrative privilege first, so concealment is something an intrusion buys after it has won, never a route to winning.
Why is 'the payload was memory-only, so the reboot cleared it' usually the wrong conclusion?
basics
~20 sMemory-only describes the executable, not the residence. The body is normally parked as data with something durable to invoke it, so a reboot fires the trigger rather than removing it. And the way in stays open.
Why does an implant pick HTTPS to a permitted destination over a hard-coded IP on a custom port?
basics
~20 sBecause the path already exists. In a fully proxied estate an arbitrary address on an odd port has no route outward at all, while port 443 to a destination the organisation already permits needs no new opening and looks like ordinary browsing.
What does persistence mean for malware on a Windows host, and which kinds of start-up trigger should a defender be able to name?
basics
~20 sPersistence is a stored trigger that makes the host launch malicious code again after sign-out or reboot. A reboot ends running processes but leaves the stored trigger, so only removing the trigger stops the relaunch.
Why can whoever holds a malware sample pre-register its generated C2 domains?
basics
~20 sBecause the generator is deterministic. Algorithm plus seed — usually the current date and a constant compiled in — produces the same names for the implant and for anyone running the sample forward, so future names are computable, not secret.
Your proxy re-originates TLS on every outbound session - why doesn't that remove command and control?
basics
~20 sInterception yields plaintext only where the endpoint trusts the interception authority and does not pin, and exempt populations exist by design. Even where it works, the recovered body can be encrypted by the implant itself - and the destination was permitted anyway.
Why does a per-user autostart on Windows need no administrator rights, and why does it vanish when the user's profile is lost?
basics
~20 sA per-user autostart sits in the current user's own registry hive and Startup folder, so it needs only that user's rights. Both are part of the profile, so a deleted or replaced profile takes the entry with it.
We block USB drives and personal webmail - can a bulk copy still leave a SaaS document tenant?
basics
~20 sBlocking removable media and personal webmail closes two exits, not the class of exit. A bulk copy leaves through the sanctioned cloud storage, sharing links and sync the business itself requires and cannot switch off.
Why does a commodity infostealer run once and never install persistence?
basics
~20 sBecause the operator is paid per install, not per victim. One pass copies the browser profile and other saved material into an archive, uploads it and exits. Staying would add cost and exposure for material already taken.
Why don't restorable backups remove a ransomware crew's leverage over you?
basics
~20 sBecause a copy of the data was taken before anything was encrypted. Restoring files ends the outage but not the threat to publish or sell what was already read, and the backup system itself is attacked early, not last.
In ransomware-as-a-service, what work does the affiliate do that the developer never touches?
basics
~20 sThe developer builds and maintains the encryptor, the builder and the affiliate panel and rents it out. The affiliate runs the intrusion itself - entry, spread, staging, launch - and keeps the larger share of whatever is paid.
Why does a cryptomining implant keep its host healthy and leave the data alone?
basics
~10 sThe asset is the machine's capacity, not its contents. Mining only pays while the host stays up, so the operator avoids anything that would get it rebuilt: no encryption, no visible theft, no crash.