T09 · Insecure Skill Coding Practices
- Location
index.js:91- Finding
Prompt-injection filtering can be bypassed through Unicode characters and case variations
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This firewall skill has a legitimate purpose, but it stores sensitive context in plaintext logs and overstates several protections, so users should review it carefully before installing.
Treat this as an experimental local firewall, not a dependable security boundary. Do not pass secrets, tokens, private prompts, or sensitive metadata in context unless logs are disabled or rewritten to redact and bound data. Verify callers ignore originalData, and do not rely on the advertised custom rules, rate limits, URL blocking, or command blocking until they are implemented and tested.
index.js:91Prompt-injection filtering can be bypassed through Unicode characters and case variations
index.js:85Advertised firewall controls are placeholders or disabled by default
index.js:265Unbounded caller-controlled context is persisted in plaintext logs
The skill’s documented behavior indicates broad logging of blocked events with full context and reliance on local files for rules/logging, which exceeds the declared filtering-only purpose and can create privacy and security exposure. In a firewall-style skill, incomplete enforcement is also dangerous because operators may trust it to block prompt injection, exfiltration, and unauthorized commands when protections are only partial or stubbed.
The skill returns originalData together with processedData, which defeats the purpose of a firewall skill intended to block or redact unsafe content before downstream consumption. Any caller that logs, forwards, or mistakenly prefers originalData can still access the unfiltered prompt or response, enabling prompt-injection bypass and secret/PII leakage.
This pattern attempts to override system instructions or ignore safety constraints. Without LLM analysis, manual review is recommended.
rule: 'role-confusion',
action: 'BLOCK',
severity: 'CRITICAL',
message: 'Role confusion detected: Agent attempted to override system instructions.'
});
filteredData = '[BLOCKED: Role confusion detected]';
}
Logging the full context of blocked messages can capture secrets, personal data, or sensitive prompts precisely at the point where suspicious or harmful content is detected. Because this skill is intended to process all agent communications, the logging scope makes the privacy risk greater, and those logs could become a secondary exfiltration target.
The logging routine persists full context objects to disk in JSONL files. In a firewall skill, context is likely to contain prompts, user identifiers, secrets, paths, or task state, so this creates unnecessary retention of sensitive material and a secondary data-exposure surface on the filesystem.
Writing action logs with full context to local storage can capture sensitive user inputs and operational metadata without explicit user awareness or consent. This expands the data lifecycle beyond transient filtering and creates a durable artifact that may be read by other local users, backup systems, or later processes.
Persisting full action context in plain-text JSONL can retain user-provided sensitive data long after processing completes. For a firewall skill specifically tasked with preventing exfiltration and unsafe handling, such storage is contextually more dangerous because it creates a built-in side channel for secrets and private inputs.
The configuration and loadRules flow imply use of an external YAML rules file, but the inline documentation admits the file is not parsed and the function always returns defaultRules. This is an intent/documentation divergence because the code path suggests configurable firewall policy while the implementation does not honor it.
The comment says "Demander à l'agent de ne pas décoder automatiquement," introducing a language-specific instruction in French within the skill file. This can violate language/locale policy because it imposes a specific language without offering user choice or documenting a justified locale constraint.