Skip to content
KitploitKITPLOIT
工具漏洞利用博客
Log in
提交
工具漏洞利用博客
提交

黑客、渗透测试和网络安全工具,武装您的安全武器库!

Kitploit 是一个黑客、网络安全和渗透测试工具的目录。发现最新的项目更新,查找漏洞、分析系统、自动化测试并加强你的安全。

订阅源联系隐私© 2026 Kitploit

工具目录

分类

查看所有分类
Loading categories
ARTEX — LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting. | Kitploit
工具/GitHubGitHub/baarai/artex
Penetration Testing FrameworksReconnaissanceVulnerability ScannersNetwork MappingVulnerability AnalysisWeb Proxies & InterceptionScripting & AutomationWeb Application ExploitationInformation GatheringPenetration TestingRed TeamingAI Security
13.9k5.4k54315小时5分前Kitploit 审核通过
GitHubbaarai/artex

ARTEX

LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

查看仓库

最受欢迎

查看全部 →

发现我们社区最常用的工具。

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 终极 OSINT 工具包:调查图谱、置信度评分、别名家族、地图、时间线和报告。49 个模块、400+ 个站点,无需 API 密钥。

    1.1k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock 一键执行应用(CVE-2026-43499)

    618
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT 平台,可将 Shadowserver 报告导入 MongoDB,并将其重放为交互式地图、分析、发现、公告和高管仪表板。

    407
  • 4

    ARTEX

    baarai/artex

    基于LLM的多智能体自主渗透测试平台,具备规划器/执行器智能体、资产与探索图谱、MITM流量记录以及漏洞复测功能。

    324
  • 5

    jumpserver

    jumpserver/jumpserver

    JumpServer是一个开源的特权访问管理(PAM)平台,为DevOps和IT团队提供通过Web浏览器按需安全访问SSH、RDP、Kubernetes、数据库和RemoteApp端点的能力。

    279
  • 6

    Aliens_eye

    arxhr007/aliens_eye

    由 AI 驱动的 OSINT 引擎,可在网络上发现并映射 7,700+ 个社交媒体身份

    270

探索所有工具

浏览我们的工具集合

查看所有工具 →
分享
内容在请求的语言中不可用。显示英文版本。
ARTEX logo

ARTEX

Autonomous penetration testing that keeps its receipts.

(upstream: Autumn-27/ARTEX, AGPL-3.0)

Self-hosted multi-agent offensive security. A planner explores, workers run real tools, and every finding stays bound to the assets and HTTP traffic that prove it.

Release License CI Go

Quick start · Screenshots · How it works · Install · Configuration · Security


ARTEX is a self-hosted, LLM-driven penetration testing platform. It is not a chat wrapper around a scanner: a planner splits a goal into intents, workers execute them with real tools, and the results are written back into two linked graphs: one for what you know about the target, one for how the test is progressing. Every finding can carry the captured request and response that justify it, and every autonomous action passes through scope rules, approval gates and budgets.

  • It explores, it doesn't chat. Goal decomposition, intent dispatch, worker execution and write-back form a closed loop that keeps advancing until the goal is proven.
  • Two graphs, one audit trail. The shared asset graph says what exists; the per-task exploration graph says what was tried, what it produced, and why. Anchors link the two.
  • Findings with evidence. A recording MITM proxy and a browser extension capture real traffic; findings, evidence quotes and retests are tied to the exact request/response.
  • Autonomy with brakes. Human-in-the-loop approvals, argv-prefix rules, scope/deny gates, token and turn budgets, a target noise governor, and prompt-injection framing on tool output.
  • Self-hosted and model-agnostic. One Go binary with the Next.js UI embedded, PostgreSQL, your own Anthropic/OpenAI-compatible endpoint, or a local Ollama.

Quick start

git clone https://github.com/BaaRai/ARTEX.git
cd ARTEX
cp .env.example .env            # set POSTGRES_PASSWORD (and optionally an LLM key)
docker compose up -d --build    # builds from this checkout, starts PostgreSQL

Open http://localhost:8787. On the first visit /setup asks for the one-time setup token printed at startup:

docker compose logs artex | grep "Setup token"

There is no prebuilt Docker image to pull: the image is always built from your checkout. For all installation paths (script, binaries, source, release archives), see Installation.


Multi-provider workers

In System → LLM, configure the profiles you want to use. In System → Settings, set the concurrent worker count to at least 2 before starting a task (the count applies to subsequently started tasks). In System → Agents → Worker, leave the model set to follow the task; a fixed Worker model takes precedence over rotation.

When creating a task, select both profiles in LLM config chain, arrange their order, and enable Enable multi-LLM worker rotation. For an existing task, open its LLM config control, change the switch or profile order, and save.

Rotation assigns successive worker intents A, B, A, B, regardless of completion order. Separate intents can run concurrently on different providers; each intent keeps its selected provider unless it fails over. Planner and other unbound roles continue using the task's current profile. Turning rotation off restores ordered task-level failover. An excluded provider is skipped, so an intent pinned to an exhausted profile falls back to the task's current profile instead of retrying it; rotation keeps cycling the whole list and does not rebalance around a dead provider. Saving the chain resets their failure state. Changes do not interrupt in-flight calls. The rotation cursor starts again after a server restart and saving the chain does not reset it; the profile order and switch remain persisted.

The task creation and PUT /api/tasks/{id}/llm APIs accept llm_rotate: true alongside the ordered llm_profile_ids. Omitting llm_rotate on an update preserves its value.

Screenshots

TasksFindings
TasksFindings
Task execution: sessions and tool callsExploration graph
ExecutionExploration graph
Asset coverage graphTraffic recording
Asset coverage graphTraffic
Human-in-the-loop chatInterception approvals
ChatInterception
More screenshots (assets, agents, LLM, logs)
AssetsAgent management
AssetsAgent
LLM configurationBackend logs
LLMLogs

How it works

Dual-graph architecture: exploration graph + asset graph

下载工具