T09 · Insecure Skill Coding Practices
- Location
SKILL.md:79- Finding
Plaintext Tilda credentials stored in the workspace
- Content
View full analysis
l.startsWith(`${key}=`)); const line = `${key}=${value}`; if (idx >= 0) { lines[idx] = line; } else { lines.push(line); } } fs.writeFileSync(envPath, lines.join('\n') + '\n'); console.log('Settings saved to .env'); } saveToEnv({ TILDA_EMAIL: emailFromUser, TILDA_PASSWORD: passwordFromUser, TILDA_PROJECT_NAME: projectFromUser || '', }); ``` ### Technical Analysis The onboarding procedure writes the user's Tilda email and raw password to `.env` in the current workspace. The write operation does not set restrictive permissions, validate file ownership, encrypt the values, or ensure that the file is excluded from source control and backups. The effective permissions therefore depend on the process umask and any permissions already assigned to an existing `.env` file. Other local users, workspace tools, backup systems, indexing services, or processes running under the same account may be able to read the credential. The file could also be committed or uploaded accidentally. The README states that the password is stored locally, but local storage alone does not adequately protect a reusable account password. ### Attack Path 1. A user completes onboarding and supplies a Tilda email and password. 2. The Skill writes both values in plaintext to `/.env`. 3. An attacker obtains read access through another process, shared workspace access, ...[truncated 1005 chars]- Remediation
View remediation
