Certipy - AD CS Attack & Enumeration Toolkit
Certipy is a powerful offensive and defensive toolkit for enumerating and abusing Active Directory Certificate Services (AD CS). It helps red teamers, penetration testers, and defenders assess AD CS misconfigurations - including full support for identifying and exploiting all known ESC1-ESC16 attack paths.
[!WARNING] Use only in environments where you have explicit authorization. Unauthorized use may be illegal.
🔍 Features
- 🔎 Discover Certificate Authorities and Templates
- 🚩 Identify misconfigurations
- 🔐 Request and forge certificates
- 🎭 Perform authentication using certificates
- 📡 Relay NTLM authentication to AD CS HTTP(S)/RPC endpoints
- 🗝️ Support for Shadow Credentials, Golden Certificates, and Certificate Mapping Attacks
- 🧰 And much more!
📚 Full Wiki & Documentation
Read the full step-by-step usage guide, including installation, vulnerability explanations, examples, and mitigations in the 📘 Certipy Wiki.
⚙️ Installation
See the Installation Guide for instructions on how to install Certipy.
🚀 Quick Start
See the Quick Start Guide for a quick overview of the most common commands and usage examples.
🎯 Supported AD CS Vulnerabilities
Certipy supports detection and exploitation of AD CS vulnerabilities across the full range of ESC1-ESC16.
For detailed explanations and exploitation steps, refer to the Certipy Wiki.
📎 Resources
See the Resources for selection of key resources related to AD CS security.
🤝 Contributing
Contributions are welcome! See CONTRIBUTING.md for guidelines on reporting issues, improving documentation, or submitting pull requests.
🌟 Sponsors
Thanks to these generous sponsors for supporting the development of this project. Your contributions help sustain ongoing work and improvements.
👤 Author
Developed by @ly4k, with valuable contributions from the community.
📘 Wiki
📖 Visit the Certipy Wiki for detailed documentation, usage examples, ESC vulnerability breakdowns, and mitigation advice.
Metadata
Release files for certipy-ad 5.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| certipy_ad-5.1.0.tar.gz | 155.3 kB | Without provenance | Details for certipy_ad-5.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| certipy_ad-5.1.0-py3-none-any.whl | Python 3 | none | any | Details for certipy_ad-5.1.0-py3-none-any.whl |
Total release size: 333.4 kB
Release files / certipy_ad-5.1.0.tar.gz
| Download URL | certipy_ad-5.1.0.tar.gz |
|---|---|
| Size | 155.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b10b3a4e91f8aa1c7e403fef2ec5aa89d84a69e09e7e6e0602af3e036f4271e
|
|
BLAKE2b-256 checksum How to use checksums |
b67c84b900ca98998b06189cafc9c889f41fff64cc1857ad10dd1f9a50cf4f2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / certipy_ad-5.1.0-py3-none-any.whl
| Download URL | certipy_ad-5.1.0-py3-none-any.whl |
|---|---|
| Size | 178.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ff0d0b78cb1d83349d3ee93fafc2c870198cd36fc59a6d40f0827fe187b5077
|
|
BLAKE2b-256 checksum How to use checksums |
54f17a25f7a18518132191651e37a4df293960e5e347b60c32ac88f1f7ba2386
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for certipy-ad 5.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.