Skip to content

About

Source-built, locally bound FailSafe distribution of ARTEX (v0.3.15)

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

 
 

Latest commit

 

History

5 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

FailSafe ARTEX

ARTEX — a source-built FailSafe distribution

A source-built, locally bound distribution of ARTEX, an open-source multi-agent security testing harness.

This repository exists because the prebuilt tomicdd/artex Docker image was found to contain an unauthenticated command-execution backdoor in November 2026. This build is compiled from the audited v0.3.15 source tag and keeps upstream's full runtime capabilities, including Node 22, Playwright, Chromium, and nmap. The compose file binds the console to localhost and does not publish the recording proxy.

Authorized testing only. ARTEX runs an autonomous agent that can execute shell commands and send network traffic. Use it only against systems you own or have explicit written permission to test.

Managed ARTEX runs

FailSafe can host and run ARTEX safely for you using GlassBreak, our cyber-grade model. We handle the isolated runtime, scoping, evidence handling, and the operational controls that are easy to get wrong in a self-hosted deployment.

If you want a managed run, contact us:

Quick start

Requirements: Docker Engine with Compose v2, and about 5 GB of free disk (the browser stack and Chromium account for most of the image size). If your Docker installation only provides the standalone docker-compose command, substitute it for docker compose below; make detects either.

cp .env.safe.example .env.safe
chmod 600 .env.safe
# edit .env.safe: set POSTGRES_PASSWORD and, optionally, an LLM key
docker compose --env-file .env.safe -f docker-compose.safe.yml up -d --build

Open http://127.0.0.1:8787 and complete the first-run setup. If you left the LLM key blank, configure a provider in the console before starting a scan.

Check status and logs:

docker compose --env-file .env.safe -f docker-compose.safe.yml ps
docker compose --env-file .env.safe -f docker-compose.safe.yml logs -f artex

Stop without deleting data:

docker compose --env-file .env.safe -f docker-compose.safe.yml down

Delete everything, including the database and ARTEX data:

docker compose --env-file .env.safe -f docker-compose.safe.yml down -v

What is different from upstream

Area Upstream default This build
Image prebuilt tomicdd/artex (backdoored) compiled from this source tree
Runtime user root root (upstream parity)
Console binding 0.0.0.0:8787 127.0.0.1:8787
Recording proxy published on 8788 not published
Browser automation Node 22 + Playwright + Chromium same, pinned versions
Browser MCP launcher npx @playwright/mcp pinned playwright-mcp
Capabilities default Docker set default Docker set + no-new-privileges
Self-update points at upstream points at this fork; one-click update disabled
Base images floating tags pinned by digest

The API, UI, skills, browser MCP, and browser-driven recon are unchanged. Node, Playwright, the Playwright MCP/CLI, and Chromium are preinstalled; nmap raw scans and runtime apt/npm -g installs work because the container runs as root, as upstream does. The deployment hardening that remains is the loopback-only console, an unpublished proxy, no-new-privileges, a persisted JWT key, and digest-pinned base images.

Build without Docker

cd web
npm ci --ignore-scripts
npm run build:static
cd ..

rm -rf server/webui/dist
mkdir -p server/webui/dist
cp -R web/out/. server/webui/dist/

CGO_ENABLED=0 go build \
  -trimpath -buildvcs=false -tags embedui \
  -ldflags="-buildid= -X main.version=v0.3.15-failsafe.1" \
  -o artex ./cmd/artex

Then run ./artex -addr 127.0.0.1:8787 -proxy 127.0.0.1:8788 with ARTEX_PG_DSN set to a PostgreSQL database you control. This bare-binary path does not install Node, Playwright, Chromium, or the recon CLI tools; use the Docker image for full upstream capability.

Verify the build

make verify

This checks the known implant indicators (verifyCaptcha, tomicdd, congdonglinux), prints the binary SHA-256, and lists the image ID. See audit/artex-v0.3.15-audit.md for the full audit of this tag.

Data and secrets

  • .env.safe contains the database password and optional LLM keys. Keep it 0600 and out of version control.
  • The database lives in the pgdata volume; ARTEX data and evidence live in artex_data; the JWT signing key lives in artex_key. Back up all three.
  • ARTEX stores scan evidence, which may include credentials, tokens, and customer data. Treat /app/data and the database as sensitive.
  • For a backup, stop the stack and archive the volumes, or use pg_dump inside the postgres container.

Updating

Read UPSTREAM.md first. In short: review the upstream diff, rebuild, run make verify, update the audit report, and only then deploy.

License and provenance

ARTEX is AGPL-3.0. See LICENSE and UPSTREAM.md. This fork's modifications are released under the same license. The upstream README is preserved as README.upstream.md.

About

Source-built, locally bound FailSafe distribution of ARTEX (v0.3.15)

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages