PAGES
← all tools
◆ Cloud Security Posture

Pacu

v1.6.1 open-source

Pacu is an open-source AWS exploitation framework designed for offensive security testing against cloud environments using plug-in modules.

Summary

Pacu is an open-source AWS exploitation framework, free to use, that lets testers exploit configuration flaws in a cloud environment once they have a foothold. It runs as a command-line shell, installed via pip or pipx or launched from a published Docker image, and it works against live AWS accounts using modules rather than a fixed feature set, covering things like IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access. privilege escalationprivilege escalationGaining permissions beyond those an account or process initially had. It can turn limited access into administrator control or access to another user's resources., backdooring users, attacking Lambda functions, and enumerating services such as EKSEKSAmazon's managed Kubernetes service, run by AWS, that handles control-plane provisioning so teams can deploy containerized workloads without operating the underlying cluster infrastructure themselves., Elastic Beanstalk, and Directory Services. It is built for penetration testers doing offensive work against cloud environments rather than defenders monitoring them, and it sits in the cloud-security exploitation space alongside other AWS-focused attack tooling, maintained by Rhino Security Labs. With 87 contributors since its 2018 first commit and 34 commits and 14 releases in the past year, the project is under active development.

Pacu is an open-source AWS exploitation framework designed for offensive security testing against cloud environments using plug-in modules.

How Pacu helps

What can this AWS account's current credentials actually be escalated into?

walks the IAM permissions attached to the foothold through known privilege-escalation paths and reports which ones let it reach a higher-privileged role or user

Which IAM users or roles have a backdoor planted that would survive a password reset?

runs the backdooring modules against chosen identities and reports the access keys or trust relationships it added, so the same actions can be checked for or undone

What secrets are sitting exposed across this account's services?

enumerates likely secret locations and lists everything it finds after the scan completes, rather than stopping at the first hit

Which EKS pods would hand over a usable service account token?

queries running pods in the cluster and extracts the tokens it can reach, showing which ones grant further access

What does this account expose through Directory Services, Elastic Beanstalk, or domain trusts that wasn't on my radar?

runs the enumeration modules for each service and lists the environments, settings, shared directories, and trust relationships it finds, building out the picture of the account beyond IAM

all 8 features, with the evidence for each →

Languages

Not documented

Features

8 capabilities · 3 backed by code, an API document or a real run

Built from Pacu's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • Pacu covers 1 of the 8 vulnerability assessment methods capabilities we track.

What Pacu offers you

  • Command-line interface
All capabilities 8 capabilities
AWS IAM permissions auditing shipped suggested Audits and counts unconfirmed permissions for AWS Identity and Access Management resources. 4 releases · 6 other sources · first seen May 2024

Suggested capability: Data access governance. This is our guess, not confirmed.

release

  • Adds MFA support to assume_role, enabling role assumption with MFA-protected principals. v1.6.1 · Jul 2025 · source · release history
  • Updates iam__bruteforce_permissions to check all AWS services, expanding permission coverage. v1.6.1 · Jul 2025 · source · release history
  • Updates iam__enum_permissions module with expanded permission enumeration capabilities. v1.6.1 · Jul 2025 · source · release history
  • Enhances iam__enum_permissions with unconfirmed permission counts in output v1.6.0 · May 2024 · source · release history

docs

  • Open-source AWS exploitation framework for offensive security testing, enabling privilege escalation, IAM backdooring, and Lambda attacks via modules.

example

  • Run Pacu with default Docker entrypoint docker run -it rhinosecuritylabs/pacu:latest
  • Run Pacu with host AWS credentials mounted docker run -it -v ~/.aws:/root/.aws rhinosecuritylabs/pacu:latest
  • Set session for CLI commands pacu --session <session name>
  • List all available Pacu modules pacu --list-modules
  • Display Pacu CLI help menu pacu --help
Cloud resource enumeration verified Enumerates resource tags associated with cloud environments. 4 releases · 3 other sources · first seen Apr 2023

