An exploit kit is a toolkit hosted on a malicious or compromised site that automatically fingerprints a visitor’s browser and plugins and launches matching exploits. A drive-by download is the result: malware installed simply by visiting the page, with no click required, by exploiting an unpatched vulnerability. Defenses: patching, disabling unneeded plugins, and browser sandboxing.
Remote code execution and privilege.
Bind shell (opens port and waits for attacker).
Reverse shell (connects to port on attackers C2 server).
Email spoofing.
IP address spoofing.
MAC spoofing.
Biometric spoofing.
ARP spoofing.
Metasploit.
ExploitDB.
Shodan - Google but for devices/servers connected to the internet.
Google the version number of anything to look for exploits.
Hak5 tools.
https://attack.mitre.org/
Begin with scoping and authorization: define targets, rules of engagement, and timing, and get written permission. Then follow the standard phases — reconnaissance (OSINT, passive/active), scanning and enumeration (Nmap, service/version discovery), vulnerability identification, exploitation to prove impact, post-exploitation/pivoting as scope allows, and finally reporting with reproducible steps and remediation. Confirm up front whether it is black/grey/white box, whether the systems are production or test, and whether a backup exists before you touch anything.
Conficker.
Morris worm.
Zeus malware.
Stuxnet.
Wannacry.
CookieMiner.
Sunburst.
Various methods of getting remote code execution.
Domain-flux.
Fast-Flux.
Covert C2 channels.
Evasion techniques (e.g. anti-sandbox).
Process hollowing.
Mutexes.
Multi-vector and polymorphic attacks.
RAT (remote access trojan) features.
Obfuscation of code, unique strings (you can use for identifying code).
IdaPro, Ghidra.
Describe the differences.
Virus total.
Reverse.it.
Hybrid Analysis.