Identity attack paths

2 tools. Compare how each tool runs, what it needs, where it sends data, what it can change and what its code can touch. Feed: /tasks/identity-attack-paths/feed.xml

Tools for the task: Identity attack paths
ToolRuns and needsWhere the tool runs and what must be in place before it works.Sends data toOutside parties the tool contacts, read from the code and the documentation. Other connections are not ruled out.Can change thingsWhether the tool's functions only read, or also create, change or delete things, run commands, or send data out.How to run itThe run advice where we have read the tool under the verdict rule, else what the code shows; below it, whether it has run in our lab.
Supercharged Tenable Identity Exposure MCP ServerDraft · awaiting review

MCP server that exposes the Tenable Identity Exposure API as 133 tools, from Active Directory exposure queries to user and API-key management.

MCP server · taherkaraki, pushed 2026-07-28

Started by your client

Works with: Any MCP client, Claude Code

Needs: Node.js 18 or later; A TIE API key, set in TIE_API_KEY; +3 more

TIE instance at TIE_BASE_URL, npm registrychanges, deletes

Code shows: adds autostart, users or keys · Approval: unknown

Not run yet

hackingBuddyGPTDraft · awaiting review

Open-source framework for building LLM-driven security-testing agents, with use cases for Linux privilege escalation and web API testing.

Agent · ipa-lab, pushed 2026-10-01

Program you start

Works with: Standalone (own model access)

Needs: Python 3.13 or newer; An LLM provider API key (litellm format), default endpoint OpenRouter; +3 more

OpenRouter / litellm-reachable LLM provider, SSH target, HTTP target host, Windows psexec target, intercepting proxy (Burp/mitmproxy), OpenAI embeddings, OpenRouter / Anthropicchanges, deletes, runs commands, sends data out

Code shows: writes outside the project · talks to any host · runs shell commands or eval · +3 more

Not run yet