lilrae

mcp
Security Audit
Fail
Health Pass
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 25 GitHub stars
Code Fail
  • rm -rf — Recursive force deletion command in .github/workflows/checks.yml
Permissions Pass
  • Permissions — No dangerous permissions requested
Purpose
This tool is a Docker-based "SOC-in-a-Box" designed for AI purple teaming. It deploys an isolated lab environment featuring vulnerable target infrastructure, a full SOC stack, and AI agents to automate red-team attacks and blue-team defenses.

Security Assessment
The overall risk is rated as Medium, primarily due to the inherent nature of the tool rather than malicious code. By design, it executes shell commands, makes network requests, and manages vulnerable applications (such as intentionally flawed web apps and phishing simulations). However, the automated code scan passed with no dangerous patterns found and there are no hardcoded secrets or dangerous permissions requested. It is crucial to note the developer's explicit warning: this is strictly a proof-of-concept for isolated research and should never be deployed in a production environment.

Quality Assessment
The project is actively maintained, with its most recent push occurring today. It benefits from clear documentation, passes a SonarCloud quality gate, and is protected under the permissive MIT license. Community trust is currently low but present, represented by 13 GitHub stars, which is typical for a niche, early-stage cybersecurity research tool.

Verdict
Use with caution — the tool itself is clean and safe for isolated research, but the intentionally vulnerable infrastructure and offensive capabilities require strict containment within a sandboxed environment.
SUMMARY

Single-user OpenRÆ backend for creating sandboxes, cyber ranges, digital twins, and other environments.

README.md

Quality gate
OpenSSF Scorecard

🎤 Accepted to Black Hat USA Arsenal 2026, SecTor Arsenal 2026, and SecTor 2026 Briefings.

APTL—Advanced Purple Team Lab

APTL is a local purple-team lab where human operators and AI agents exercise
red- and blue-team workflows against an intentionally vulnerable enterprise
range. Scenario documents select and realize the target, attacker, and SOC
topology; the CLI owns validation, startup, readiness, access discovery,
teardown, and run records.

Use cases include autonomous cyber-operations research, purple-team training,
and AI threat-actor assessment.

Status And Safety

Active development. Not for production. Not hardened. APTL gives AI agents
penetration-testing tools and starts intentionally vulnerable services. Use a
dedicated, rebuildable host, keep unrelated credentials and workloads
elsewhere, control the surrounding network, and operate only on systems you are
authorized to test.

For stronger host and cross-seat isolation on Linux/KVM, use a disposable
aptl seat. A VM boundary reduces
risk but does not eliminate it; keep the host kernel and hypervisor current.

Quick Start

Install the released CLI and materialize its bundled lab assets. No source
checkout is required:

pipx install aptl-labs
aptl lab init my-lab
cd my-lab
aptl lab start --scenario techvault

Startup validates the selected scenario, creates private project state,
realizes the topology, waits for required readiness checks, and reports a
structured outcome. Inspect the runtime-derived state and access information:

aptl lab status
aptl lab info
aptl container list

URLs, host ports, available containers, usernames, and credential locations
belong to the realized project. Use aptl lab info; do not rely on static
values copied from documentation.

At the end of the session:

aptl lab stop      # preserve project volumes
aptl lab stop -v   # confirm and destroy project volume data

Read the first-lab guide for scenario
selection, safe activity, result inspection, troubleshooting, and teardown.

Requirements

  • Python 3.11 or newer and pipx
  • Docker Engine or Docker Desktop with Compose and Buildx
  • OpenSSH client with ssh-keygen on PATH
  • Node.js 20 or newer and npm for MCP artifact builds
  • 20GB or more of free disk space
  • Sufficient Docker memory for the selected scenario; the full acquired
    TechVault stack needs more than 20GB

See Prerequisites for platform-specific
setup and verification.

Supported Interfaces

  • CLI is the primary lab control plane.
  • MCP servers give authorized agents scenario-aware
    red- and blue-team tools through generated private client configuration.
  • Web interface provides a loopback-first local
    operator UI and typed API.

The APTL operator UI, vulnerable target applications, and third-party SOC
interfaces are separate surfaces. The selected scenario determines which ones
exist.

Scenarios

The APTL startup catalog exposes the scenario selections supported by the
installed release. Reusable environment-pack definitions and authoring support
live in the companion OpenRAE/env-packs
repository; APTL owns admission, realization, readiness, and operation of the
selected scenario in the local lab.

Documentation

The published site is the canonical user manual:

The README is the GitHub and package-index gateway, not a second copy of the
manual.

Project Links

Do not report suspected vulnerabilities through a public issue. The
security policy describes scope and the private fallback contact
path.

Ethics And Disclaimer

APTL uses commodity services and standard security tooling. AI agents get Kali
access; this public repository does not add red-team enhancements to their
latent capabilities. You are responsible for following all applicable laws and
for obtaining authorization before testing a system.

The repository contains intentional test credentials used only by lab
fixtures. They are not production secrets. Runtime control-plane credentials
are generated into private project files and must not be committed or shared.

License

MIT

Reviews (0)

No results found