Skip to main content
The dump command provides comprehensive Kerberos ticket extraction capabilities from system memory, supporting both targeted and bulk harvesting operations across user sessions.

Memory Extraction

Extract tickets directly from LSA memory structures

Multi-Session Support

Access tickets across all user sessions when elevated

Flexible Filtering

Target specific users, services, or session IDs

Export Ready

Base64-encoded output ready for injection or analysis

Overview

Extract all current Kerberos tickets from memory on the local system. This command provides comprehensive ticket harvesting capabilities, extracting both TGTs and service tickets for offline analysis and reuse.

Parameters

Available Operations

  • Extract current user tickets
  • Access current LUID only
  • View authenticated services
  • Export for analysis

Limitations

  • No other user sessions
  • No cross-LUID access
  • No system tickets
  • Limited session scope
Typical Extraction Scope:
  • User’s TGT (krbtgt ticket)
  • Service tickets for accessed resources
  • Cached authentication tickets
  • Current session credentials only
Use Cases:
  • Personal credential analysis
  • Current session assessment
  • Individual ticket extraction
  • Basic reconnaissance

TGT Characteristics

Service Pattern: krbtgt/DOMAIN.COMProperties:
  • Domain authentication proof
  • Service ticket request capability
  • Renewable based on policy
  • Session-specific encryption

Attack Value

Capabilities:
  • Request any domain service
  • Enable lateral movement
  • Support golden ticket creation
  • Facilitate pass-the-ticket
Action Header
string
Indicates the operation being performedExamples:
  • [*] Action: Dump Kerberos tickets (Current User)
  • [*] Action: Dump Kerberos tickets (All Users)
  • [*] Action: Dump Kerberos tickets (LUID: 0x12345)
Current LUID
hex
Current process logon session identifierFormat: [*] Current LUID : 0x[hexvalue]Common Values:
  • 0x3e7 - SYSTEM session
  • 0x3e4 - NETWORK SERVICE
  • 0x3e5 - LOCAL SERVICE
Session Information
object
Authentication Details:
  • UserName - Account name (user, computer, service)
  • Domain - Authentication domain
  • LogonId - Session identifier (matches LUID)
  • UserSID - Security identifier
  • AuthenticationPackage - Kerberos, NTLM, etc.
  • LogonType - Interactive, Service, Network, etc.
  • LogonTime - Session establishment time
  • LogonServer - Authenticating domain controller
  • LogonServerDNSDomain - Domain FQDN
  • UserPrincipalName - UPN if available
1

Encryption Analysis

AES256

Type: 0x12 - AES256-CTS-HMAC-SHA1-96Characteristics:
  • Strongest available encryption
  • Default in modern domains
  • FIPS 140-2 compliant
  • Preferred for security

AES128

Type: 0x11 - AES128-CTS-HMAC-SHA1-96Characteristics:
  • Strong encryption standard
  • Widely supported
  • Good performance balance
  • Acceptable for most environments
2

Timing Analysis

Validity Period Assessment:
  • Compare start/end times for anomalies
  • Check for unusually long durations
  • Identify renewable vs. non-renewable tickets
  • Look for post-dated or future tickets
Renewal Patterns:
  • Standard TGT: 10 hours validity, 7 days renewable
  • Service tickets: 10 hours validity, not renewable
  • Anomalous patterns may indicate attacks
3

Principal Analysis

Service Principal Patterns:
  • krbtgt/* - Ticket Granting Tickets
  • cifs/* - File sharing access
  • host/* - General host services
  • http/* - Web service access
  • Custom SPNs for specialized services
Client Principal Assessment:
  • User accounts: username@DOMAIN
  • Machine accounts: COMPUTER$@DOMAIN
  • Service accounts: service@DOMAIN
4

Flag Interpretation

1

TGT Extraction & Reuse

2

Service Ticket Reuse

3

Cross-Session Operations

Combine dump with session management for advanced scenarios
Rubeus dump operations can trigger multiple detection mechanisms
1

Privilege Problems

Symptoms:
  • “Access Denied” errors
  • Empty output despite tickets existing
  • LUID enumeration failures
Diagnosis:
Solutions:
  • Run from elevated context
  • Use appropriate user session
  • Check process integrity level
  • Verify SeDebugPrivilege
2

Anti-Malware Interference

Common Indicators:
  • Process termination
  • API call blocking
  • Memory access failures
  • Behavioral detection alerts
Mitigation Approaches:
  • Use process exclusions
  • Implement custom obfuscation
  • Modify compilation parameters
  • Use alternative execution methods
1

Reconnaissance Phase

Initial Assessment:
Target Identification:
  • Identify high-value sessions
  • Locate administrative accounts
  • Map available services
  • Assess delegation opportunities
2

Targeted Extraction

Strategic Harvesting:
Documentation:
  • Record extraction timestamps
  • Note ticket validity periods
  • Document source sessions
  • Track service relationships
3

Analysis & Validation

Ticket Assessment:
Quality Control:
  • Verify ticket integrity
  • Check expiration times
  • Validate service principals
  • Assess encryption strength
4

Utilization & Testing

Ticket Injection:
Operational Testing:
  • Validate service access
  • Test lateral movement
  • Confirm privilege levels
  • Document successful paths

Quick Enumeration

triage - Fast ticket overview and session mapping

Detailed Listing

klist - Comprehensive current ticket analysis

Ticket Analysis

describe - Deep ticket structure examination

Ticket Injection

ptt - Pass extracted tickets to sessions

Real-time Monitoring

monitor - Continuous ticket capture

Automated Collection

harvest - Systematic ticket harvesting