Privilege_Escalation_Test
ListedSimulates privilege escalation attempts to identify potential vulnerabilities in system configurations and user permissions.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add charpup/skill-security-auditor --skill privilege_escalation_test -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
charpup
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
Declares what it does: failed
SKILL.md has no YAML frontmatter, so it declares nothing machine-readable.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.clawsec.io.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
api.clawsec.ioundeclaredraw.githubusercontent.comsource hostgithub.comsource hostWhat it found
- config/default.yaml:24contacts api.clawsec.io
feed_url: https://api.clawsec.io/v1/feed - lib/clawsec_integration.py:48contacts api.clawsec.io
"https://api.clawsec.io/v1/feed"
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned charpup/skill-security-auditor at 086718493c.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 086718493c
- Manifest
- SKILL.md
- Scanned
- 30 files, 3,341 lines
About this skill
What it does
This skill, privilege_escalation_test, is designed to assess a system's vulnerability to privilege escalation attacks. It can identify potential weaknesses in user permissions and access controls, simulating common exploitation techniques. The tool helps security auditors proactively discover misconfigurations that could allow unauthorized users to gain elevated privileges.
When to use it
- Security Audits: As part of a broader security audit of a system or application.
- Penetration Testing: To simulate an attacker attempting to escalate their privilege level within a controlled environment.
- Post-Configuration Verification: After implementing new user roles or access control policies, to ensure they are functioning as intended and haven't introduced unintended escalation paths.
- Vulnerability Hunting: Proactively searching for potential privilege escalation vulnerabilities before malicious actors can exploit them.
Key capabilities
- Privilege Escalation Testing
- User Permission Assessment
- Access Control Validation
- Exploitation Simulation
Example prompts
- "Test for privilege escalation paths starting from the 'guest' user account."
- "Simulate a scenario where a user has compromised a service account and attempt to escalate privileges."
- “Identify any misconfigured sudo rules that could lead to privilege escalation.”
Tips & gotchas
This skill requires a thorough understanding of system administration and security principles. Incorrect usage or interpretation of results can lead to unintended consequences, so it's best used by experienced security professionals.