T09 · Insecure Skill Coding Practices
- Location
SKILL.md:50- Finding
Insecure Collection of Account Credentials and SMS Authentication Codes
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 50-52
Vulnerability Type: Plaintext sensitive-data handling
Risk Level: HighVulnerable Code Snippet:
markdown 2. Frage den Human nach E-Mail + Passwort für den Login 3. Gib die Anmeldedaten ein 4. **SMS-Code**: Der Human gibt den Code, sobald er per SMS ankommt. Warte auf ihn.English translation:
text 2. Ask the user for their email address and password for login. 3. Enter the login credentials. 4. SMS code: The user provides the code when it arrives by SMS. Wait for it.Technical Analysis
The skill explicitly instructs the agent to solicit the user's Kleinanzeigen email address, password, and SMS authentication code. Supplying these secrets through the agent exposes them to the conversational context and potentially to model telemetry, logs, session history, memory features, browser automation traces, or other components with access to agent inputs.
This violates secure authentication design and least-exposure principles. Browser automation does not require the agent to know or process the credentials: the workflow can pause while the user enters the password and multifactor authentication code directly into the trusted website interface.
No malicious exfiltration destination is specified, but the insecure handling itself creates an exploitable disclosure channel.
Attack Path
- The user invokes the skill to create a Kleinanzeigen listing.
- The workflow reaches the login stage.
- Following
SKILL.md, the agent asks the user to provide an email address and password through the agent conversation. - The agent receives and enters those credentials into the website.
- The agent also asks the user to provide the time-sensitive SMS authentication code.
- The credentials and MFA code become available in agent-visible context and may be retained in conversation history, telemetry, logs, memory, or tool tr ...[truncated 1035 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove all instructions asking users to send passwords or SMS codes to the agent.
- Navigate to the legitimate Kleinanzeigen login page, pause automation, and instruct the user to enter their email address, password, and MFA code directly into the browser.
- Resume automation only after the website confirms successful authentication.
- Add an explicit warning that passwords, one-time codes, recovery codes, and session tokens must never be entered into chat.
- Ensure browser tooling does not capture authentication-field values in screenshots, logs, traces, or action summaries.
- Redact sensitive form fields if the browser framework records page state.
- Do not store authentication data in skill state, long-term memory, temporary files, or generated listing content.
- Prefer an existing authenticated browser session or a platform-supported delegated authorization mechanism where available.
- Clear any transient authentication-related context after login and implement retention controls for automation telemetry.
