/var/log/mire/access.log and useragent.log for logged entries.
CORE FUNCTIONAL CHANGE Presently, The MIRE/C³ is configured to route all errors into its neutral 404 handler
Delays are configured from 5-15 seconds
Secure 404 error handler that prevents information disclosure through verbose error messages—a common penetration testing finding. Returns a clean, minimal 404 page with proper HTTP status code (3–8s delay) without leaking stack traces, file paths, server versions, or internal application structure that attackers use for reconnaissance.
Targets Laravel environment files with production credentials (AWS, DB, Stripe, Pusher). Fake log files expose DB credentials and API keys. Artisan script reveals database URL in comments.
phpMyAdmin and Adminer login pages with internal MySQL servers pre-populated. 2–5s delay on all DB admin paths. Generic endpoints return JSON with database lists and API tokens.
Jenkins dashboard with fake build jobs (1.5–4s delay). Script console with Groovy environment showing DB passwords and AWS keys. Job pages expose backup artifacts and config files.
AWS EC2 metadata endpoints return IAM credentials with AccessKeyId/SecretAccessKey. User-data shows bash script with DB passwords and AWS keys. GCP metadata returns service account tokens.
Direct AWS credentials file exposure (1–3.5s delay). Returns realistic .aws/credentials format with [default], [production], and [s3-backup] profiles containing AccessKeyId and SecretAccessKey.
Fake checkout page with payment form. Exposes Stripe API keys (pk_live_, sk_live_) plus payment gateway URL, merchant ID, and API token in visible HTML block.
.git directory exposure with config file showing GitHub remote URL and personal access token (ghp_...). HEAD file reveals current branch. Directory listing shows typical git structure.
Any path ending in an archive extension triggers nested archive generation (100KB–2MB) with a 2–6s delay. OS path decoys seeded throughout; a canary token is guaranteed deployed inside every archive. 20% chance of password-protection — password is logged.
Paths like /dev/, /test/, /staging/ appear as "Production" or "Pre-Production" to simulate misconfigured servers. phpinfo.php exposes environment vars with AWS keys and DB passwords. Debug traces show connection strings.
Classic CGI vulnerability scanner target. Directory listing shows common scripts (status.cgi, admin.cgi, printenv.cgi). Script content exposes DB credentials and admin email in fake bash output.
/info and /about return detailed server information (nginx version, PHP, MySQL, Redis, Node.js versions) plus database hosts, API endpoints, credentials, deploy info, and Git commit hashes.
Directory listing shows backup archives, database exports, user CSVs, and config files. Webshell probes (.php, .asp, .jsp files) return fake PHP shell code. Detects malicious upload attempts.
Swagger UI and API documentation endpoints (0.8–2.5s delay). JSON specs include API keys, database URLs, and endpoint listings. GraphQL playground exposes users query with database_url and api_key in response.