🐟🍟

Phish&Chips

TRACK 01: BLAST RADIUS ZERO

Fresh phish, fried in a sandbox. // Ephemeral Detonation & AI Forensics

Vultr BLR Control Plane
| 0 / 3 Sandboxes Active | phishnet: Enforced | Inference: Connected
Test Presets:
Real-Time Orchestration Pipeline CONTROL PLANE IDLE • STANDBY
1. Client Origin 💻
User Browser
HTTPS / TLS 1.3 (sslip.io)
2. Control Plane ⚙️
Vultr VM Host
Auth, Queue, SSRF Shield
3. Detonation Chamber 🔒
phishnet Container
cgroups 1G, Cap-Drop, 169.254.x Drop
4. Threat Engine 🧠
Vultr Serverless AI
Vision / Heuristic Synthesis
Live Containment Terminal STREAMING SSE
0 events
Connecting to sandbox event stream...
Perimeter: 172.30.0.0/16 (phishnet) • DROP ALL CAPABILITIES
Hard Containment Boundaries
cgroup Memory 1024 MB Cap
CPU Quota 1.0 vCPU
Capabilities DROP ALL
Root Filesystem READ-ONLY
Sandboxed Visual Forensics 0 captures
Detonation Capture

Click screenshot to inspect full-resolution container artifact

How Phish&Chips Stays Safe (Blast Radius Zero)

1. Process Isolation Untrusted code runs strictly inside a throwaway container; the host VM and user device are completely insulated.
2. Secret Hygiene No API keys, credentials, or private paths ever enter the sandbox container runtime.
3. Resource Limits Hard Linux cgroups cap execution to 1 CPU, 1 GB RAM, 256 PIDs, with a 45s hard wall-clock kill switch.
4. Lifecycle Discipline Every container is purged immediately after scan completion. No state persists.