ClawHub
Back to skill

Security audit

Phoenix API Generator

Security checks across malware telemetry and agentic risk

Overview

This is a normal Phoenix API generator, but its tenant-security examples could lead generated apps to expose or change another tenant's data.

Review generated authorization code before using it. For tenant-scoped APIs, derive tenant identity from verified authentication or membership, scope every read/update/delete query by tenant at the context/query layer, and add tests that deny cross-tenant access.

SkillSpector

By NVIDIA
Vulnerability Patterns
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Intent-Code Divergence

Medium
Confidence
96% confidence
Finding
The router shows tenant-scoped API usage, but the controller examples for `show`, `update`, and `delete` call `Accounts.get_user!(id)` without applying `tenant_id` filtering. In a multi-tenant Phoenix app, this can teach generated code to authorize access based only on a guessed or enumerated ID, enabling cross-tenant read or modification of records.

VirusTotal

52/52 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.