hunt-laravel

Validates Laravel and PHP application security through evidence-gated black-box testing workflows.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-laravel-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-laravel
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/hunt-laravel
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-laravel-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security testers assessing Laravel/PHP applications often produce false positives from generic scanner hits or PHP stack traces, and risk unsafe actions like triggering deserialization gadgets or leaking APP_KEY secrets. This Skill enforces an evidence-gated, authorization-first workflow for Laravel-specific validation. ## Core Features & Use Cases - Framework Fingerprinting: Confirms Laravel version, exposed routes, debug status, and session/file/queue features from responses, static assets, and deployment metadata before any probing. - Evidence-Gated Validation: Uses vendor advisories and self-owned debug canaries for low-impact verification, rejecting scanner findings and generic PHP errors as proof. - Safe Routing & Stop Conditions: Halts on deserialization gadgets, secret usage, or queue commands, and routes upload/session/deserialization findings to specialized skills or CVE methodology. - Use Case: During an authorized engagement, you detect a Laravel debug page on a target. Use this Skill to confirm the framework version, validate configuration boundaries with your own canary, and document evidence without executing chain exploits. ## Quick Start Use hunt-laravel to plan an evidence-gated, authorized validation path for the Laravel target in scope.

Frequently Asked Questions about hunt-laravel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a Laravel application for security issues?

Start by confirming the framework and version from responses, error pages, or deployment metadata, then check debug status, exposed routes, and session/file/queue features. Validate findings only with vendor advisories or your own canaries, never with chain exploits.

How to confirm a website is running Laravel?

Look for trigger signals such as Laravel cookies, artisan hints, composer metadata, debug pages, and PHP stack traces. A generic PHP page or header alone is not sufficient evidence of Laravel.

What counts as valid evidence in Laravel security testing?

Valid evidence is independent confirmation of an affected Laravel version with exposed preconditions, or a self-owned canary showing a configuration boundary failure. Scanner findings, stack traces, and generic PHP errors are inconclusive.

When should Laravel penetration testing stop immediately?

Stop when encountering deserialization gadgets, APP_KEY or secret usage, queue command execution, real debug data, or any irreversible side effect. WAF blocks, captchas, and timeouts are treated as inconclusive, not failures.

Can this workflow run without authorization?

No. The engagement gate requires declared authorization, locked scope, and an established host, identity, and path baseline before any probing. Only self-owned accounts, test data, and approved rates are permitted.