MSF RCP key terms

An open-source penetration testing platform written largely in Ruby that provides a modular library of exploits, payloads, encoders, and auxiliary tools, plus an interactive console for running them against authorized targets.

The primary interactive command-line interface to the Metasploit Framework, used to search for modules, set options, run exploits and auxiliary modules, and manage sessions and workspaces.

A self-contained Ruby component in Metasploit that performs one task, such as exploiting a flaw, scanning a service, or generating a payload; modules are organized by type and loaded on demand.

A Metasploit module that delivers a payload by abusing a specific vulnerability in a target service or application, defining the target versions, offsets, and delivery technique required.

A Metasploit module that performs supporting tasks without delivering a payload, such as port scanning, service version detection, credential brute forcing, or fuzzing.

The code an exploit delivers and executes on a target after successful exploitation, ranging from a simple command to a full remote shell or Meterpreter agent.

A small first-stage payload whose job is to establish a connection back to the attacker and download or inject the larger second-stage payload into memory.

The larger second-stage payload fetched and executed by a stager, containing the full functionality such as a Meterpreter session or shell environment.

An advanced in-memory payload that provides an interactive agent with commands for file transfer, process manipulation, credential access, pivoting, and privilege escalation, without writing itself to disk.

A payload in which the compromised target initiates an outbound connection back to the attacker's listener, commonly used to bypass inbound firewall rules on the target.

A payload in which the target opens a listening port that the attacker connects to, requiring the target to accept inbound connections and often blocked by firewalls.

A Metasploit component that waits for an incoming connection from a stager or reverse shell and then services the resulting session, configured with matching host and port options.

An active connection between Metasploit and a compromised target, created when a payload executes and a handler receives it; sessions can be shell, Meterpreter, or other types.

The Metasploit option specifying target host addresses, which accepts single addresses, ranges, CIDR notation, or a file of hosts for use by exploits and scanners.

The Metasploit option specifying the remote port on the target that a module connects to, often defaulting to the standard port for the affected service.

The Metasploit option specifying the local address the attacker's machine uses for a listener or callback, which must be reachable from the target for reverse payloads.

The Metasploit option specifying the local port on which a handler listens for an incoming reverse connection from a payload.

Within an exploit module, a selectable definition of the specific operating system, service version, or architecture the exploit is configured to attack, affecting offsets and payload compatibility.

A Metasploit command that runs a module's non-exploiting detection routine, if implemented, to report whether the target appears vulnerable before an exploit is attempted.

A Metasploit auxiliary module that probes targets to identify open ports, running services, versions, or vulnerabilities, producing results without exploiting them.

A scan that identifies which network services are listening on discovered ports and often their product and version, informing selection of matching exploit modules.

A weakness in software, configuration, or process that can be exploited to compromise confidentiality, integrity, or availability; Metasploit modules typically target a specific known vulnerability.

The process of confirming that a suspected weakness is real and exploitable in the target environment, using safe checks or controlled exploitation, before reporting it as a finding.

A reported finding that does not actually exist or is not exploitable on the target, often caused by inaccurate version banners, incomplete checks, or misconfigured scanners.

A Metasploit module that transforms a payload's bytes to avoid bad characters or evade simple signature detection; encoding is not a substitute for proper antivirus testing.

Byte values that cannot appear in a payload because the vulnerable input path or protocol will truncate or alter them, requiring encoding or payload adjustment.

A command-line tool that combines payload generation and encoding, producing standalone payload files in formats such as executables, scripts, and raw shellcode for delivery.

A Metasploit module run against an existing session to gather information, escalate privileges, dump credentials, or move laterally within the authorized scope.

Using a compromised host as a relay to reach systems on networks not directly accessible from the attacker, often through Metasploit route or proxy features.

A named container in Metasploit, especially in Pro, that groups hosts, services, credentials, sessions, and findings belonging to one engagement or project.

An attack that targets a user's application, such as a browser or document reader, rather than a directly reachable server service, typically relying on user interaction.

Manipulating people into taking actions such as opening a file or revealing credentials; in Metasploit contexts this often means pairing a crafted payload with a convincing pretext.

Sending deceptive messages that impersonate a trusted party to lure recipients into clicking links, opening attachments, or submitting credentials, commonly used to deliver client-side payloads.

A Metasploit Pro organizational unit that stores all data for an engagement, including hosts, services, vulnerabilities, credentials, sessions, and generated reports.

A Metasploit Pro output artifact that summarizes findings, evidence, and remediation guidance for stakeholders, configurable by template, scope, and included data types.

A stored username and secret pair, such as a password or hash, that Metasploit can collect from sessions or use in authentication attempts against authorized targets.

A documented agreement defining authorized targets, permitted techniques, time windows, escalation contacts, and constraints for a penetration test before testing begins.

The explicitly defined set of systems, networks, and activities a tester is permitted to touch; anything outside it must not be scanned or exploited.

Documented permission from the system owner allowing testing of specified assets; without it, using Metasploit against a system may be unlawful and unethical.

The professional principles guiding penetration testers to act only within consent, minimize harm, protect collected data, and disclose findings responsibly.