conducting-pass-the-ticket-attack▌
mukul975/Anthropic-Cybersecurity-Skills · updated May 25, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
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 fro
| name | conducting-pass-the-ticket-attack |
| description | 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 fro |
| domain | cybersecurity |
| subdomain | red-teaming |
| tags | - red-team - adversary-simulation - mitre-attack - exploitation - post-exploitation - kerberos - pass-the-ticket - lateral-movement |
| version | '1.0' |
| author | mahipal |
| license | Apache-2.0 |
| d3fend_techniques | - Token Binding - Execution Isolation - Restore Access - Application Protocol Command Analysis - Process Termination |
| nist_csf | - ID.RA-01 - GV.OV-02 - DE.AE-07 |
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
- Gain local admin access on target workstation
- Dump Kerberos tickets from LSASS memory using Mimikatz or Rubeus
- Export tickets in .kirbi format (Mimikatz) or base64 (Rubeus)
- Identify high-value tickets (Domain Admin TGTs, service tickets to critical systems)
Phase 2: Ticket Injection
- Purge existing Kerberos tickets from attacker session
- Import/inject stolen ticket into current session
- Verify ticket is loaded and valid
- Access target resources using injected ticket
Phase 3: Lateral Movement
- Access remote systems using the stolen ticket identity
- Perform actions as the impersonated user
- Collect additional credentials from accessed systems
- 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
How to use conducting-pass-the-ticket-attack on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add conducting-pass-the-ticket-attack
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches conducting-pass-the-ticket-attack from GitHub repository mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate conducting-pass-the-ticket-attack. Access the skill through slash commands (e.g., /conducting-pass-the-ticket-attack) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★34 reviews- ★★★★★Ira Khanna· Dec 24, 2024
conducting-pass-the-ticket-attack reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Chen Mehta· Dec 20, 2024
Registry listing for conducting-pass-the-ticket-attack matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Harper Huang· Nov 15, 2024
We added conducting-pass-the-ticket-attack from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Sakshi Patil· Nov 7, 2024
Useful defaults in conducting-pass-the-ticket-attack — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Chaitanya Patil· Oct 26, 2024
Registry listing for conducting-pass-the-ticket-attack matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Li Choi· Oct 6, 2024
Keeps context tight: conducting-pass-the-ticket-attack is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Amelia Gonzalez· Sep 17, 2024
Registry listing for conducting-pass-the-ticket-attack matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Oshnikdeep· Sep 13, 2024
Keeps context tight: conducting-pass-the-ticket-attack is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Chen Kapoor· Sep 13, 2024
conducting-pass-the-ticket-attack has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Amina Brown· Sep 13, 2024
conducting-pass-the-ticket-attack reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 34