release

  • Adds ebs__enum_snapshots_unauth module for Unauthenticated EBS Snapshot Reconnaissance v1.4.2 · Oct 2023 · source · release history
  • Expands route53__enum enumeration to discover additional AWS Route 53 resources v1.3.1 · Aug 2023 · source · release history
  • Adds the organizations__assume_role lateral move module to perform role assumption across AWS Organizations boundaries v1.3.0 · Jun 2023 · source · release history
  • Adds iam__enum_action_query module for enumerated permissions query by actions v1.2.1 · Apr 2023 · source · release history

command line

example

  • Run the new unauthenticated scan to identify exposed EBS snapshots without credentials. pacu run ebs__enum_snapshots_unauth v1.4.2 · Oct 2023 · source
  • Run the updated enumeration module to find more Route 53 resources. pacu > run route53__enum v1.3.1 · Aug 2023 · source
Secret scanning verified Downloads the source code of a deployed application and scans it for secrets. 4 releases · 3 other sources · first seen Apr 2023

Shared capability: Static application security testing

release

  • Updates secrets_enum to list all found secrets after enumeration. v1.6.1 · Jul 2025 · source · release history
  • Adds the akid module with a built-in decoder to extract AWS Access Key IDs from provided strings v1.5.1 · Jan 2024 · source · release history
  • Adds jq module to parse collected data using jq syntax v1.3.1 · Aug 2023 · source · release history
  • Adds privesc method information output and method list feature to iam__privesc_scan v1.2.1 · Apr 2023 · source · release history

command line

  • --source — Download the source code of the deployed application and scan it for secrets. v1.6.1 · Jul 2025 · command-line history

example

  • Extract Access Key IDs from input text using the new akid module command. run akid -i "AKIA…" v1.5.1 · Jan 2024 · source
  • Execute the new lateral move module to assume roles across organizational units pacu --module organizations__assume_role v1.3.0 · Jun 2023 · source
Active Directory enumeration verified Enumerates Active Directory objects including shared directories, directory settings, and domain trusts. 2 releases · 3 other sources · first seen Jul 2025

release

  • New ds__enum (directory services enumeration) module for AWS Directory Service reconnaissance. v1.6.1 · Jul 2025 · source · release history
  • New eks__enum_pod_tokens module to extract service account tokens from running pods in EKS clusters. v1.6.1 · Jul 2025 · source · release history

command line

AWS Cognito interaction shipped Interacts with AWS Cognito services to test authentication flows and discover configuration details. 1 release · 1 other source · first seen Oct 2023

release

  • Adds cognito module for interacting with AWS Cognito services v1.4.0 · Oct 2023 · source · release history

example

  • Interact with AWS Cognito services to test authentication flows. python3 pacu.py --module cognito v1.4.0 · Oct 2023 · source
Elastic Beanstalk enumeration shipped Enumerates Elastic Beanstalk environments and their configurations. 1 release · first seen Jul 2025

release

  • New elasticbeanstalk__enum module to enumerate Elastic Beanstalk environments and configurations. v1.6.1 · Jul 2025 · source · release history
AWS Message Queue enumeration shipped Enumerates Message Queue resources to discover configuration details. 1 release · first seen May 2024

release

  • Adds new mq__enum module for enumerating Message Queue resources v1.6.0 · May 2024 · source · release history
AWS SNS enumeration shipped Enumerates SNS topics and manages subscriptions such as email-based notifications. 1 release · first seen May 2024

release

  • Adds new SNS topic subscription via email and SNS enum modules (sns__enum, sns__topic_subscription_email) v1.6.0 · May 2024 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Pacu, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Pacu puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

8 entries

  1. July 20251
  2. May 20241
  3. January 20241
  4. October 20232
  5. August 20231
  6. June 20231
  7. April 20231
    Show

    8 entries

    Project health

    Issue, contributor and maintainer activity in RhinoSecurityLabs/pacu, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 6 −1 vs prior 12 months
    2. Maintainers 2 +2 joined · −3 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 203 days first maintainer reply 12 days
    6. Open backlog 22 of 148 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 22
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 5,336
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →