Back to skill

Security audit

tamil messaging

Security checks for vulnerabilities and agentic risk

Overview

This skill is a simple Tamil/Tanglish messaging style guide with no code execution, credentials, network access, or persistence.

Installers should understand that this skill may steer SMS replies toward Tanglish to reduce message length and cost. If preserving Tamil script is more important than SMS segment count, override that preference in the user prompt or local 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
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Natural-Language Policy Violations

Medium
Confidence
84% confidence
Finding
The instruction says to prefer Tanglish on SMS unless the user wrote in Tamil script first, which imposes a language/script choice based on channel constraints rather than explicit user preference. This is a natural-language locale policy concern because it can override the user's preferred language form without opt-in.

Static analysis

No suspicious patterns detected.