ad-cs-abuse
Audited by Socket on Sep 19, 2026
4 alerts found:
Securityx4SUSPICIOUS. The skill is internally coherent as an AD CS attack playbook, but its actual footprint is a high-risk offensive security capability for an AI agent: exploit execution, credential use, persistence, credential dumping, and anti-forensics. Supply-chain trust is weak because it mixes official and unofficial packages plus git-cloned PoCs, and forwards sensitive creds/material into those external tools.
The visible fragment is an extensive AD CS exploitation and post-exploitation playbook. It contains plaintext credentials and directly actionable commands for certificate-based impersonation, NTLM relay, authentication coercion, Shadow Credentials, Golden Certificates, DCSync, persistence, and anti-forensics. It is not obfuscated and no executable malware payload is visible, but it presents a high security and abuse risk if included in an otherwise unrelated software package. Package installation behavior and omitted file sections require separate review.
This fragment is a dual-use AD CS penetration-testing and defense playbook, not package malware. It contains highly actionable privilege-escalation, credential-access, NTLM-relay, certificate-forgery, Shadow Credentials, PKINIT, and hash-dumping procedures. If executed without authorization, the commands could compromise an Active Directory forest. No embedded malware, persistence, obfuscation, automatic exfiltration, or supply-chain backdoor is present in the supplied text. The example password appears to be lab data but should be treated as unsafe and replaced.
This fragment is offensive security test-case documentation for AD CS and Active Directory attacks. It describes highly consequential actions, including certificate-based domain-controller impersonation, DCSync hash extraction, shadow-credential persistence, and CA private-key export. It does not itself contain executable malware, data exfiltration logic, or package-install behavior. Use is appropriate only with explicit authorization and isolated test credentials; the embedded example passwords should not be used in production.