Back to skill

Security audit

ia-php-laravel

Security checks for vulnerabilities and agentic risk

Overview

The skill is marked suspicious because scanners report that its queue verification guidance could process a live queued job without warning; the scan also found a purpose mismatch and a missing referenced path, so evidence is incomplete.

Review the queue verification instructions before installing: running the command against a shared or production queue could trigger a job's side effects. The scan covered the listed components but remained partial because a local path-like reference was unresolved; treat the findings as incomplete evidence, not proof that the skill is safe.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (5)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

The supplied commands concern evaluating and diagnosing a named skill, not developing or testing a Laravel application. Although the target name references PHP and Laravel, that does not make these meta-evaluation operations part of the declared purpose. The invoked script's internals are not supplied, so no additional behavior or resource access is inferred.

Content

No source excerpt is available for this finding.

Anti-Refusal Statement

High
Category
Anti-Refusal
Confidence
80% confidence
Finding

Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.

Content

Scanner excerpt · references/common-pitfalls.md (reported line 19)May include surrounding context.

md
hole in whatever the events enforce.

**The cascade does not fire at all when the parent soft-deletes.** `SoftDeletes` intercepts `delete()` at the model layer and rewrites it as `UPDATE ... SET deleted_at = ...`; `ON DELETE CASCADE` only fires on real `DELETE` SQL. The parent row stays alive, the children's FK still points at a live row, and the cascade is a pure no-op for every path that calls `$parent->delete()`, usually the dominant one. It applies only to the `forceDelete()` minority, with no warning at migration time and no failure at runtime. Same trap in any ORM that overlays soft delete on an SQL referential action.

When a change adds a delete path on a parent, answer both: do the children die by cascade or row by row, and does the parent use `SoftDeletes`? `grep` the parent model for `use SoftDeletes;` and classify every `->delete()` / `->forceDelete()` call site. Delete per row inside the transaction wherever an event-layer invariant must hold. On the test side, write casca

The queue verification step executes a pending job without warning about live side effects.

Medium
Category
Output Handling
Confidence
93% confidence
Finding

The skill directs the agent to run queue:work --once as a routine verification step without requiring an isolated environment or queue. This processes an available job from the configured queue, potentially an unrelated live job with effects such as sending notifications, modifying records, or invoking external services; --once limits execution count, not side effects.

Content

No source excerpt is available for this finding.

The scheduling example instructs daily deletion of session records without warning about session-data loss or possible user sign-outs.

Medium
Category
Output Handling
Confidence
88% confidence
Finding

The example schedules deletion of all session records whose last activity is more than one day old, without checking the application's configured session lifetime. There is no accompanying warning that this permanently removes session state and could invalidate otherwise valid sessions when longer lifetimes are configured.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

Scanner excerpt · references/mocking-and-faking.md (reported line 97)May include surrounding context.

md
$this->assertSame('Test', $result['name']);

    Http::assertSent(fn ($request) =>
        $request->url() === 'https://api.example.com/data'
        && $request->hasHeader('Authorization')
    );
}