Code and System Security Review

• Outcome: Pass
• Latest audit: Sep 16, 2026 · 8:02 AM UTC
• Version: 1.0.1

Overview

This is a straightforward code security review checklist skill with no executable payload, persistence, or hidden behavior beyond a harmless UTF-8 BOM marker.

Install only if you want Codex to help review code for security issues. It may cause security-review requests to use this checklist and may suggest code patches, so review proposed changes before applying them.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Privilege Escalation: Excessive Permissions, Sudo/Root Execution, Credential Access
• Tool Misuse: Tool Parameter Abuse, Chaining Abuse, Unsafe Defaults
• Trigger Abuse: Overly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration

Findings (5)

Hidden Instructions

High

• Category: Prompt Injection

Content

# Security Review Checklist

## Injection Vulnerabilities

• Confidence: 60% confidence
• Finding: Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.

Hidden Instructions

High

• Category: Prompt Injection

Content

# Security Review Checklist

## Injection Vulnerabilities

• Confidence: 60% confidence
• Finding: Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.

Credential Access

High

• Category: Privilege Escalation

Content

- Are API keys / tokens / passwords hardcoded?
- Are keys in configuration files encrypted or stored in environment variables?
- Is sensitive information (tokens, passwords, ID numbers) printed in logs?
- Are .env / key files listed in .gitignore?

## Insecure Deserialization

• Confidence: 60% confidence
• Finding: Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Vague Triggers

Medium

• Confidence: 95% confidence
• Finding: The invocation text lists generic phrases such as 'security check', 'security assessment', and 'code scan' without clarifying scope, exclusions, or negative examples. This can cause unintended activation for broad everyday requests about security-related topics rather than a deliberate request to run this specific skill.

Unsafe Defaults

Medium

• Category: Tool Misuse

Content

- Are weak algorithms used (MD5, SHA1, DES, RC4)?
- Are the TLS version and cipher suites secure?
- Is certificate verification skipped (`verify=False`)?

## SSRF

• Confidence: 75% confidence
• Finding: Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.

Static analysis

No suspicious patterns detected.