T09 · Insecure Skill Coding Practices
- Location
scripts/encryption-service.js:70- Finding
Extractable operational encryption keys remain exposed in page memory
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This is a local encryption skill with no evident exfiltration, but its own implementation keeps extractable key material in memory without a clear lock mechanism.
Review this before installing if you expect strong protection against same-page script compromise. It appears local-only and purpose-aligned, but users should treat the vault as exposed while unlocked, understand there is no password reset, and prefer an implementation that uses non-extractable operational keys and clears in-memory key state on lock, logout, or session expiry.
scripts/encryption-service.js:70Extractable operational encryption keys remain exposed in page memory
The function unlocks an existing vault using a passphrase and performs master-key rotation logic involving the KEK, which is sensitive credential-handling behavior. While there is a startup log message, it does not disclose the safety-sensitive nature of unlocking and re-wrapping encryption keys, and there is no confirmation prompt, warning comment, or user-facing notice about the impact of the operation.
The natural-language navigation explicitly presents only English and Chinese sections, and the document does not state that these are optional examples or that users may choose other languages. Under the policy, forcing a specific language or locale without user opt-in can be a violation unless clearly justified.
The phrase 'after هر reboot' introduces a non-user-selected non-Latin script into operational instructions, which can confuse users, impair accessibility, and create ambiguity in security-critical recovery guidance. In a security/encryption skill, even small comprehension issues matter because users may misunderstand passphrase persistence or recovery expectations.