Back to skill

Security audit

Flutter Senior Review (HauTV)

Security checks for vulnerabilities and agentic risk

Overview

This skill is a Flutter/GetX code-review checklist with no executable code, hidden persistence, or credential access behavior.

Install this only if you want Codex to apply a strict Flutter/GetX review style. It will likely flag many architecture, formatting, logging, and Jira-ticket issues, but the reviewed artifact contains no executable components or hidden data access instructions.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 62)May include surrounding context.

md
## 8. Security & Logging
- **DON'T** allow raw `print()` statements in the code. Flag all `print()` usages and suggest using a custom Logger (e.g., `logger` package) that only prints in `kDebugMode`.
- **DON'T** hardcode sensitive keys (API Keys, Tokens) in the source code. Require them to be loaded from `.env files`.

## 9. Naming Conventions & Folder Structure
- **File names**: Must be `snake_case.dart`.