AGENT SKILL

conducting-pass-the-ticket-attack

Perform Pass-the-Ticket (PtT) lateral movement by extracting Kerberos TGT/TGS tickets from LSASS memory on a compromised host and injecting them into another session to impersonate the ticket owner without knowing their password. Use during authorized post-exploitation to move laterally or escalate access via stolen Kerberos tickets, or to validate detections for Kerberos ticket theft and reuse.

License 许可
Apache-2.0
最近更新
2026-09-11
Stars
★ 0
Forks
0

01 前言 Front Matter

name
conducting-pass-the-ticket-attack
tags
[ "red-team", "adversary-simulation", "mitre-attack", "exploitation", "post-exploitation", "kerberos", "pass-the-ticket", "lateral-movement" ]
author
mahipal
domain
cybersecurity
license
Apache-2.0
version
1.0
nist_csf
[ "ID.RA-01", "GV.OV-02", "DE.AE-07" ]
subdomain
red-teaming
description
Perform Pass-the-Ticket (PtT) lateral movement by extracting Kerberos TGT/TGS tickets from LSASS memory on a compromised host and injecting them into another session to impersonate the ticket owner without knowing their password. Use during authorized post-exploitation to move laterally or escalate access via stolen Kerberos tickets, or to validate detections for Kerberos ticket theft and reuse.
mitre_attack
[ "T1550.003", "T1558.003", "T1078" ]
d3fend_techniques
[ "Token Binding", "Execution Isolation", "Restore Access", "Application Protocol Command Analysis", "Process Termination" ]

02 资源文件 7

03 SKILL.md 正文

Conducting Pass-the-Ticket Attack

Legal Notice: This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.

Overview

Pass-the-Ticket (PtT) is a lateral movement technique that uses stolen Kerberos tickets (TGT or TGS) to authenticate to services without knowing the user's password. By extracting Kerberos tickets from memory (LSASS) on a compromised host, an attacker can inject those tickets into their own session to impersonate the ticket owner and access resources as that user.

When to Use

  • When conducting security assessments that involve conducting pass the ticket attack
  • When following incident response procedures for related security events
  • When performing scheduled security testing or auditing activities
  • When validating security controls through hands-on testing

Prerequisites

  • Familiarity with red teaming concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

MITRE ATT&CK Mapping

  • T1550.003 - Use Alternate Authentication Material: Pass the Ticket
  • T1003.001 - OS Credential Dumping: LSASS Memory
  • T1558 - Steal or Forge Kerberos Tickets
  • T1021.002 - Remote Services: SMB/Windows Admin Shares

Workflow

Phase 1: Ticket Extraction

  1. Gain local admin access on target workstation
  2. Dump Kerberos tickets from LSASS memory using Mimikatz or Rubeus
  3. Export tickets in .kirbi format (Mimikatz) or base64 (Rubeus)
  4. Identify high-value tickets (Domain Admin TGTs, service tickets to critical systems)

Phase 2: Ticket Injection

  1. Purge existing Kerberos tickets from attacker session
  2. Import/inject stolen ticket into current session
  3. Verify ticket is loaded and valid
  4. Access target resources using injected ticket

Phase 3: Lateral Movement

  1. Access remote systems using the stolen ticket identity
  2. Perform actions as the impersonated user
  3. Collect additional credentials from accessed systems
  4. Document evidence of successful lateral movement

Tools and Resources

Tool Purpose Command
Mimikatz Ticket export/import sekurlsa::tickets /export, kerberos::ptt
Rubeus Ticket dumping and injection dump, ptt, tgtdeleg
Impacket ticketConverter Convert between formats ticketConverter.py ticket.kirbi ticket.ccache
Impacket psexec/smbexec Remote execution with ticket KRB5CCNAME=ticket.ccache psexec.py

Detection Indicators

  • Event ID 4768 with unusual client addresses
  • Event ID 4769 service ticket requests from unexpected hosts
  • TGT usage from different IP than the TGT was issued to
  • Multiple authentications from same ticket across different workstations

Validation Criteria

  • [ ] Kerberos tickets extracted from compromised host
  • [ ] Tickets injected into attacker session
  • [ ] Lateral movement demonstrated using stolen tickets
  • [ ] Evidence captured for reporting

04 同仓库更多 Skills

NeelakshSaxena
NeelakshSaxena/Vayu

runpodctl

Runpod CLI for managing GPU/CPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send/receive). Use for terminal/CI/scripting, Hub browse/deploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod

Start here for any Runpod task — running GPU/CPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-usage

How Runpod works and how to work it — pods vs serverless, GPU/VRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv/apt). Use to answer "how does X work", "which GPU", "how do I build a container", or "how do I stand up a workload on a pod". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-templates

Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says "run <X> on a pod" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-migrate

Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.

★ 0
NeelakshSaxena
NeelakshSaxena/Vayu

runpod-mcp

Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU/CPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.

★ 0