Metasploit › Module 2 › Lesson 2
Console Basics
Prompt, help, version, exit — read the console before modules touch $LAB.
Visual · msf_console_basics
msfconsole help and version. Original Cyberlium.
Opening
The console is a REPL for modules — help and version are your first two commands.
Launch `msfconsole -q` for a quiet prompt. Run `help`, `version`, and `banner` literacy. Notice tab completion and `back` to leave module context. No `use`, no `run`, no RHOSTS this lesson — just navigation. Next: Workspaces.
1. Prompt and context
Global prompt `msf6 >` vs module prompt `msf6 exploit(.) >`. Context matters: options you set may not persist after `back`.
`history` and `grep` in readline help audit what you typed — useful for lab writeups.
Command guide
Try these commands — Prompt and context
═══ TOOLS & WEBSITES ═══ Browse / read these (authorized learning only — stay in YOUR lab / program scope)
msfconsole basics — https://docs.rapid7.com/metasploit/msf-overview/ Command reference — https://docs.rapid7.com/metasploit/msf-console-commands/
═══ INSTALL ═══
Linux (Debian/Ubuntu): Kali: preinstalled, or: sudo apt install metasploit-framework
macOS: Prefer Kali/Linux VM — brew install metasploit (heavy)
Windows: Use Kali VM or WSL with metasploit-framework — not raw Windows host
═══ LINUX / macOS ═══
Command — copy this
msfconsole -q -x 'help; help search; help use; exit' 2>/dev/null || echo 'Run in Kali/lab VM'
Primary tools to practice this lesson: msfconsole. Reference sites: msfconsole basics (https://docs.rapid7.com/metasploit/msf-overview/); Command reference (https://docs.rapid7.com/metasploit/msf-console-commands/). Run every command in the box — install first, then the usage lines — only on YOUR lab / program scope.
2. help and version
`help` lists command families; `help search` narrows. `version` shows framework rev — tie to lab notes when modules differ from blogs.
Save version string in cyberlium-lab; defenders correlate exploits to framework age.
3. Safe defaults
Do not pass `-r resource.rc` from strangers — scripts can set evil RHOSTS. Write your own rc files naming $LAB only.
Exit cleanly with `exit` or Ctrl-D; orphaned handlers are a later-lesson problem on lab only.
4. What you ship: help/version transcript
Saved msfconsole version + help search snippet. No modules run. chmod 600.
5. What you record before the next lesson
Date. version output. help search line. File t14-m02-l02-console-basics.txt chmod 600.
6. Wrong vs right: stranger hosts vs YOUR lab VM
Worked failure — same MSF word, opposite target. Right never needs a café Wi-Fi or classmate laptop.
Wrong
Paste a random resource.rc from GitHub. Run the first exploit in banner art.
Right
help + version only. Next: Workspaces.
Mission: first console session read-only
1) msfconsole -q 2) version 3) help search 4) exit 5) Save transcript chmod 600. No use/run/set RHOSTS.
Stuck? Ask Cyberlium AI Mentor
Prompt looks like hacking; your RoE file decides if action is allowed.
Knowledge Check
APPLY: Safest first msfconsole commands in Cyberlium:
Multiple choice
Knowledge Check
APPLY: True or False: Module context persists after `back` for all options globally.
True or False
Knowledge Check
APPLY: `version` helps you:
Multiple choice